高级软件工程课件第二节.pptVIP

Chapter 2Process: A Generic View Chapter Overview What? A software process - a series of predictable steps that leads to a timely, high-quality product. Who? Managers, software engineers, and customers. Why? Provides stability, control, and organization to an otherwise chaotic(无秩序的) activity. Steps? A handful of activities are common to all software processes, details vary. Work product? Programs, documents, and data. Correct process? Assessment, quality deliverable. A Layered Technology Software Engineering A Process Framework Umbrella Activities Software project management Formal technical reviews Software quality assurance Software configuration management Work product preparation and production Reusability management Measurement Risk management Framework Activities Communication Planning Modeling Analysis of requirements Design Construction Code generation Testing Deployment The Process Model:Adaptability The framework activities will always be applied on every project ... BUT The tasks (and degree of rigor) for each activity will vary based on: the type of project characteristics of the project common sense judgment; concurrence of the project team The CMMI The CMMI defines each process area in terms of “specific goals” and the “specific practices” required to achieve these goals. Specific goals establish the characteristics that must exist if the activities implied by a process area are to be effective. Specific practices refine a goal into a set of process-related activities. Personal Software Process (PSP) Recommends five framework activities: Planning High-level design High-level design review Development Postmortem Stresses the need for each software engineer to identify errors early and as important, to understand the types of errors Team Software Process (TSP) Each project is “launched” using a “script” that defines the tasks to be accomplished Teams (of 2 to 20 engineers) are self-directed: Plan and track work, set goals, own processes and plans Mea