Unified Modeling Language is a graphical language used in system design. UML offers standard way to write system blue prints. UML can presents system's functions, processes, relationships and all other activities related such as database schemas (design), message flows, user interactions, etc.
UML is not an industry standard for writing system blue prints but is wide accepted and practices by system designers. It makes other stake holders to clearly understand the system and interact with each other. This is not a programming language but the start point for programmers to developed the system using UML diagrams.
UML diagram is a graphical presentation of set of elements, most often rendered as a connected graphs of vertices (things) and arches (relationships). There are many diagrams in UML and we are mainly talking about following diagrams.
Class Diagram: A class diagram shows a set of classes, interfaces, and collaborations and their relationships. An object diagram shows a set of objects and their relationships. A Use of Case Diagram shows a set of use cases and actors and their relationships.
Both sequence diagrams and collaboration diagrams are kind of interaction diagrams. A state-chart diagram shows states of objects, transitions, events and activities. State-chart diagram shows dynamics of a system. Activity diagram is a special kind of state-chart diagram that shows the flow from activity within a system.
Component diagram show the organization and dependencies among a set of components. deployment diagram shows the configuration of runtime processes of a system.
Even though there are lots of diagrams specified above, the real use of UML is more personal than standard. The real understanding on UML comes with the practice of real world system design.
UML is not an industry standard for writing system blue prints but is wide accepted and practices by system designers. It makes other stake holders to clearly understand the system and interact with each other. This is not a programming language but the start point for programmers to developed the system using UML diagrams.
UML diagram is a graphical presentation of set of elements, most often rendered as a connected graphs of vertices (things) and arches (relationships). There are many diagrams in UML and we are mainly talking about following diagrams.
Class Diagram: A class diagram shows a set of classes, interfaces, and collaborations and their relationships. An object diagram shows a set of objects and their relationships. A Use of Case Diagram shows a set of use cases and actors and their relationships.
Both sequence diagrams and collaboration diagrams are kind of interaction diagrams. A state-chart diagram shows states of objects, transitions, events and activities. State-chart diagram shows dynamics of a system. Activity diagram is a special kind of state-chart diagram that shows the flow from activity within a system.
Component diagram show the organization and dependencies among a set of components. deployment diagram shows the configuration of runtime processes of a system.
Even though there are lots of diagrams specified above, the real use of UML is more personal than standard. The real understanding on UML comes with the practice of real world system design.
an example UML diagram
What is the software you used to create these UML diagrams ? Is it rational rose or a software like creately ? I've seen some good diagram examples in creately diagram community.
ReplyDelete