1. Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 15, Software Life Cycle

2. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2 Figure 15-1, Simple life cycle for software development. «include» ClientEnd userDeveloperProject manager Software development System developmentProblem definitionSystem operation Administrator

3. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3 Figure 15-2, Simple life cycle for software development. System operation activity System development activity Problem definition activity

4. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4 Figure 15-3, Another simple life cycle. System upgrade activity Market creation activity System development activity

5. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5 Figure 15-4, Entity-centered view of software development. Lessons learned document System specification document Executable system Market survey document Software Development

6. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6 Figure 15-5, Activities and products of the simple life cycle of Figure 15-2. Specification Executable system Lessons learned Market survey Problem definition System development System operation ActivityWork product consumes produces consumes produces consumes produces activity document

7. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7 Figure 15-6, Model of the software life cycle. Process Group ActivityWork Product Resource Task Process Money Time Participant consumed by produces Work Unit * * * * Software Life Cycle * *

8. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8 Verification & Validation Process Configuration Management Process Documentation Development Process Training Process Project Monitoring &Ctrl Process S/W Quality Management Process Project Initiation Process Operation & Support Process Maintenance Process Design Process Concept Exploration Process System Allocation Process Requirements Process Implementation Process Installation Process Retirement Process Development processesManagement processesIntegral processes Figure 15-7. Process interrelationships in the IEEE 1074 standard.

9. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9 Requirements Process System Allocation Process Project Initiation Process Concept Exploration Process Design Process Implementation Process Installation Process Operation & Support Process Verification & Validation Process Figure 15-8, The waterfall model of software development is an activity-centered view of the software life cycle.

10. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10 System Requirements Analysis Implementation Preliminary Design Detailed Design Software Requirements Elicitation Operation Client Acceptance Requirements Analysis Unit Test System Integration & Test Component Integration & Test Figure 15-9, V- Model of software development.

11. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11 Figure 15-10, Boehm’s spiral model (Adapted from [Boehm, 1987]).

12. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12 Figure 15-11, Workflows in the unified software life cycle used by Royce. * releases * Design RequirementsImplementation Deployment Unified Process Software Life Cycle Management * Environment Assessment Workflow ArtifactIteration Transition ConstructionInception Elaboration Phase 4 Cycle * Product

13. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13 Figure 15-12, States of a Software System called phases in the Unified Process. Inception Elaboration Construction Transition

14. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14 Figure 15-13, The seven workflows in the Unified Process.

15. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 15 Figure 15-14, Entity-centered life cycle view of the models of the Unified Process. Use case model Analysis model Design model Deployment model Test model Implementation model specified by realized by distributed by implemented by verified by

16. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 16 Figure 15-15, Snapshot of a project issue base. Issues i1 and i5 have been resolved, whereas all other issues are still open. Dependencies among issues indicate that the resolution of an issue can constraint the alternatives for dependent issues. i1:Issue status={Closed} i2:Issue i7:Issue i6:Issue i5:Issue status = {Open} i3:Issue status = {Open} status={Closed} status = {Open}

17. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 17 Figure 15-16, The waterfall model as a special case of the issue-based life cycle model. All issues that belong to the same issue category are contained in the same UML package. In the project status shown in the figure, all the requirements elicitation and analysis issues have been closed; that is, the requirements elicitation and analysis activities have been completed. Analysis System Design Req. Elicitation i1:Issue status={Closed} i2:Issue i7:Issue i6:Issue i5:Issue status={Closed} i3:Issue status={Closed} status = {Open}

18. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 18 Figure 15-17, In a complex project state, all activities can still have some open issues, which means that all activities need to be managed concurrently. Analysis System Design Req. Elicitation i1:Issue status={Open} i2:Issue i7:Issue i6:Issue i5:Issue status={Closed} i3:Issue status={Closed} status={Open} status={Closed} status = {Open}