This course introduces a selection of theories and practices that, we believe, will enhance the student's ability in developing correct and high-quality software. Its goal is to acquaint the students with some of the well-used methods and tools for practical software development as well as some fundamentals of software verification, so as to prepare them for a career in software development. The view taken here is that of an engineer (programmer, software engineer, or software architect) and hence the focus of the course is primarily on the technical aspects of software development process.

• 06/16: scores of term project.
• 06/07: final exam due 5:20PM 06/07.
• 05/24: HW#5 due 23:59PM 06/06.
• 05/24: slides for Formal Logic, Hoare Logic, and Frama-C and ACSL available.
• 05/16: suggested solutions to HW#3 and HW#4 available.
• 05/10: slides for Software Testing available.
• 05/09: review forms for the second preliminary demo presentations: Evaluation by Individual Reviewer and Group-for-Group Comments.
• 04/26: HW#4 due 2:00PM 05/03.
• 04/12: slides for Web Application Security available.
• 04/12: review forms for the first preliminary demo presentations: Evaluation by Individual Reviewer and Group-for-Group Comments.
• 03/29: HW#3 due 2:20PM 04/06.
• 03/29: slides for Domain Modeling available (revised 04/02).
• 03/22: slides for Design Document and an example design document available.
• 03/17: review forms for the proposal presentations: Evaluation by Individual Reviewer and Group-for-Group Comments.
• 03/15: slides for Advanced Web Programming available.
• 03/09: Term Project finalized.
• 03/09: HW#2 due 2:00PM 03/15.
• 03/08: slides for Chrome DevTools available.
• 03/08: slides for UML Diagrams available.
• 03/08: slides for Basics of Web Programming (from Year 2021) available.
• 03/01: Draft of Term Project available for discussions, to be finalized on 03/08.
• 03/01: slides for An Overview of Software Modeling and UML available.
• 02/25: HW#1 (attachment: zipped hw#1.txt) due 2:00PM 03/01.
• 02/22: slides for Git available.
• 02/22: slides for Course Introduction available.
• 02/18: this website created to complement the NTU COOL site for this course.

