Ch2 pressman
2 likes1,618 views
This document discusses software engineering processes and process improvement. It describes a generic process framework with activities like communication, planning, modeling, construction, and deployment. It also discusses umbrella activities like management, quality assurance, and configuration management. The document explains that the CMMI defines capability maturity levels and that processes should be assessed against basic criteria. It introduces the Personal Software Process and Team Software Process approaches.
![The CMMI (1/3)
CMMI stands for “Capability Maturity Model Integrated”
Remember that the process repeatability and predictability are called
“capability maturity”
By the mid-1990’s, the five-level world view of
mid- five-
Capability M t it M d l f S ft
C bilit Maturity Model for Software bbecame
dominant and there appeared too many CMMs for [*]
Therefore, U.S. Defense Department and Software
Engineering Institute @ CMU developed a common
and extensible framework, which is CMMI, a second
framework,
generation of CMMs
CS350 Intro. to SE
Excerpted from “CMMI Survival Guide” by S.Garcia and R.Turner
Spring 2008 9](https://image.slidesharecdn.com/ch2-pressman-110528134143-phpapp01/85/Ch2-pressman-9-320.jpg)
Ch2 pressman
- 1. Chapter 2 Process: A Generic View Moonzoo Kim CS Division of EECS Dept. KAIST moonzoo@cs.kaist.ac.kr moonzoo@cs kaist ac kr http://pswlab.kaist.ac.kr/courses/CS350-07 CS350 Intro. to SE Spring 2008 1
- 2. A Layered Technology Software Engineering g g A set of Forms the basic tools basis/context for principles management of methods SW project process model a “quality” focus Try increasingly more effective approaches CS350 Intro. to SE Spring 2008 2
- 3. Why Is Process Important? Every organization tried to “get the fat” out of industrial get fat processes for more than a century Ex. Toyota’s cost reduction for vehicle manufacturing Process helps us order our thinikng by defining common activities and artifacts Process is a means to capture and transfer the knowledge we gain in developing a particular product Process improvement identify a d dep oy knowledge over large ocess p o e e de y and deploy o edge o e a ge groups. CS350 Intro. to SE Spring 2008 3
- 4. Why Process Improvement Helps A process is about incorporating discipline into routine activities to check everything that was supposed to be done was done Making sure There was sufficient repeatabilitity in the tasks to make future work predictable This process repeatability and predictability are called “capability maturity” maturity” Informally speaking, process improvement is to incorporate individual wisdom/guidance into the way the organization works CS350 Intro. to SE Spring 2008 4
- 5. A Process Framework Process framework Framework activities work tasks work products milestones & d li il deliverables bl QA checkpoints Umbrella A ti iti U b ll Activities CS350 Intro. to SE Spring 2008 5
- 6. Framework Activities Communication Planning Modeling Analysis of requirements Design Construction Code generation Testing Deployment CS350 Intro. to SE Spring 2008 6
- 7. Umbrella Activities Software project management Risk management Software quality assurance q y Formal technical reviews Software configuration management g g Work product preparation and production Reusability management y g CS350 Intro. to SE Spring 2008 7
- 8. 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 CS350 Intro. to SE Spring 2008 8
- 9. The CMMI (1/3) CMMI stands for “Capability Maturity Model Integrated” Remember that the process repeatability and predictability are called “capability maturity” By the mid-1990’s, the five-level world view of mid- five- Capability M t it M d l f S ft C bilit Maturity Model for Software bbecame dominant and there appeared too many CMMs for [*] Therefore, U.S. Defense Department and Software Engineering Institute @ CMU developed a common and extensible framework, which is CMMI, a second framework, generation of CMMs CS350 Intro. to SE Excerpted from “CMMI Survival Guide” by S.Garcia and R.Turner Spring 2008 9
- 10. The CMMI (2/3) Process improvement is to incorporate individual wisdom/guidance into the way the organization works y g 1. Individual learning: Knowledge resides within individuals and may be informally shared 2. 2 Group learning: Knowledge is explicitly collected and shared within groups such as teams or projects, supporting better performance within the group 3. 3 Organizational learning: Group- Group-based knowledge is collected and standardized, and mechanisms standardized, exist that encourage its use across related groups 4. 4 Quantitative learning: The organizational knowledge tranfer and use are measured, and decisions measured, are made based on empirical information 5. Strategic learning: Knowledge collection, transfer, and use are rapid across the organization CS350 Intro. to SE Spring 2008 10
- 11. The CMMI (3/3) The CMMI defines each process area in terms of “specific goals” and the “specific practices” required to achieve these goals specific practices goals. Level 0: Incomplete Level 1: Performed Level 2: Managed Level 3: Defined Level 4: Quantitatively managed Level 5 O ti i d L l 5: Optimized 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. process- CS350 Intro. to SE Spring 2008 11
- 12. Process Assessment 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: SCAMPI (Standard CMMI Assessment Method for Process Improvement) I t) CBA IPI (CMM-Based Appraisal for Internal Process (CMM- Improvement) SPICE (ISO/IEC15504) ISO 9001:2000 CS350 Intro. to SE Spring 2008 12
- 13. Assessment and Improvement Software Process identifies is examined by identifies capabilities modifications to and risk of Software Process Assessment Capability Software Process leads to leads to Determination D t i ti Improvement motivates CS350 Intro. to SE Spring 2008 13
- 14. Personal Software Process (PSP) Recommends five framework activities: Planning High- High-level design High- 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 CS350 Intro. to SE Spring 2008 14
- 15. Team Software Process (TSP) Each project is “launched” using a “script” that p j g p defines the tasks to be accomplished Teams are self-directed self- Measurement is encouraged Measures are analyzed with the intent of improving the team process CS350 Intro. to SE Spring 2008 15