Unified Modelling Language (UML) Intro
UML was first introduced in 1997.It is the product of three other modelling languages (OMT, OOSE, Booch). The primary goal of UML is to provide the development community with a stable and common design language. It’s similar to the blueprint used by construction workers. Therefore by modelling your project using UML notations, it’s easy for a UML proficient person joining your team, to understand the application under development and become productive immediately. The increasing popularity of UML can be attributed to the facts that it’s independent of any programming language and it’s not a methodology but a language by itself.
There are many UML diagrams, the most useful (standard) UML diagrams are explained very briefly here.
A) Use-case Diagram:
A use case is used to communicate a unit of functionality provided by the system. The main purpose of the use-case diagram is to help development team visualize the functional requirements of a system, including the relationship with users.
B) Class Diagram:
It shows how the various entities in the system interact with each other. As the name represents class diagrams are used to represent classes. These classes can be either logical or the real implemented classes. It denotes a class with it’s name, attributes and methods. It’s also is used to display relationship between various classes.
C) Sequence Diagrams:
Sequence diagrams show a detailed flow, for a specific use case or even just part of a specific use case. They display the calls between objects in the sequence in which they occur.
D) State Chart Diagram:
As the name indicates this diagram displays the different states of a class and also the transition from one state to another.
E) Activity Diagram:
This diagram is used to show the procedural flow of control between two classes. But the difference between this and sequence diagram is that this is used to make non- technical people to understand the business process.
F) Component Diagram:
Sequence diagrams show a detailed flow, for a specific use case or even just part of a specific use case. They display the calls between objects in the sequence in which they occur.
D) State Chart Diagram:
As the name indicates this diagram displays the different states of a class and also the transition from one state to another.
E) Activity Diagram:
This diagram is used to show the procedural flow of control between two classes. But the difference between this and sequence diagram is that this is used to make non- technical people to understand the business process.
F) Component Diagram:
It shows a physical view of the system i.e. it shows the software dependencies on other software component.
For people wanting to learn more please refer the links below:
posted by Pradeep Selvaraj at
5:58 PM
0 Comments:
Post a Comment
<< Home