This document provides an overview of the Unified Process (UP) methodology for software development. It discusses the iterative and incremental nature of UP, with development occurring through multiple iterations. Each iteration involves requirements analysis, design, implementation, testing, and integration work. The UP approach includes four phases - Inception, Elaboration, Construction, and Transition - with different disciplines and processes emphasized in each phase. Iterations allow for early programming and testing of partial systems, with feedback from each iteration informing refinement in subsequent iterations to evolve requirements and design.

1. Introduction to UP
Lecture # 3
Ms. Shazia Yousaf
Lecturer, Department of computer science,
University of Sargodha Mandi Bahauddin Campus

2. Development Methodology
 A software development process describes an
approach to building, deploying and possibly
maintaining software
 Waterfall
Problems
 Iterative and evolutionary development
Involves early programming and testing of partial system
Development starts before all requirements are defined
in detail.

3. Iterative & Evolutionary development
Requirements
Design
Implementation &
Test & Integration
& More Design
Final Integration
& System Test
Requirements
Design
3 weeks (for example)
The system grows
incrementally.
Feedback from
iteration N leads to
refinement and
adaptation of the
requirements and
design in iteration
N+1.
Iterations are fixed in
length, or timeboxed.
Time
Implementation &
Test & Integration
& More Design
Final Integration
& System Test

4. Iterative feedback and Evolution
Early iterations are farther from the "true
path" of the system. Via feedback and
adaptation, the system converges towards
the most appropriate requirements and
design.
In late iterations, a significant change in
requirements is rare, but can occur. Such
late changes may give an organization a
competitive business advantage.
one iteration of design,
implement, integrate, and test

5. Agile Methods
Time boxed iterative and evolutionary
development
Adaptive planning and incremental
delivery
The agile manifesto
 Individuals and interactions over processes and tools
 Working software over comprehensive docs
 Customer collaboration over contract negotiation
 Responding to change over following a plan
 Agile Modeling
 Is to understand, not to document

6. Agile methods
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5
20%
2%
requirements
software
30%
5%
requirements
software
50%
8%
90% 90%
20%
10%
requirements workshops
Imagine this will
ultimately be a 20-
iteration project.
In evolutionary iterative
development, the
requirements evolve
over a set of the early
iterations, through a
series of requirements
workshops (for
example). Perhaps
after four iterations and
workshops, 90% of the
requirements are
defined and refined.
Nevertheless, only
10% of the software is
built.
1 2 3 4 5 ... 20
week 1
M T W Th F
week 2
M T W Th F
week 3
M T W Th F
kickoff meeting
clarifying iteration
goals with the team.
1 hour
team agile
modeling &
design,
UML
whiteboard
sketching.
5 hours
start
coding &
testing
a 3-week iteration
de-scope
iteration
goals if
too much
work
final check-in
and code-
freeze for the
iteration
baseline
demo and
2-day
requirements
workshop
next
iteration
planning
meeting;
2 hours
Most OOA/D and
applying UML during
this period
Use-case modeling
during the workshop

7. UP
 Phases
Inception
Elaboration
Construction
Transition

8. UP Phases
inc. elaboration construction transition
iteration phase
development cycle
release
A stable executable
subset of the final
product. The end of
each iteration is a
minor release.
increment
The difference
(delta) between the
releases of 2
subsequent
iterations.
final production
release
At this point, the
system is released
for production use.
milestone
An iteration end-
point when some
significant decision
or evaluation
occurs.

9. Inception Phase
Conduct feasibility study
Define approximate vision, business
cases, and scope for project
Develop vague estimates (size, cost,
and schedule)

10. Elaboration Phase
Refine vision
Identify most requirements and scope
Do iterative implementation of the
system’s core architecture
Resolve high risks

11. Construction Phase
Do iterative implementation of the
system’s easier and lower risk elements
Prepare for deployment

12. Transition Phase
Conduct beta tests
Deploy system

13. UP Disciplines
 A discipline is a set of activities and the related
artifacts created by those activities
 An artifact is any work product
 code,
documents,
diagrams,
models, etc.

14. Other UP Disciplines
 UP Disciplines include
Business Modeling
Requirements Analysis
Design
Implementation (programming & building
the system)
Test
Deployment (releasing the system)
Configuration and Change Management
Project Management
Environment (create development environment)

15. UP Disciplines
Iterations
Sample
UP Disciplines
Business Modeling
Requirements
Design
Implementation
Test
Deployment
Configuration & Change
Management
Project Management
Environment
Focus
of this
book
Note th
althoug
iteration
work in
disciplin
relative
emphas
over tim
This exa
suggest
literal.
A four-week iteration (for example).
A mini-project that includes work in most
disciplines, ending in a stable executable.

16. UP Disciplines
Sample
UP Disciplines
Business
Modeling
Requirements
Design
Implementation
...
The relative effort in
disciplines shifts
across the phases.
This example is
suggestive, not literal.
incep-
tion
elaboration construction
transi-
tion
...

17. Iteration, Disciplines, Phases
Each iteration may use some or all of the
disciplines, depending on when that
iteration occurs in development
Likewise, the Phases may each
correspond to one or more iterations so
each Phase will also use some or all of the
disciplines

18. Thanks