Your SlideShare is downloading. ×
0
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Ch2   pressman
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Ch2 pressman

1,263

Published on

roger s pressman

roger s pressman

Published in: Education, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,263
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
63
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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-07CS350 Intro. to SESpring 2008 1
  • 2. A Layered Technology Software Engineering g g A set of Forms the basic tools basis/context forprinciples management of methods SW project process model a “quality” focus Try increasingly more effective approachesCS350 Intro. to SESpring 2008 2
  • 3. Why Is Process Important?Every organization tried to “get the fat” out of industrial get fatprocesses for more than a century Ex. Toyota’s cost reduction for vehicle manufacturingProcess helps us order our thinikng by defining commonactivities 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 HelpsA process is about incorporating discipline into routineactivities to check everything that was supposed to bedone 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 toincorporate individual wisdom/guidance into the way theorganization works CS350 Intro. to SE Spring 2008 4
  • 5. A Process FrameworkProcess 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 DeploymentCS350 Intro. to SESpring 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 gCS350 Intro. to SESpring 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 teamCS350 Intro. to SESpring 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 ftC bilit Maturity Model for Software bbecamedominant and there appeared too many CMMs for [*]Therefore, U.S. Defense Department and SoftwareEngineering Institute @ CMU developed a commonand 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 intothe way the organization works y g 1. Individual learning: Knowledge resides within individuals and may be informally shared2.2 Group learning: Knowledge is explicitly collected and shared within groups such as teams or projects, supporting better performance within the group3.3 Organizational learning: Group- Group-based knowledge is collected and standardized, and mechanisms standardized, exist that encourage its use across related groups4.4 Quantitative learning: The organizational knowledge tranfer and use are measured, and decisions measured, are made based on empirical information5. 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: OptimizedSpecific goals establish the characteristics that must exist if theactivities 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 SESpring 2008 11
  • 12. Process AssessmentThe process should be assessed to ensure that it meetsa set of basic process criteria that have been shown tobe 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:2000CS350 Intro. to SESpring 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 motivatesCS350 Intro. to SESpring 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 errorsCS350 Intro. to SESpring 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 processCS350 Intro. to SESpring 2008 15

×