Скачать презентацию Software Engineering A Practitioner s Approach 6 e Chapter 2 Скачать презентацию Software Engineering A Practitioner s Approach 6 e Chapter 2

67535c6879b3280cf6df50483467f4f9.ppt

  • Количество слайдов: 13

Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R. S. Pressman & Associates, Inc. 1

A Layered Technology Software Engineering tools methods process model a “quality” focus 2 A Layered Technology Software Engineering tools methods process model a “quality” focus 2

A Process Framework Process framework Framework activities work tasks work products milestones & deliverables A Process Framework Process framework Framework activities work tasks work products milestones & deliverables QA checkpoints Umbrella Activities 3

Framework Activities n n n Communication Planning Modeling n n n Construction n Analysis Framework Activities n n n Communication Planning Modeling n n n Construction n Analysis of requirements Design Code generation Testing Deployment 4

Umbrella Activities n n n n Software project management Formal technical reviews Software quality Umbrella Activities n n n n Software project management Formal technical reviews Software quality assurance Software configuration management Work product preparation and production Reusability management Measurement Risk management 5

The Process Model: Adaptability n n the framework activities will always be applied on The Process Model: Adaptability n n the framework activities will always be applied on every project. . . BUT the tasks (and degree of rigor) for each activity will vary based on: n n n the type of project characteristics of the project common sense judgment; concurrence of the project team 6

The CMMI n n n The CMMI defines each process area in terms of The CMMI n n n 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 processrelated activities. 7

Process Patterns n n n Process patterns define a set of activities, actions, work Process Patterns n n n Process patterns define a set of activities, actions, work tasks, work products and/or related behaviors A template is used to define a pattern Typical examples: n n n Customer communication (a process activity) Analysis (an action) Requirements gathering (a process task) Reviewing a work product (a process task) Design model (a work product) 8

Process Assessment n n The process should be assessed to ensure that it meets Process Assessment n n The process should be assessed to ensure that it meets a set of basic process criteria that have been shown to be essential for a successful software engineering. Many different assessment options are available: n n SCAMPI CBA IPI SPICE ISO 9001: 2000 9

Assessment and Improvement 10 Assessment and Improvement 10

Personal Software Process (PSP) n Recommends five framework activities: n n n Planning High-level Personal Software Process (PSP) n Recommends five framework activities: n n n Planning 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 11

Team Software Process (TSP) n n Each project is “launched” using a “script” that Team Software Process (TSP) n n Each project is “launched” using a “script” that defines the tasks to be accomplished Teams are self-directed Measurement is encouraged Measures are analyzed with the intent of improving the team process 12

The Primary Goal of Any Software Process: High Quality Remember: High quality = project The Primary Goal of Any Software Process: High Quality Remember: High quality = project timeliness Why? Less rework! 13