Information Technology Reference
In-Depth Information
: to understand the organization and the business
in which the software will be used.
Business modeling
: to understand the customer needs and analyze them
to ensure that the right solution is developed.
Requirements
: to architect the system, design the compo-
nents, build an object model, and define the solution specification.
Analysis and design
: to build the software programming code blocks
that will realize the requirements.
Implementation
Testing
: to ensure that the software is built according to the
requirements.
Deployment
: to package, deliver, install, and train the customer to
use the software.
There are other disciplines that are considered to perform a supporting
role, such as configuration and change management, project management,
environment, etc.
Horizontal Dimension: Phases
RUP defines four phases along a horizontal axis that is a temporal scale.
Each phase is usually achieved through one or more iterations with
software being produced (usually) at the end of each iteration.
The four phases are:
1.
Inception
: to determine what is to be created, for whom, and
whether it is economically viable.
2.
: to address the key components of the system, identify
various technical approaches, and assess the proper architecture.
Elaboration
3.
Construction
: to develop the system.
4.
Transition
: to deliver the system.
The end of each phase marks a milestone. This is a point in the devel-
opment life cycle where one makes a decision whether or not to continue
the project.
Using Life Cycle as a Model
A life-cycle approach is better suited to manage a relatively independent
unit of work. Something that goes on forever, for example, running a
nation, is not handled through life cycles.
A life cycle helps one figure out where one is. If in the requirements
phase, whether it is a two-person-year project or a 200-person-year project,
