《3.微软如何做软件.pptVIP

How Microsoft Builds Software* Presented by: Ron Norman Society for Software Quality June 23, 1998 Michael A. Cusumano Professor of Strategy Technology Management Sloan School of Management Massachusetts Institute of Technology Richard W. Selby Associate Professor of Computer Science Department of Information Computer Science University of California, Irvine The Challenges Quality problems Delayed deliveries Larger development teams Win 95 had over 200 programmers and testers Software products with millions of lines of source code 11+ million lines of code in Win 95 Development lasting one or more years Product Complexity Components are interdependent Components are difficult to define in early stages of the development cycle Need to proceed with coordination, while allowing flexibility to be creative Need a mechanism to test the product with customers and refine the designs during the development process The need for iterations Users’ needs are difficult to understand Software/hardware changes rapidly It is difficult to design a software system completely in advance Similar to the spiral model and other iterative enhancement development processes Scaling up a flexible, entrepreneurial company Small team style (3-8 developers) Many parallel teams Freedom to evolve designs Synchronize frequently Synch-and-Stabilize Approach Continually synchronize parallel teams Periodically stabilize the product in increments versus once at the end Also known as: milestone process daily build process nightly build process zero-defect process Overview of Synch-and-Stabilize Development Planning Phase Vision Statement - Product Managers Define goals for the new product Priority-order user activities that need to be supported by product features Deliverables: Specification document Schedule and “feature” team formation 1 program manager 3-8 developers 3-8 testers (1:1 ratio with developers) Development Phase Feature development in 3-4 subprojects (lasting 2-4 months each) using fu