Table of Contents
Unified Modeling Language
The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering, that is intended to provide a standard way to visualize the design of a system.
The Unified Modeling Language is a graphical notation for describing object-oriented designs. It has been adopted as a standard by the Open Management Group with wide industry support. “The Unified Modeling Language (UML) is a language for specifying software, visualizing software, constructing software, and documenting software and the artifacts of software systems, as well as for business modeling and other non-software systems.” Fair Use Source: OMG UML Summary, Version 1.0, September 1, 1997
The creation of UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design. It was developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in 1994–1995, with further development led by them through 1996. In 1997 UML was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2005 UML was also published by the International Organization for Standardization (ISO) as an approved ISO standard.
Courses
-
- “This course introduces the Unified Modeling Language (UML) and several of the programming diagrams that are most often used in software development.”
- “Seldom does a software project of any size get built by only one person. Most often many different people, with different programming skills work together to build the solution. It is not uncommon to have the technology not be the most challenging part of the project, but rather it is often the lack of clear communication between the project team members. The Unified Modeling Language (UML) helps the team members to communicate clearly and precisely. The UML includes several programming diagrams and programming models that support the software design of different aspects of the solution. If each member of the team is able to understand those models that are useful to them they are more likely to understand each other, and the challenges and risks of different understandings and views of the solution are minimized. In this course we review the need for this clear communication. We discuss several of the common diagrams that teams use to model a software solution and identify some of the team members that most commonly use the diagram. The UML is very large and there is much that can be done with it beyond what is covered in this introductory course. But having this basic understanding of the common models can reduce many of the challenges faced by project teams.”