CS472 DAY #5 9/14/04

THE UNIFIED PROCESS

Chapter 3 (Summary)

“The Rational Unified Process: An Introduction, Second Edition,” Philippe Kruchten,

Addison-Wesley 2000, ISBN 0-201-70710-1

“The Unified Software Development Process,” I. Jacobson, G. Booch, & J. Rumbaugh,

Addison-Wesley 1999, ISBN 0-201-57169-2

THE UNIFIED PROCESS is: An O-O Methodology that is combined with

The Iterative & Incremental life-cycle model.

WORKFLOWS

CORE WORKFLOWS / Terminology / Activities (HOW?)
Requirements
(language of client) / Domain
Business Model
Constraints
Activities: Elicitation &
Concept exploration / Chapter 10
Analysis & Design
(language of developers) / CLASS’s/OBJECT’s
Analysis: Definition of sets of classes
(modules) & interactions
Classical analysis mistakes
(ambiguity, incompleteness,
contradictions)
Design: Class algorithms & data structures
Software Project Management Plan / Chapter 11 &12
Chapter 13
Chapter 9
Implementation / Code artifacts / Chapter 14(not 472)
Test / Artifacts / Traceability
Unit testing
Integration testing
Product testing
Acceptance testing / Chapter 6
NOT A CORE WORKFLOW
Postdelivery maintenance / Regression testing / Chapter 15(not 472)

We will NOT cover DOMAIN MODEL, BUSINESS MODEL, or BUSINESS CASE in 472.

PHASES

What are the goals of each phase?

What are the outputs of each phase (Deliverables/Milestones)?

PHASES / Goals / Deliverables/Milestone
Inception / To achieve concurrence among all stakeholders on product objectives (To determine if product is economically viable) / Vision Document
Requirements Specification Document (Initial)
Software Design Document (Preliminary)
Plan (for elaboration phase)
Elaboration / Refine requirements
Refine architecture/design
Refine risk priorities
Produce SPMP / Requirements Specification Document (Complete)
Software Design Document (Complete)
Test Plan/Test code (Initial)
Source code (Initial)
Software Project Management Plan
Construction / Complete the first operational
quality version of product / User Manual(s)
Requirements Specification Document (Complete)
Software Design Document (Complete)
Source code (Complete)
Test plan/Test code (Complete)
Software Project Management Plan
Transition / To ensure that the all
requirements have been met
To move the product to the
user community / Vision document
Requirements Specification Document (Final)
Software Design Document (Final)
User Manual(s)
Source code (Final)
Test plan/Test code/Test Report (Final)

The four main artifacts evolve continuously throughout all phases.

Requirements Specification Document
Software Design Document
Source code
Test plan/Test code

Rational/IBM provides example templates for all documents.

(Templates will be provided for homework in this class)

Vision Document

Vision of requirements

Key features

Main constraints

Requirements Specification Document

Use-case models

Project glossary

List of use-cases in order of decreasing risk

Software Design Document

UML Models

List of architectural concerns in order of decreasing risk


REVIEW

THE ITERATIVE & INCREMENTAL MODEL

(Chapter 2)

INCREMENTS ARE DEFINED IN ORDER OF DECREASING RISK.

(Architectural risks first, implementation risks second, etc.)

ITERATIONS ARE CONDUCTED IN ORDER OF WORKFLOWS, BUT

THE NEED FOR REPETITION IS BASED ON THE FUNDAMENTAL

COMPLEXITY OF THE TASK.

(i.e., Iteration is continued until you have satisfied the goals of the increment)