|
What is UML ?
The Unified Modeling
Language (UML) is a standard language for specifying,
visualizing, constructing, and documenting the artifacts of
software systems, as well as for business modeling and other
non-software systems. The UML represents a collection of best
engineering practices that have proven successful in the
modeling of large and complex systems. The UML is a very
important part of developing object oriented software and the
software development process. The UML uses mostly graphical
notations to express the design of software projects. Using
the UML helps project teams communicate, explore potential
designs, and validate the architectural design of the
software.
The development of UML
began in late 1994 when Grady Booch and Jim Rumbaugh of
Rational Software Corporation began their work on unifying the
Booch and OMT (Object Modeling Technique) methods. In the Fall
of 1995, Ivar Jacobson and his Objectory company joined
Rational and this unification effort, merging in the OOSE
(Object-Oriented Software Engineering) method.
Goals of UML
1.Provide users with a ready-to-use,
expressive visual modeling language so they can develop and
exchange meaningful models.
2.Provide extensibility
and specialization mechanisms to extend the core concepts.
3.Be independent of
particular programming languages and development
processes.
4.Provide a formal basis
for understanding the modeling language.
5.Encourage the growth of
the OO tools market.
6.Support higher-level
development concepts such as collaborations, frameworks,
patterns and components.
7.Integrate best practices
Types of UML
Diagrams.
1.Use Case Diagram. A use case is a set of scenarios that
describing an interaction between a user and a system
2.Class Diagram .Models class structure and contents using
design elements such as classes, packages and objects. It also
displays relationships such as containment, inheritance,
associations and others
3.Sequence Diagram displays the time sequence of the
objects participating in the interaction.
4.Collaboration Diagram displays an interaction organized
around the objects and their links to one another. Numbers are
used to show the sequence of messages
5.State Diagram displays the sequences of states that an
object of an interaction goes through during its life in
response to received stimuli, together with its responses and
actions.
6.Activity Diagram displays a special state diagram where
most of the states are action states and most of the
transitions are triggered by completion of the actions in the
source states. This diagram focuses on flows driven by
internal processing.
7.Component Diagram displays the high level packaged
structure of the code. Dependencies among components are
shown, including source code components, binary code
components, and executable components.
8.Deployment Diagram displays the configuration of run-time
processing elements and the software components, processes,
and objects that live on them
| 
Home