Posts: 3,561
Threads: 923
Joined: Sep 2010
Eran Kampf 2005
What is UML?
UML – Unified Modeling Language
Posts: 2,300
Threads: 878
Joined: Sep 2010
[attachment=6471]
Unified Modeling Language
History Of UML
In October 1994 the Unified Modeling Language was introduced as UML 0.9 and then in 1996 (0.91) by (Grady booch ,Ivor Jacobson)
Input was obtained from many, including TI, IBM, Microsoft, Oracle, and HP.
This led to UML 1.0 in 1997
Eventually, the semantics and flexibility was improved resulting in UML 2.0 in 2003
At same time, the software engineering community wanted an effective and standardized modeling language
Posts: 2,300
Threads: 878
Joined: Sep 2010
UML is the Unified Modeling Language
What is UML?
UML is the Unified Modeling Language
Unifies the OO modeling techniques of Grady Booch, Jim Rumbaugh and Ivar Jacobson (the three amigos)
UML is a current standard by the OMG (Object Management Group)
Current UML revision is UML v 1.5 (2003)
It is a way to express an OO design, easily communicative to others, regardless of the language
UML can express systems other than computer systems
UML is not a process or method: it is a modeling language
OO Analysis & Design has a static view and a dynamic view
A static view is one in which we view the structure of the system
A dynamic view is one in which we see how the system object collaborate to solve the problem
UML offers modeling for both, static and dynamic views
Posts: 2,300
Threads: 878
Joined: Sep 2010
[attachment=6751]
The Unified Modeling Language (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.1 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.
Goals of UML
The primary goals in the design of the UML were:
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.
Why Use UML?
As the strategic value of software increases for many companies, the industry looks for techniques to automate the production of software and to improve quality and reduce cost and time-to-market. These techniques include component technology, visual programming, patterns and frameworks. Businesses also seek techniques to manage the complexity of systems as they increase in scope and scale. In particular, they recognize the need to solve recurring architectural problems, such as physical distribution, concurrency, replication, security, load balancing and fault tolerance. Additionally, the development for the World Wide Web, while making some things simpler, has exacerbated these architectural problems. The Unified Modeling Language (UML) was designed to respond to these needs.
Each UML diagram is designed to let developers and customers view a software system from a different perspective and in varying degrees of abstraction. UML diagrams commonly created in visual modeling tools include:1