Visualizing the
design of a system graphically and textually
Specifying models
that are precise, unambiguous, and complete
Construction code
by mapping a model in UML to a programming language such as Java
or C++
Documenting the
artifacts of a system such as Requirements, Architecture,
Design, Source code, Project plans, Tests, Prototypes, and
Releases
Testing the
system
There are the
nine types of Diagrams in the UML.
Class diagram -
Shows a set of classes, interfaces, and collaborations and their
relationships. This is the most common type of diagram
used when modeling OO systems.
Object diagram
- Shows a set of objects and their relationships. Can be
thought of as an instance of a Class diagram.
Use case
diagram - Shows a set of use cases and actors and their
relationships. these types of diagrams drive the whole
development process since they describe the requirements of the
system.
Sequence
diagram - Shows an interaction, consisting of a set of
objects and their relationships, including the messages that may
be dispatched among them. Emphasizes the time-ordering of
messages.
Collaboration
diagram - Shows an interaction, consisting of a set of
objects and their relationships, including the messages that may
be dispatched among them. Emphasizes the structural
organization of the objects that send and receive messages.
Statechart
diagram - Shows a state machine, consisting of states,
transitions, events, and activities.
Activity
diagram - Special kind of a Statechart diagram that shows
the flow from activity to activity within a system. They
are very similar to flowchart diagrams except that concurrency
may be modeled in Activity diagrams.
Component
diagram - Shows the organizations and dependencies among a
set of components.
Deployment
diagram - Shows the configuration of run - time processing
nodes and the components that live on them.
Use case view>
- Encompass the use cases that describe the behavior of the
system as seen by its end users, analysts, and testers
Design view
- Encompass the classes, interfaces, and collaborations that
form the vocabulary of the problem and its solution
Process view
- Encompass the threads and processes that form the system's
concurrency and synchronization mechanisms
Implementation
view - Encompass the components and files that are used to
assemble and release the physical system
Deployment
view - Encompass the nodes that form the system's hardware
topology on which the system executes
Each of the five
views is a projection into the organization and structure of the
system, focused on a particular aspect of that system.
Each of these five views can stand alone so that different
stakeholders can focus on the issues of the system's
architecture that most concern them. The five views also
interact with each other. For example, nodes in the
deployment view hold components in the implementation view that,
in turn, represent the physical realization of classes,
interfaces, collaborations, and active classes from the design
and process views.
Use case
driven, which means that use cases are used as a primary
artifact for establishing the desired behavior of the system,
for verifying and validating the system's architecture, for
testing, and for communicating among the stakeholders of the
project
Architecture-centric,
which means that a system's architecture is used as a primary
artifact for conceptualizing, constructing, managing, and
evolving the system under development
Iterative,
which is one that involves managing a stream of executable
releases
Incremental,
which is one that involves the continuous integration of the
system's architecture to produce these releases, with each new
release embodying incremental improvements over the other
Risk driven,
which means that each new release is focused on attacking and
reducing the most significant risks to the success of the
project
This process is
broken down into Phases, which is the span of time
between two major milestones of the process, when a well-defined
set of objectives are met, artifacts are completed, and
decisions are made whether to move into the next phase.
What are the
four Phases of the Rational Unified Process ?
- Inception
- Elaboration
- Construction
- Transition
