1. How Software Projects Start SW projects start with a need. We need to keep better data on the students in the CSCE Dept. I heard that one of our competitors is sending customers their bills by email. If we can delay paying some bills, then we can keep the money invested earning interest. Our payroll system was written in 1975 and has a 1,000 patches.

2. The Software Engineering Process Communication – with the stakeholders to determine requirements Planning – the tasks, the risks, the resources, work products produced, and a work schedule Modeling – So all can better understand the requirements and design Construction – Coding and testing Deployment – Put into operation and obtain feedback from users

3. Communication Task List small project 1.Get list of stakeholders 2.Get stakeholders to an informal meeting 3.Ask each stakeholder to make a list of features and functions needed or required. 4.Discuss requirements and build a final list. 5.Prioritize requirements 6.Note areas of uncertainty 7.Often process must iterate before final

4. Communication Task List Large projects 1.List of stakeholders 2.Interview each stakeholder 3.Preliminary list of functions and features 4.Schedule series of meetings 5.Conduct meetings 6.Produce user scenarios for each meeting 7.Refine scenarios based on feedback 8.Build revised list of requirements

5. Communication Task List Large projects (cont) 9. Prioritize requirements 10. Package requirements so they can be delivered incrementally 11. Identify constraints and restrictions on system. 12. Discuss methods for validating the system

6. Umbrella Activities Overlay entire process Project tracking and control Risk management Formal technical reviews Measurement of process, project and product Software Configuration Management – manage effects of change throughout the process Reusability management – use and create reusable components Work Product Preparation and Production – the models, documents, logs, forms and lists