Some say the cup is half empty, while others say it is half full. However, in an engineer’s opinion both are wrong. The real problem is the cup is too big. That’s where an engineer comes into practicality i.e. examining a situation on the basis of evidences. With the coming of the better but synthetic era, engineers have formed a better layer in our lives. Engineers are unmistakably the true perceivers of engineering rather than being the vice versa.
Engineering is further divided into the following: electrical, mechanical, computer and electronics. But this article will discuss a specific architectural stratum in the field of software engineering i.e. UML or Unified Modelling Language.
Models and diagrams are representations of a real-world application. A model is the abstract representation of the system, while different diagrams provide concrete images of the system. Unified Modelling Language (UML) Models represent systems at different levels of detail. Some models describe a system from a higher, more abstract level, while other models provide greater detail. UML models contain model elements, such as actors, use cases, classes, and packages, and one or more diagrams that show a specific perspective of a system. A model can also contain other, more detailed models.
The Unified Modelling Language is a general-purpose modelling language in the field of software engineering. It provides a set of graphic notation techniques to create visual models of object-oriented software-intensive systems. It was developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in the 1990s. It was adopted by the Object Management Group (OMG) in 1997, and has been managed by this organization ever since. In 2000 the Unified Modelling Language was accepted by the International Organization for Standardization (ISO) as a standard for modelling software-intensive systems.
Now, in order to gain a coherent understanding of the same, one needs to understand the following terms:
- Data modelling: It is the process of creating a data model for an information system by applying formal data modelling techniques.
- Business modelling: It is the activity of representing processes of an enterprise, so that the current process may be analyzed and improved.
- Object modelling: A collection of objects or classes through which a program can examine and manipulate some specific parts of its world.
Unified Modelling Language integrates applications from data modelling, business modelling, object modelling, and component modelling.
The Unified Modelling Language (UML) offers standardization for a system’s architectural blueprints, including elements such as activities, actors, business processes, database schemas, logical components, programming language statements and reusable software components.
UML can be applied in many areas like embedded systems, web applications, commercial applications but its effectiveness has shown better prominence in the following fields:
- Enterprise information systems.
- Banking and financial services.
- Medical electronics.
- Distributed Web-based services.
The UML can also be used to model non-software systems, such as workflow in the legal system, a patient healthcare system, software engineering in aircraft combat systems, and the design of hardware.