an approach for:
Building
Deploying
Maintaining
UP
In
Why UP?
Think
are timeboxed.
Incremental
Iterative:
Iterations
Each iteration involves :
Choosing small subset of requirements.
Quick design, implementation and testing
User quickly see partial system
Rapid , early feedback ( ex: usability tests from
users)
Yes , thats exactly what I asked for .
I try it , what I really want is something slightely different
Iterations
Iterations
Each phase has iterations, each having the
purpose of producing a demonstrable
piece of software. The duration of iteration
may vary from two weeks or less up to six
months.
Iterations
Inception
Iterations
Elaboration
Iterations
Construction
Iterations
Transition
UP phases
Process Workflows
Inception Elaboration
Construction
Transition
Business Modeling
Requirements
Analysis & Design
Implementation
Test
Deployment
Supporting Workflows
Configuration Mgmt
Management
Environment
time
Iter. Iter.
#m #m+1
Requirements
Design
Implementation
Test
Benefits to iterative
developement
Less project failure
UP phases
Inception :
Approximate vision.
Business case .
Scope. (we model the system not the business)
Vague estimates.
Ask yourself : is the system feasible ? Should we go on or stop?
Elaboration
Refined vision
Iterative implementation of core architecture
High risks issues are mitigated
Most requirements are identified !!
More realistic estimates
UP phases
Construction
Transition
UP
disciplines:
UP phases
Construction
Transition
Beta Tests
Deployment
Phases
Process Workflows
Inception Elaboration
Construction
Transition
Business Modeling
Requirements
Analysis & Design
Implementation
Test
Deployment
Supporting Workflows
Configuration Mgmt
Management
Environment
Iter. Iter.
#m #m+1