Yih-Kuen Tsay (蔡益坤), Room 1108, Management II, 3366-1189, Xtsay@ntu.edu.twX (between the enclosing pair of X's).

Jeffrey CH Liu (劉智雄, Appier), Clement CW Su (蘇志文, IBM), Scar Su (蘇瑞亨, 叡揚), Chih-Pin Tai (戴智斌, 創炎/Traiwan出來玩), Ming-Hsien Tsai (蔡明憲, 國家資通安全研究院), and Ching-Lin Yu (游景麟, Google).

Wednesday 2:20-5:20PM, Room 302, College of Management, Building 2.

Tuesday 1:30-2:00PM, Wednesday 1:30-2:00PM, or by appointment, Room 1108, Management Building 2.

Same as the instructor.

Object-Oriented Programming and Database Management.

Class notes and selected readings.

We will start with an overview of the typical software development process and relevant issues and then study in greater details some fundamental elements of software modeling, design, and verification, along with several software productivity tools and development practices. To practice applying these methods and tools, we will carry out a term project that involves the development of a large Web application. We will also study Web application programming techniques and security, to better prepare for the project.

• Introduction (2/3 week: 02/22a)
  Overview of software requirements, development process, design methods, verification
  [slides]
• Productivity Tools: Version Control with Git (1/3 week: 02/22b) [slides]
• Software Modeling: An Overview of UML (2/3 week: 03/01a)
  Introduction, basics of modeling, overview of the UML
  [slides]
• Term Project: Initial Discussions (1/3 week: 03/01b) [Draft]
• Software Modeling: UML Diagrams (2/3 week: 03/08a)
  Structural modeling (class diagrams, classifiers, interfaces, packages), behavioral modeling (interactions, use case diagrams, interaction diagrams, activity diagrams), architectural modeling (collaborations, deployment diagrams), advanced structural modeling (object diagrams, components), advanced behavioral modeling (events, state machines, processes and threads, timing constraints)
  [slides]
• Productivity Tools: Chrome DevTools (1/3 week: 03/08b) [slides]
• Software Implementation: Advanced Web Programming (1 week: 03/15) [basics, advanced,examples]
• Term Project: Proposal Presentations (1/3 week: 03/22a)
  
• Software Development Practice: Design Document (2/3 week: 03/22b)
  Design document introduction, high level design document, implementation level design document, design document for agile development
  [slides, An Example Design Document]
• Software Modeling: Domain Modeling (1 week: 03/29)
  Introduction, mathematical preliminaries, and basic and higher abstractions [slides]
  
• Term Project: First Preliminary Demos (1/3 week: 04/12a)
  
• Software Security: Web Application Security (2/3 week: 04/12b)
  Dynamic Web pages, client-side scripts, security vulnerabilities, vulnerabilities detection and prevention
  [slides]
• Productivity Tools: Debuggers (1/3 week: 04/19a) [slides]
• Software Design: Design Patterns (1 and 2/3 weeks: 04/19b, 04/26)
  Why design patterns, introduction to creational, structural, and behavioral patterns, GoF patterns
  [slides, code examples]
• Software Development Practice: Agile Development in Practice (1 week: 05/03)
  Principles for building an agile team, essentials of scrum, kanban, and scrumban, DevOps, and engineering culture
  [slides]
• Term Project: Second Preliminary Demos (1/3 week: 05/10a)
  
• Midterm Discussions (or Make-Up Lecture) (2/3 week: 05/10b)
• Software Verification: Testing (1 week: 05/17)
  [slides]
• Formal Specification: Formal Logic and Correctness Requirements (.5 week: 05/24a)
  Motivation, program correctness, propositional and first-order logics (propositions, proofs, theorems, predicates, models)
  [slides]
• Formal Verification: Verification of Programs with Frama-C and ACSL (.5 week: 05/24b)
  [slides: Hoare Logic, Frama-C and ACSL]
• Term Project: Final Presentations (2023/05/31)
• Final Exam (2023/06/07)

Homework 10%, Attendance/Participation 10%, Term Project 50%, Final 30%.

1. Thinking Above the Code, L. Lamport, Microsoft Research Faculty Summit 2014.
2. Software Requirements and Specifications: A Lexicon of Practice, Principles and Prejudices, M. Jackson, Addison-Wesley, 1995.
3. Agile software development, Wikipedia.
4. Git.
5. Eclipse, The Eclipse Foundation open source community website.
6. The UML Resource Page, OMG.
7. UML Use Case Diagram Tutorial, YouTube.
8. How to Make a UML Sequence Diagram, YouTube.
9. The Unified Modeling Language User Guide, 2nd Edition, G. Booch, I. Jacobson, and J. Rumbaugh, Addison-Wesley, 2005.
10. The OWASP Website. (Note: a website dedicated to Web application security.)
11. Analysis Patterns: Reusable Object Models, M. Fowler, Addison-Wesley, 1997.
12. Design Patterns: Elements of Reusable Object-Oriented Software, E. Gamma, R. Helm, R. Johnson, and J. Vlissides, Addison-Wesley, 1995.
13. The Formal Methods Page, J. Bowen. (Note: this Web portal provides links to numerous formal methods and tools.)
14. Logic in Computer Science: Modelling and Reasoning about Systems, M. Huth and M. Ryan, Cambridge University Press, 2004.
15. Logic for Computer Science: Foundations of Automatic Theorem Proving, J.H. Gallier, Harper & Row Publishers, 1985. (Note: follow the link to author's free download site.)
16. Object Constraint Language, Version 2.4, OMG, 2014.
17. Software Abstractions: Logic, Language, and Analysis, D. Jackson, MIT Press, 2006.
18. Verification of Sequential and Concurrent Programs, 3rd Edition, K.R. Apt, F.S. de Boer, and E.-R. Olderog, Springer, 2009.
19. Frama-C.
20. The SPIN Model Checker: Primer and Reference Manual, G.J. Holzman, Addison-Wesley, 2003.
21. Spin.
22. Java Pathfinder.

[Midterm 2004, Solutions]
[Final 2004]
[Midterm 2006, Solutions]
[Final 2006]
[Midterm 2008]
[Midterm 2009]
[Midterm 2010]
[Midterm 2011]
[Midterm 2012]
[Final 2013]
[Final 2014]
[Final 2015]
[Final 2016]
[Final 2017]
[Final 2020]
[Final 2021]
[Final 2022]