Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.  adapts to meet needs of software engineers and managers. n Different types of projects require different software processes. n Best indicators of how well a process worked are the quality, timeliness, and long-term viability of the resulting software product.

Software Processes n What is a process?  Sequence of steps required to develop or maintain software n Characteristics  prescribes major activities  constraints and controls apply to activities, resources, and products  utilizes resources, subject to constraints such as schedule, to produce intermediate and final results  constraints on activities: time, budget, tools  controls on activities: config. mgmt, reports

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 3 A Process Framework Process framework Framework activities work tasks work products milestones & deliverables QA checkpoints Umbrella Activities

Common Process Framework Activities n Communication n Planning n Modeling  Analysis of requirements  Design n Construction  Code generation  Testing n Deployment

Umbrella Activities n Software project tracking and control n Formal technical reviews n Software quality assurance n Software configuration management n Work product preparation and production (activities to create models, documents, logs, forms, lists, etc.) n Reusability management (defines criteria for work product reuse and establish mechanisms to achieve component reuse) n Measurement n Risk management

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009). Slides copyright 2009 by Roger Pressman. 6 A Generic Process Model

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009). Slides copyright 2009 by Roger Pressman. 7 Process Flow

8 Identifying a Task Set A task set defines the actual work to be done to accomplish the objectives of a software engineering action.  A list of the task to be accomplished  A list of the work products to be produced  A list of the quality assurance filters to be applied

Attributes for Comparing Process Models n Overall flow and level of task dependencies n Degree to which work products are identified and required within each framework activity n Manner in which quality assurance activities are applied n Manner in which project tracking and control activities are applied n Overall degree of detail and rigor of process description n Degree to which stakeholders are involved in the project n Level of autonomy given to project team n Degree to which team organization and roles are prescribed

Process Assessment n SPICE (ISO/IE15504) standard defines a set of requirements for process assessment n ISO 9001:2000 for Software defines requirements for a quality management system that will produce higher quality products and improve customer satisfaction

Software Engineering Institute (SEI) Capability Maturity Model Integration (CMMI) n Level 0: Incomplete (process is not performed) n Level 1: Performed (tasks are being conducted) n Level 2: Managed (tasks and products are monitored, reviewed, and evaluated for conformance to process description) n Level 3: Defined (processes documented, standardized, and integrated into organization-wide software process) n Level 4: Quantitatively Managed (software process and products are quantitatively understood and controlled using detailed measures) n Level 5: Optimizing (continuous process improvement is enabled by quantitative feedback from the process and testing innovative ideas)

Team Software Process n Objectives  Build self-directed teams that plan and track their work, establish goals, and own their processes and plans  Show managers how to coach and motivate their teams and maintain peak performance  Accelerate software process improvement by making CCM Level 5 behavior normal and expected  Provide improvement guidance to high-maturity organizations  Facilitate university teaching of industrial team skills

Team Software Process n Scripts for Project Activities  Project launch  Design  Implementation  Integration and system testing  Postmortem