1. COMP 474 Software Engineering Professor William L. Honig

2. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Software Processes Coherent sets of activities for specifying, designing, implementing and testing software systems

3. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Waterfall model

4. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Waterfall model phases Requirements analysis and definition System and software design Implementation and unit testing Integration and system testing Operation and maintenance The drawback of the waterfall model is the difficulty of accommodating change after the process is underway

5. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Waterfall model problems Inflexible partitioning of the project into distinct stages This makes it difficult to respond to changing customer requirements Therefore, this model is only appropriate when the requirements are well-understood

6. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering The V Model

7. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Evolutionary development Exploratory development –Objective is to work with customers and to evolve a final system from an initial outline specification. Should start with well-understood requirements Throw-away prototyping –Objective is to understand the system requirements. Should start with poorly understood requirements

8. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Evolutionary development

9. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Spiral development Process is represented as a spiral rather than as a sequence of activities with backtracking Each loop in the spiral represents a phase in the process. No fixed phases such as specification or design - loops in the spiral are chosen depending on what is required Risks are explicitly assessed and resolved throughout the process

10. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Spiral model of the software process

11. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Spiral model sectors Objective setting –Specific objectives for the phase are identified Risk assessment and reduction –Risks are assessed and activities put in place to reduce the key risks Development and validation –A development model for the system is chosen which can be any of the generic models Planning –The project is reviewed and the next phase of the spiral is planned

12. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering ISO 9000 ISO = International Standards Organization A “Quality Assurance System” For all kinds of business (not just software) ISO 9000-3 is adapted especially for software

13. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Reuse-oriented development Based on systematic reuse where systems are integrated from existing components or COTS (Commercial-off-the-shelf) systems Process stages –Component analysis –Requirements modification –System design with reuse –Development and integration This approach is becoming more important but still limited experience with it

14. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Reuse-oriented development

15. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Extreme programming New approach to development based on the development and delivery of very small increments of functionality Relies on constant code improvement, user involvement in the development team and pairwise programming

16. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Cycle Two Demonstrations – In Class Content: –Introduction –Demonstration of Functionality of your Product (Most Important) –Summary of Project Metrics and Your View of QUALITY –Any thing else you find interesting… Logistics: –At least 3 team members Participate –Plan Ahead; Use Time Wisely; 20 minute limit –Arrange to have your demonstration work in classroom!

17. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Cycle Two Grading Criteria Class Demonstration: – Functionality – Completeness of Project – Software Techniques – Technology Used – Software Engineering – Evidence of Process – Evidence of Teamwork – Presentation Organization and Style Product Delivery: – Configuration Management – Ability to Deliver all Pieces – Documentation and Organization – Final TSPi Data and all Forms, Reports

18. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Cycle Two Awards Celebration The last class session, just like in industry, will be an opportunity for celebration for the ON TIME completion of the project : –Recognition of all the good work –In Class Team Presentations on Process & Teamwork –Opportunity to give serious or funny awards to team mates –We will have some food (I will bring some, you can too if you wish) Price of Admission: –ALL work done before last class Project Notebook Complete Project Handover Complete NO MORE TSPi work! –EVERYONE has at least one award to give to some team mate

19. Dr. William L. Honig Copyright 2008 COMP 474 Software Engineering Key Topics - Process Concept of “process”, life cycle Software process models –Waterfall model –V model –Spiral model Process modeling (high level concept only)