CS 577b: Software Engineering II

1. CS 577b: Software Engineering II Team Discussions

2. Outline • Iteration Planning • Plan Iteration • Manage Iteration • Assess Iteration • Software Engineering Metrics & Measurements (C) 2011 USC-CSSE

3. Iteration Planning • Plan Iteration • Prioritize Work Items List • Identify and review risks • Assign resources • Manage Iteration • Track progress • Handle exceptions and problems • Identify and review risks • Assess Iteration • Retrospective analysis • Assign tasks based on lesson learned (C) 2011 USC-CSSE

4. Manage Iteration • What are the differences between your current project status and what you planned in the DC Package? • Human resources • Requirements • Architecture • When was the last time you talk to you clients? (C) 2011 USC-CSSE

5. Risk Management

6. Risks Management • Identify the potential risks in the following categories? • What are the current risks that your team have? • Risk Description • Probability of Risk • Size of Loss • Mitigation Strategies (C) 2011 USC-CSSE

7. Prospective vs Retrospective studies • Prospective Study • looks forward in time, e.g. follow the development of a disease. Usually takes a long time. • Retrospective Study • looks backwards and examines exposures to suspected risk or protection factors in relation to an outcome Ref: http://www.statsdirect.com/help/basics/prospective.htm http://www.childrens-mercy.org/stats/definitions/retrospective.htm (C) 2011 USC-CSSE

8. Retrospective Analysis • In previous iteration or in CSCI577a • what went well • what could have gone better • how things could be changed to deliver better results • Action items • Responsible person (C) 2011 USC-CSSE

9. Outline • Iteration Planning • Plan Iteration • Manage Iteration • Assess Iteration • Software Engineering Metrics & Measurements (C) 2011 USC-CSSE

10. Software Metrics (Measurements) • A software metric is a measure of some property of a piece of software or its specifications, in quantitative measurements • Business Operation • Defect trend, requirements churn • Technical measurements http://en.wikipedia.org/wiki/Software_metric http://sunset.usc.edu/classes/cs577b_2001/metricsguide/metrics.html (C) 2011 USC-CSSE

11. Software metrics Software metrics are numerical data related to software development. Metrics strongly support software project management activities. They relate to the four functions of management as follows: • Planning - Metrics serve as a basis of cost estimating, training planning, resource planning, scheduling, and budgeting. • Organizing - Size and schedule metrics influence a project's organization. • Controlling - Metrics are used to status and track software development activities for compliance to plans. • Improving - Metrics are used as a tool for process improvement and to identify where improvement efforts should be concentrated and measure the effects of process improvement efforts. (C) 2011 USC-CSSE

12. Categories of metrics (1/3) (C) 2011 USC-CSSE

13. Categories of metrics (2/3) (C) 2011 USC-CSSE

14. Categories of metrics (3/3) (C) 2011 USC-CSSE

15. Requirements Churn http://www.ibm.com/developerworks/rational/library/4786.html (C) 2011 USC-CSSE

16. (C) 2011 USC-CSSE

17. Systems Engineering Leading Indicators Guide EPI 270-20, Rev. 1.7 Draft, November 10, 2009 (C) 2011 USC-CSSE

18. Iteration Burndown : work left to do versus time http://en.wikipedia.org/wiki/Burn_down_chart (C) 2011 USC-CSSE

19. Iteration Velocity: Unit of works completed in each iteration (C) 2011 USC-CSSE

20. Defect Trends http://www.teknologika.com/blog/category/test-management/ (C) 2011 USC-CSSE

21. Software Engineering Metrics, Linda M. Laird (C) 2011 USC-CSSE

22. Backlog Trend: No. of change request or jobs not done (C) 2011 USC-CSSE

23. (C) 2011 USC-CSSE