This course presents a survey of topics in software engineering most relevant to students studying computer science. At the end of the semester, all students will be able to do the following:

1. Identify and differentiate phases of a typical software process and how it relates to the software life cycle and the different software process models.

2. Create functional requirement specifications in the form of use cases and user stories, and differentiate between functional and non-functional requirements.

3. Develop static and dynamic UML diagrams to model both the structural and behavioral aspects of the software system throughout the different phases of the development life cycle.

4. Create a software architecture specification, including subsystem decomposition and subsystem interface descriptions.

5. Communicate and effectively function as a member of a software development team to develop a software system based on its specification and previously created models.

6. As a team, deliver a coherent and professional presentation and demonstration of a functioning software system and the results of its testing.

1. Software engineering and software process (3-hours)
2. Team and project management (2-hours)
3. Requirements elicitation and specification (4-hours)
4. Use case modeling (3-hours)
5. Requirements analysis (4-hours)
6. UML diagrams (4-hours)
7. Static and dynamic modeling (3-hours)
8. System design and architectural styles (4-hours)
9. Design patterns (3-hours)
10. Detailed (object) design (4-hours)
11. Object constraint language (1-hour)
12. Implementation techniques (5-hours)
13. Source code management (2-hours)
14. Persistence and storage systems (2-hours)
15. Verification and testing (3-hours)
16. Software demonstration (3-hours)

Students will gain an understanding of modern software engineering methodologies, including an in-depth study of one of the methodologies. They will be exposed to the full software life-cycle, including requirements specification, analysis, software design, implementation, and testing. The students will implement a large system, following the design and development of one of the studied software methodologies.

Expected Learning Outcomes:

This course presents a survey of topics in software engineering most relevant to students studying computer science. At the end of the semester, all students will be able to do the following: 

1. Identify and differentiate phases of a typical software process and how it relates to the software life cycle and the different software process models. 
2. Create functional requirement specifications in the form of use cases and user stories and differentiate between functional and non-functional requirements.
3. Develop static and dynamic UML diagrams to model both the structural and behavioral aspects of the software system throughout the different phases of the development life cycle.
4. Create a software architecture specification, including subsystem decomposition and subsystem interface descriptions.
5. Communicate and effectively function as a member of a software development team to develop a software system based on its specification and previously created models.
6. Deliver, as a team, a coherent and professional presentation and demonstration of a functioning software system and the results of its testing.

1. Software engineering and software process (3-hours)
2. Team and project management (2-hours)
3. Requirements elicitation and specification (4-hours)
4. Use case modeling (3-hours)
5. Requirements analysis (4-hours)
6. UML diagrams (4-hours)
7. Static and dynamic modeling (3-hours)
8. System design and architectural styles (4-hours)
9. Design patterns (3-hour)
10. Detailed (object) design (4-hours)
11. Object constraint language (1-hours)
12. Implementation techniques (5-hours)
13. Source code management (2-hours)
14. Persistence and storage systems (2-hours)
15. Verification and testing (3-hours)
16. Software demonstration (3-hours)