UML Basics
UML, or Unified Modeling Language, is a specification language that is used in the software engineering field. It can be defined as a general purpose language that uses a graphical designation which can create an abstract model. This abstract model can then be used in a system. This system is called the UML model. The Object Management group is responsible for defining UML, and they do this via the UML metamodel. XMI can be used to serialize the UML model.
The Unified Modeling Language is commonly used to visualize and construct systems which are software intensive. Because software has become much more complex in recent years, developers are finding it more challenging to build complex applications within short time periods. Even when they do, these software applications are often filled with bugs, and it can take programmers weeks to find and fix them. This is time that has been wasted, since an approach could have been used which would have reduced the number of bugs before the application was completed.
However, it should be emphasized that UML is not limited simply modeling software. It can also be used to build models for system engineering, business processes, and organization structures. A special language called Systems Modeling Language was designed to handle systems which were defined within UML 2.0. The Unified Modeling Language is important for a number of reasons. First, it has been used as a catalyst for the advancement of technologies which are model driven, and some of these include Model Driven Development and Model Driven Architecture.
Because an emphasis has been placed on the importance of graphics notation, UML is proficient in meeting this demand, and it can be used to represent behaviors, classes, and aggregation. While software developers were forced to deal with more rudimentary issues in the past, languages like UML have now allowed them to focus on the structure and design of their software programs. It should also be noted that UML models can be transformed into various other representations, often without a great deal of effort. One example of this is the ability to transform UML models into Java representations.
This transformation can be accomplished through a transformation language that is similar to QVT. Many of these languages may be supported by OMG. The Unified Modeling Language has a number of features and characteristics which separate it from other languages within the same category. Many of these attributes have allowed it to be useful for developers. In this article, I intend to show you many of these attributes, and you will then understand why the Unified Modeling Language is one of the most powerful languages in existence today.
{mospagebreak title=UML Characteristics}
Unified Modeling Language Characteristics
It must be emphasized that UML is an extensible language. It has two elements that are used for customization, and these are stereotypes and profiles. Much of the semantics for this language were greatly improved with the UML 2.0 update. In 1996, a group of developers came together to create the UML Partners.
It was this collaboration which allowed them to create the Unified Modeling Language. When it was first created, the developers offered it as the response to OMG RFP. While the semantic integration was weak when the language was first introduced it, these problems were fixed with the release of UML 2.0.
Another characteristic of UML is that is borrows many concepts from the object oriented approach. When UML was created, one of the goals of the developers was to create a language that could support every object oriented approach. Some of the features which UML supports includes time analysis, data analysis, object oriented structure design, and state charts. With all these features, UML became the program of choice for professionals who needed to solve various engineering challenges.
Engineers commonly use it for single processes and systems which are distributed. However, UML is not limited to the engineering field. It is useful in any situation where developers need to map out complex systems or processes that can be understood by others.
While UML is a rich language, it is quite large. The standard for this language is maintained on an international level, and a number of additions have been made to it since the 1.1 release. As of this writing, UML 2.1 is in development, and it will be directly connected to XMI 2.1. When it comes to methods, it must be emphasized that UML is not a method itself. Instead, it is a language that was designed to work with the best object oriented approaches available.
{mospagebreak title= UML Methods and UML Models}
UML Methods
When UML was first introduced, it offered full support for Booch, OMT, and Objectory, the most popular OO methods of the time. However, as with all technology, UML has evolved since its introduction, and it has been altered in a way which allows it to process notations such as OMT. In addition to this, a number of new methods have been created around UML. One of the most popular UML methods is the RUP, or Rational Unified Process. Some of the other well known UML methods include the Dynamic Systems Development Method, and the Abstraction Method.
Each method is important, because they may provide solutions which are specific. In addition to this, they can be used to achieve objectives which are different from other methods. These methods are a very important part of the UML history and function, and they will continue to evolve to meet the demands of the future. If you wish to become proficient with using UML, you will want to learn about the different methods can how they can be used to solve a number of challenging problems.
UML Models
When you talk about UML, it is very important to differentiate between the system diagrams and the UML model. A system diagram is a portion of a graphical symbol, and it is used to denote the system’s model. The model will have what is called a semantic backplane, and this is a document that is used to deal with the diagrams and elements of a model. There are three areas of the system model that you will want to become familiar with. These are the object model, the functional model, and the dynamic model. Each model has specific roles that it must play for the proper function of the system.
The Object model will be responsible for demonstrating the system structure and substructure, and it will do this by using relationships, attributes, and operations. Class diagrams are closely related to this model. As the name implies, the functional model will demonstrate the system functionality from the view of the user. It will be directly connected to the use case diagrams. The dynamic model will be responsible for demonstrating inner behavior of a system. It is directly connected to state machine diagrams, sequence diagrams, and activity diagrams.
It should also be noted that a model can be traded among UML tools via the XMI file format. Diagrams are important part of UML, and there are 13 of them in version 2.0. To understand why these diagrams are important, the must be structured based on hierarchy, and this can be visualized with a chart. Like the models, each diagram will have its own function within the system. For example, the behavior diagram is responsible for defining what should happen in a system. The Interaction diagram will be responsible controlling the flow of data among the elements in the system that is being modeled.
Another element that you will want to become familiar with is the Protocol State Machine. This is a variation of the State Machine, and it is used to generate models for the communication protocols of the network. The Protocol State Machine is valuable for a number of reasons. By generating models for the protocols of networks, it can allow developers to enhance those networks in a manner which will make them much more efficient.
[catlist id=151].