1. Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends upon individual effort

2. Software Engineering II Lecture 2 Fakhar Lodhi

3. Level 2 Level 2 – Repeatable: Basic project management processes are established to track cost, schedule, and functionality. The necessary project discipline is in place to repeat earlier successes on projects with similar applications

4. Level 3 Level 3 – Defined: The software process for both management and engineering activities is documented, standardized, and integrated into an organizational software process. All projects use a documented and approved version of the organization’s processes for developing and supporting software

5. Level 4 Level 4 – Managed: Detailed measures for software process and product quality are controlled. Both the software process and products are quantitatively understood and controlled using detailed measures

6. Level 5 Level 5 – Optimizing: Continuous process improvement is enabled by qualitative feedback from the process and from testing innovative ideas and technologies

7. Key Process Areas (KPAs) The KPAs describe those software engineering functions that must be present to satisfy good practice at a particular level. Each KPA is described by identifying the following characteristics

8. Software Life-Cycle Steps Life-cycle model (formerly, process model) –Requirements phase –Specification phase –Design phase –Implementation phase –Integration phase –Maintenance phase –Retirement

9. Different Lifecycle Models Build-and-fix model Waterfall model Rapid prototyping model Incremental model Extreme programming Synchronize-and-stabilize model Spiral model Object-oriented life-cycle models Comparison of life-cycle models

10. Build and Fix Model Build first version Modify until client is satisfied Maintenance phase Retirement Development Maintenance

11. Waterfall Model Requirement Definition System and Software Design Implementation and Unit Testing Integration and System Testing Operation and Maintenance

12. Waterfall Model Requirement Definition System and Software Design Implementation and Unit Testing Integration and System Testing Operation and Maintenance

13. Rapid Prototyping Model Requirement Definition System and Software Design Implementation and Unit Testing Integration and System Testing Operation and Maintenance Rapid Prototyping

14. The Process A software process is a road map that helps you create a timely, high quality result. It is the way we produce software Provides stability and control Work Product –Programs, documents, and data produced as a consequence of the software engineering activities

15. Process Maturity SEI – Software Engineering Institute 5 maturity levels Capability Maturity Model (CMM)

16. INITIAL – Ad hoc Process REPEATABLE – Project Management DEFINED – Process Definition MANAGED – Process Measurement OPTIMIZED – Process Improvement CMM Maturity Levels

17. Goals Abilities Key Process Areas (KPAs) Methods for monitoring implementation Commitments Activities Methods for verifying implementation

18. Software Configuration Management Software Quality Assurance Software subcontract Management Level 2 KPAs

19. Software project tracking and oversight Software project planning Requirement management Level 2 KPAs - Continued

20. Peer reviews Inter-group coordination Software product Engineering Integrated software management Level 3 KPAs

21. Level 3 KPAs - Continued Training program Organization process management Organization process focus

22. Process change management Technology change management Defect prevention Level 5 KPAs

23. 1.Vision – focus on why 2.Definition – focus on what 2. Development – focus on how 3. Maintenance – focus on change Software Engineering Phases VisionDefinitionDevelopmentMaintenance