Transcript Document
Sixteenth Meeting 6:30 – 9:20 pm, Thursday, September 20, 2001 Review - Looking Forward (from Part IV, Chapter 15 of Royce’ book) Final Examination Review –The Four Parts of the Course • Software Management Renaissance – The conventional software management process. – Five improvements to make the waterfall process work. • A Software Management Process Framework – Phases – Artifacts – Workflows – Checkpoints • Software Management Disciplines – Planning – Organization – Automation – Process control and instrumentation – Tailoring • Looking Ahead – Modern project profiles – Next-generation software economics – Modern process transitions Topics for Today • • • • • Continuous Integration Early Risk Resolution Evolutionary Requirements Teamwork Among Stakeholders Top Ten Software Management Principles Modern Practice – Resolve These Issues • Protracted integration and late design changes. • Late risk resolution. • Analysis paralysis due to requirementsdriven design. • Adversarial stakeholder relationships. • Focus on documents rather than product. Basic Solution • • • • Continuous integration. Early risk resolution. Evolutionary requirements. Teamwork among stakeholders. Modern Project Profile Conventional versus Modern Workflows The 80/20 Rule • 80% of engineering for 20% of requirements. – Understand the 20% before committing full resources. • 80% of cost due to 20% of components. – Do the 20% components first. • 80% of errors caused by 20% of components. – Do the 20% components first. • 80% of scrap and rework caused by 20% of changes. – Do change-critical 20% first. • 80% of resources for 20% components. – Do 20% components first. • 80% of progress by 20% of people. – Make best possible initial team. Risk Exposure Evolutionary Requirements • Old Way – Requirements were further subdivided, and again, until very lowest level. Then, the design was accomplished by making components to match the low level requirements. This leads to functional design which is traceable to requirements, but is brittle and non-optimal. • New Way – Use top-level requirements to derive an architecture first. Then develop design. Finally, do requirements traceability. Software Component Organization Teamwork Among Stakeholders • Old Way – Distrust, lack of understanding regarding requirements and impact. Non-optimal products. • New Way – An iterative process, collaborative with stakeholders, so that balance between requirements and development is achieved. • Depends on demonstrations, extension to stakeholder domains. Major Milestone Results Royce’ Top Ten Principles for a Modern Process 1. Architecture first. 2. Iterative process. 3. Component-based development. 4. Change management environment. 5. Round-trip engineering. 6. Use model-based notation for artifacts. 7. Instrument the process for objective quality control. 8. Demonstration-based approach. 9. Release iterations with evolving level of detail. 10. Use a configuration process that is scalable for improved ROI. Balanced Application of Modern Principles Sample Final Exam Do the 7 questions as indicated from the list below. Questions to answer: __, __, __, __, __, __, __. - 1. Discuss briefly the four major milestones of a modern software development process. – 2. Discuss briefly the primary purpose of each of the four major milestones. – 3. Discuss briefly the six topics of periodic status assessment reviews. – 4. Discuss briefly the similarities and the differences of top-level organization of a conventional WBS and the top-level organization of a modern WBS. – 5. Discuss briefly the similarities and the differences between the four steps for a top-down cost and schedule estimate and the three steps for a bottom-up cost and schedule estimate. – 6. Discuss briefly the similarities and the differences of the contents of the iterations in each of the four development phases. Sample Final Exam (cont’d) –7. Discuss briefly the similarities and the differences between the Line-of.-Business organization and the Software Project organization. –8. Discuss briefly the responsibilities of the software management organization. –9. Discuss briefly the types of automation tools which should be used. –10. Discuss briefly the elements of organization policy. –11. Discuss briefly the elements of organization environment. –12. Discuss briefly the pros and cons of extension to the stakeholder environment. Sample Final Exam (cont’d) –13. Discuss briefly the three core management metrics. –14. Discuss briefly the four core quality metrics. –15. Discuss briefly the three primary causes of excessive personnel attrition. –16. Discuss briefly the dimensions and priorities for tailoring software projects. –17. Discuss briefly the differences in tailoring for large, contract projects versus small, commercial projects. –18. Discuss briefly what you have learned in this course about software project management.