Chapter 2
Process: A Generic View
1
Chapter Overview
What? A software process - a series of predictable
steps that leads to a timely, high-quality product.
Who? Managers, software engineers, and customers.
Why? Provides stability, control, and organization to
an otherwise chaotic activity.
Steps? A handful of activities are common to all
software processes, details vary.
Work product? Programs, documents, and data.
Correct process? Assessment, quality deliverable.
2
A Layered Technology
Software Engineering
tools
methods
process model
a “quality” focus
3
Software Engineering
Software Engineering: (1) The application of a
systematic, disciplined, quantifiable approach to
the development, operation, and maintenance of
software; that is, the application of engineering to
software. (2) The study of approaches as in (1).
- IEEE Standard 610.12-1990
4
Software process A Process Framework
Process framework
Umbrella activities
framework activity #1 framework activity #2
SE action #1.1 SE action #2.1
tas work tasks
work tas work tasks
work
k
set products
QA points
k
set products
QA points
s milestones
s milestones
SE action #1.2 SE action #2.2
tas work tasks
work tas work tasks
work
k
set products
QA points
k
set products
QA points
s milestones
s milestones
5
Umbrella
Activities
Software project management
Formal technical reviews
Software quality assurance
Software configuration management
Work product preparation and
production
Reusability management
Measurement
Risk management
6
Framework
Activities
Communication
Planning
Modeling
Analysis of requirements
Design
Construction
Code generation
Testing
Deployment
7
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
8
The
CMMI
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 process-related activities.
9
Personal Software Process
(PSP)
Recommends five framework activities:
Planning
High-level design
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
10
Team Software Process (TSP)
Each project is “launched” using a “script”
that defines the tasks to be accomplished
Teams (of 2 to 20 engineers) are self-
directed:
Plan and track work, set goals, own processes and plans
Measurement is encouraged
Measures are analyzed with the intent of
improving the team process (through
coaching, motivation, …)
11
Process Patterns
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:
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)
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
CBA IPI
SPICE
ISO 9001:2000 13
Assessment and Improvement
Software Process
identifies is examined by identifies capabilities
modifications to and risk of
Software Process
Assessment
leads to leads to Capability
Software Process Determination
Improvement
motivates
14
The Primary Goal of Any
Software Process: High Quality
Remember:
High quality project timeliness
Why?
Less rework!
15
