The document explains the Unified Modeling Language (UML), a standard for modeling and documenting software systems, emphasizing its significance in object-oriented design. It highlights UML's characteristics such as being an open standard that facilitates communication among stakeholders, its evolution from various methodologies in the 1990s, and the existence of different models and views within UML. Additionally, the document notes UML's broad application support across multiple software tools and its multi-diagrammatic nature, which provides partial representations of systems tailored to various stakeholder perspectives.

1. UML

2. What is UML?
• Unified Modeling Language
– OMG Standard, Object Management Group.
– Depending on function through Booch,
Rumbaugh, Jacobson.
• UML is really a modeling language to express as well
as design documents, software
– Especially helpful for OO design.
– Not a process, however some have been proposed
using UML.
– Independent associated with implementation
language.

3. Why use UML
• Open Standard, Graphical with regard to
– Indicating, visualizing, constructing, as well as
documenting software systems.
• Language may be used through common initial
design in order to really specific detailed design over
the entire software development lifecycle.
• Increase understanding/communication associated
with product to customers and developers.

4. Cont..
• Support with regard to diverse application
areas.
• Support with regard to UML in several
software packages today (for example,
Rational, plugins with regard to popular IDE’s
like NetBeans, Eclipse).
• Based on experience as well as requirements
from the user community.

5. Brief History
• Inundated with methodologies in early 90’s
– Booch, Jacobson, Yourden, Rumbaugh.
• Booch, Jacobson merged methods 1994.
• Rumbaugh joined 1995.
• 1997 UML 1.1 from OMG includes input from
others, e.g. Yourden.
• UML v2.0 current version.

6. History of UML

7. Contributions to UML

8. Systems, Models and Views
• Model:
– The model is an abstraction explaining the subset of
a system.
• View:
– A view derepresents picts selected aspects of a
model.
• Notation:
– A notation is a set of graphical or even textual rules
with regard to depicting views.
• Views as well as models of a single system may overlap
one another.

9. Cont..
For Examples:
• System:
– Aircraft
• Models:
– Flight simulator, scale model
• Views:
– All blueprints, electrical wiring, fuel system

10. Cont..
System
View 1
Model 2
View 2
View 3
Model 1
Aircraft
Flightsimulator
Scale Model
Blueprints
Electrical
Wiring

11. UML Models, Views, Diagrams
• UML is a multi-diagrammatic language.
– Every diagram is a view into a model
• Diagram introduced from the aspect of a
particular stakeholder.
• Provides a partial representation of the system.
• Is actually semantically consistent along with
additional views.

12. Cont..
• Example views

13. Models, Views, Diagrams

14. Thank You
www.myassignmenthelp.net
Email Us at :
support@myassignmenthelp.net