Software Project Management Brochure Template Page 6

ADVERTISEMENT

6
Handbook on Software Engineering & Knowledge Engineering
process is architecture-centric, meaning that its main deliverable is an executable
architecture (the system), described by a set of models generated during the
system development (use-case model, analysis model, design model, deployment
model, implementation model, and test model). The models are represented
using the standard UML diagrams [13]. The Unified Process is also use-case
oriented, which means that generic scenarios of how the user or external
applications use the system or its subsystems bind all the workflows and drive
the iterations.
CORE
PHASES
WORKFLOWS
Inception
Elaboration
Construction
Transition
Requirements
An iteration in the
elaboration phase
Analysis
Design
Implementation
Test
Preliminary
Iter.
Iter.
Iter.
Iter.
Iter.
Iter.
Iter.
iteration(s)
# 1
# 2
# n
# n+1
# n+2
# m
# m+1
Iterations
Figure 4 - Core workflows, phases, and iterations in the Unified Process of object-
oriented software development (after [24])
Being iterative, the Unified Process reduces additional development costs
generated by unexpected situations (usually just a single iteration of work is
lost). Iterating through all core workflows in every iteration, the process is
compliant with the reality of ever changing and incomplete user requirements.
The Unified Process is also risk-driven - it enforces examining areas of highest
risk in every phase and every iteration, as well as doing the most critical tasks
first. Hence it minimizes the risk of project runaways. Managers can easily adapt
the Unified Process to different application types, project sizes, development
teams, and levels of competence.
Because of the importance of the Unified Process for software project
management today, comments on some other issues from the Unified Process
perspective are included in the following chapters.

ADVERTISEMENT

00 votes

Related Articles

Related forms

Related Categories

Parent category: Business