Sekolah Tinggi Manajemen Informatika dan Komputer

STMIK Widya Pratama

Jl. Patriot No. 25 Pekalongan, Telp. (0285) 427816, Fax. (0285) 427815

Core message -- second bullet

 Sekolah Tinggi Manajemen Informatika dan Komputer
STMIK Widya Pratama 03/09/21

Jl. Patriot No. 25 Pekalongan, Telp. (0285) 427816, Fax. (0285) 427815

The RUP is based on the

UML, so we first discuss
the UML and then explain
what the UML does NOT
provide. The RUP fills in
the gaps.

The software systems we develop today are much more

complex than the human mind can comprehend in their
entirety. This is why we model systems. The choice of what
models to create has a profound influence upon how a
problem is attacked and how a solution is shaped. No single
model is sufficient; every complex system is best approached
through a small set of nearly independent models. To increase
comprehension, a common language like the Unified Modeling
Language is used to express models.
 Sekolah Tinggi Manajemen Informatika dan Komputer
STMIK Widya Pratama
Jl. Patriot No. 25 Pekalongan, Telp. (0285) 427816, Fax. (0285) 427815

Use case diagrams are created to visualize the relationships between actors and use cases
A sequence diagram displays object interactions arranged in a time sequence
A collaboration diagram displays object interactions organized around objects and their links to one another
A class diagram shows the existence of classes and their relationships in the logical view of a system
A class is a collection of objects with common structure, common behavior, common relationships and common semantics
A state transition diagram shows
The life history of a given class
The events that cause a transition from one state to another
The actions that result from a state change
Component diagrams illustrate the organizations and dependencies among software components
The deployment diagram shows the configuration of run-time processing elements and the software processes living on them
 Sekolah Tinggi Manajemen Informatika dan Komputer
STMIK Widya Pratama 03/09/21

Jl. Patriot No. 25 Pekalongan, Telp. (0285) 427816, Fax. (0285) 427815

This diagram was also

shown in the previous
module. We are repeating
it here because we will
provide examples of a few
of these diagrams on the
pages which follow.
The UML emphasizes a
graphical language for
representing models, but
provides little/no guidance
on when and how to use
these diagrams. This is an
area where the RUP
helps. It describes the
kinds of project artifacts
needed, including In building a visual model of a system, many different
diagrams, and puts them diagrams are needed to represent different views of the
in the context of an overall
system. The UML provides a rich notation for visualizing our
project plan.
models. This includes the following key diagrams:
Use Case diagrams to illustrate user interactions with the
system.
Class diagrams to illustrate logical structure.
Object diagrams to illustrate objects and links.
State diagrams to illustrate behavior.
Component diagrams to illustrate physical structure of the
software.
Deployment diagrams to show the mapping of software to
 Sekolah Tinggi Manajemen Informatika dan Komputer
STMIK Widya Pratama 03/09/21

Jl. Patriot No. 25 Pekalongan, Telp. (0285) 427816, Fax. (0285) 427815

The last set of slides briefly introduces most of the UML notations.