1. |
|
Ch.1. Introduction to Software Engineering |
Software (Engineering) Failures |
|
2. |
|
Ch.1. Introduction to Software Engineering |
what is software Engineering? |
|
3. |
|
Ch.1. Introduction to Software Engineering |
SE concepts, SE Development Activities |
|
4. |
|
Ch.3. Project Organization and Communication |
Introduction Ariane 501 |
|
5. |
|
Ch.2. Modeling with UML |
An overview of UML |
|
6. |
|
Ch.4. Requirements Elicitation |
Introduction Requirements Elicitation |
|
7. |
|
Ch.4. Requirements Elicitation |
Requirement Elicitation Activities |
|
8. |
|
Ch.4. Requirements Elicitation |
Managing Requirement Elicitation, ARENA Case study |
|
9. |
|
Ch.5. Analysis |
overview of analysis, Analysis activities |
|
10. |
|
Ch.5. Analysis |
Interaction Diagrams (Example : Two Button watch, Sequence diagrams) |
|
11. |
|
Ch.5. Analysis |
Analysis activities : from use cases to objects |
|
12. |
|
Ch.5. Analysis |
Analysis Document, Identifying Entity objects |
|
13. |
|
Ch.6. System Design: Decomposing the System |
Sequence diagrams example,
System design introduction: A Floor plan example |
|
14. |
|
Ch.6. System Design: Decomposing the System |
System design concepts |
|
15. |
|
Ch.6. System Design: Decomposing the System |
System design activities: From Objects to subsystems, Identifying design goals |
|
|
|
Formal Verification |
Formal Verification, Intel pentium FDIV bug, Toyota, Specification&counterexample |
|
|
|
Ch.6. System Design: Decomposing the System |
Architectural design decision, Architectural Patterns |
|
|
|
Ch.7. System Design: Addressing Design Goals |
Introduction: A redundancy |
|
|
|
Ch.7. System Design: Addressing Design Goals |
Reviewing System Design, Identifying Boundary conditions, Software Architecture |
|
|
|
Ch.7. System Design: Addressing Design Goals |
Software process models |
|
|
|
Ch.3. Agile Software Decelopment [lan Sommerville] |
Agile methods |
|