The Software Process CpSc 372: Introduction to Software Engineering Jason O. Hallstrom Authorship Disclaimer. These slides are intended to serve as teaching instruments for an undergraduate course in Software Engineering. While the slides were formatted by Dr. Hallstrom, the content is compiled from other sources, including the readings listed on the course website, Dr. Pressman’s Software Engineering textbook, and various internet materials. In almost every case, the ideas belong to someone other than Dr. Hallstrom. Indeed, text is often quoted verbatim without an explicit citation (to improve the readability of the slides). The original authors retain all copyrights. If you are interested in citing any of the material in these slides, please contact Dr. Hallstrom for the original source(s). DO NOT CITE THIS PRESENTATION. THE CONTENT SHOULD NOT BE ATTRIBUTED TO DR. HALLSTROM. SEE DR. HALLSTROM IF YOU HAVE ANY QUESTIONS.

CpSc 372 Overview of Software Engineering Software requirements are embodied knowledge that is initially dispersed, tacit, latent, and incomplete. It should do X. It should do Y. I’m not sure… Software Engineering A quality focus Process Methods Tools Software engineering encompasses a process, management and technical methods, and tools.

CpSc 372 Generic Software Engineering Phases The definition phase  What product is going to be built? The development phase  How will the product be built, and how will it be tested? The support phase  Incorporate changes from the four sources of change. Correction Adaptation Enhancement Prevention

CpSc 372 CMM: Measuring Process Maturity (i) Level 1: Initial  Chaotic; few processes defined; success depends on individual effort Level 2: Repeatable  Basic processes established; earlier successes repeatable with similar applications Level 3: Defined  Processes documented and standardized; all projects use documented processes Level 4: Managed  Detailed quality measures are collected; processes and products are quantitatively understood and controlled Level 5: Optimizing  Continuous improvement through quantitative feedback and testing of innovative ideas and technologies

CpSc 372 CMM: Measuring Process Maturity (ii) Level 2: Repeatable  KPA: Configuration management  KPA: Quality assurance  KPA: Subcontract management  … … To determine an organization’s process maturity level, the SEI defines key process areas (KPA) – categories of competency – that must be satisfied at each level. Each KPA is evidenced by key practices – policies, procedures, and activities that support the goal of the KPA. Some key practices count more than others in assessing whether the goals of the KPA are being met – these key practices are referred to as key indicators.