Software Process Models S/E 1 Waterfall Model S/E 2

Table of Contents Phases

System analysis
– Waterfall Model Requirements Problem Description
– Waterfall Model Phases
Specification Problem Definition
– Waterfall Model Phases (cont)
– Waterfall Model Phases (cont) High Level Design Logical Design
Modular Composition
– Waterfall Model Phases (cont) Physical Design Low Level Design
– Spiral Model Step-Wise Refinement
Top-Down Design Dependent Design
– Spiral Model (cont) Coding Prog. Language
Operating Sys.
Integration
System Reliability
Testing

feedback loops Deployment

Advantages / Disadvantages Maintenance

– Most-widely used process model
– Controls schedules, budgets & documentation
– Tends to favor well-understood system aspects over poorly
understood system components
– Does not detect development areas behind schedule early in the
lifecycle stages.
Document-driven process
– Deliverables: documents produced at the end of each phase, usually
in accordance to contract deadlines

Computer Science Dept Va Tech August, 1998 Intro Data Structures & SE ©1995-1998 Barnette ND, McQuain WD Computer Science Dept Va Tech August, 1998 Intro Data Structures & SE ©1995-1998 Barnette ND, McQuain WD
Waterfall Model: Phases S/E 3 Waterfall Model: Phases (cont) S/E 4

Requirements Coding and Debugging (implementation)

– A statement of the functions and behavior of the system required by – Translation of design into a programming language
its users & operators – Indispensable Programmer Phenomena
– General Requirements – Program Unit Notebooks
† Defines broad & detailed objectives of the system 1. Documents programmer‘s work activities
† e.g., reliable, correct, efficient, user-friendly, expandable 2. Maintains current unit (module) documentation
– Gives relationship of Qualitative & Quantitative System Goals 3. Passed from programmer to programmer during development
Specification
– Listing of specific, measurable behavioral system constraints that
satisfy system requirements
– Clearly communicates system operations with end user(s)
† complete, unambiguous, minimal, understandable, testable
– Cross-reference indexed to requirement items
– Defines the design validation & final system testing criteria
– Provides chief mechanism for estimating the project’s progress
Design: Representation or model of a system
High Level Structure Charts,
Data-flow Diagrams less
Design
User-interface design
Decision Tables
Low Level PDLs (Prog Design Langs)
Design HIPO
(Hierarchy Input Processing Output)

Details Internal Code Processing:

algorithms, data structures,
control flow

Code Programming more

Level Language
Detail

Computer Science Dept Va Tech August, 1998 Intro Data Structures & SE ©1995-1998 Barnette ND, McQuain WD Computer Science Dept Va Tech August, 1998 Intro Data Structures & SE ©1995-1998 Barnette ND, McQuain WD
 Waterfall Model: Phases (cont) S/E 5 Waterfall Model: Phases (cont) S/E 6

Coding and Debugging (implementation) Integration and Testing

– Data Dictionary: records information and physical format details of – Unit testing: individual modules (functions) are tested separate from
all structures, variables, files . . . other modules
– Integration testing: system modules are tested together

Deployment & Maintenance

– Requires previous phases to be repeated
– Makes up 70%-90% of total system cost
– Majority of maintenance time (50%) spent on system understanding
-> system documentation
– Maintenance Tasks
† collection, analysis and prioritization of user trouble reports
† new system release installations
† documentation (user’s manuals) changes
† configuration control issues

– Data Dictionary performs documentation mapping

Data Objects ==> System Structures
“ ” ==> Parent Objects
“ ” ==> Module Routines
– Data Dictionary Entry
Name: from the data-flow diagram or structure chart
Routine Usage: routines that access the object
Purpose: explanation
Derivation: where the data that the items holds comes
from ex. files, user, other entries . . .
Subitems: Record components Notes: comments

Computer Science Dept Va Tech August, 1998 Intro Data Structures & SE ©1995-1998 Barnette ND, McQuain WD Computer Science Dept Va Tech August, 1998 Intro Data Structures & SE ©1995-1998 Barnette ND, McQuain WD
Spiral Model S/E 7 Spiral Model (cont) S/E 8

The Spiral Software Process Model Diagram Prototype Based

– Prototype: a limited, semi-functional, task restricted, partially
operational system
† Analogous to a model or mockup that allows evaluation of
development alternatives before commitment
– Rapid Prototyping Systems
† Authoring/scripting (multimedia) systems used to quickly develop
multiple interfaces for user evaluation, cannot serve as a kernel for future
iterative system prototype development
† Users tend to view prototypes as final versions of the system

Mimic
– Risk analysis produces a risk-resolution strategy
† Feasibility Study: determination of a strategy achieving set goals and
requirements within stated constraints.
‡ Address development factors of expertise, experience,
resources and motivation
† Extension of cost/benefit analysis
‡ cost & benefits are estimated for best & worst case
Barry Boehm, “A Spiral Model of Software Development and Enhancement”, Computer, (May
outcomes which are multipled by their probability of
1988), pp. 61-72, © 1988 IEEE. occurrence giving an expected value.
‡ Decisions on strategies are made to minimize cost and
– Development phases reiterates through four cycles: maximize benefits
† Set goals and determine constraints for the phase
† Evaluate and resolve risks for the phase – Cycles are modified to concentrate on different areas of system
† Develop the prototype for the phase development driven by the risk-resolution plan
† Plan the next stage activities – Spiral model tends to behave like other process models due to
– Step 2 involves a Risk Analysis that identifies: differing cycles
less understood system areas
systems areas that pose the greatest jeopardy to development

Computer Science Dept Va Tech August, 1998 Intro Data Structures & SE ©1995-1998 Barnette ND, McQuain WD Computer Science Dept Va Tech August, 1998 Intro Data Structures & SE ©1995-1998 Barnette ND, McQuain WD