Professional Documents
Culture Documents
Usecase Model
1
People are more important than any process.
Good people with a good process will outperform good people with no
process every time.
—Grady Booch
What Is a Process?
A process defines Who is doing What, When and How
to reach a certain goal. In software engineering the goal
is to build a software product or to enhance an existing
one
2
Unified Process
1. The Unified Process [JBR99] has emerged as a popular software
development process for building object-oriented systems. In
particular, the Rational Unified Process or RUP [Kruchten00], a
detailed refinement of the Unified Process, has been widely adopted.
2. The Unified Process (UP) combines commonly accepted best
practices, such as an interactive lifecycle and risk-driven development,
into a cohesive and well-documented description.
3. Interactive and incremental development.
time
3
The UP Phases • iterative
implementati
1.A UP project organizes the work and iterations
on of the across four
• approxima • refined vision, 3.
remaining
major phases:
Inception
te vision, 2.
iterative Constructi
lower risk and
Elaborati on 4.
business implementation easier Transitio
on
case, of the core elements, and n
scope, architecture, preparation
vague resolution of for • beta
estimates. high risks, deployment tests,
identification of deploym
most ent
requirements
and scope,
more realistic
estimates.
Features of UP Phases
This is not the old "waterfall" or sequential lifecycle
of first defining all the requirements, and then
doing all or most of the design.
4
UP Phases and Iterations
Inception Elaboration Construction Transition
Process Customization
Inception Elab1 Elab2 Elab3 Elab 4
* Release 1 Time
^ Final Release
5
Use Cases Drive the Iteration Process
Inception Elaboration Construction Transition
“Mini-Waterfall” Process
Iteration Planning
Rqmts Capture
Analysis & Design
Implementation
Test
Prepare Release
6
Artifacts/Models in UP Workflows
Discipline Artifact Incep. Elab. Const. Trans.
Iteration→ I1 E1…En C1-Cn T1-T2