UML Understandings!

UML visualizations helps Business folks to understand & monitor the Process.

The Unified Modeling Language (UML) is most commonly used graphical representation or technique to create visual models of object-oriented software-intensive systems.

It is required to understand, UML may be used in a variety of ways to support Software Development, and it has a various graphic notations with specific standards which are required to follow.

These graphical notations, helps developers to understand Application Structure, Behavior, Architecture, Business Process and/or Data Structure. {In other-words, it is a standard way to write a system “blue print” to define business process, system functionality or database schemas}

There are different graphical representations for defining UML visualizations.. .following list are most commonly used diagrams:

  • Use Case diagram: is typically used to identify and define the interactions between a role (normally called as an “Actor”) and a system, to achieve a goal.
  • Statechart diagram: defines behaviour of the actors or usecases to represent situations during the life of on object. It describes the flow of control from one state to another state. States are defined as a condition in which an object exists and changes when some event is triggered.
  • Activity Diagram: defines dynamic nature of the system or flow of the system from one activity to another activity; each activity represents behaviour of an application which results in execution system.
  • Sequence Diagram: is a graphical representation of object interactions over time, or in other-words it represents flow of messages from one object to another and such correspond to the methods and events supported by a class/object.
  • BPMN: Business Process Diagram is technique, to represent requirements/process with graphical notations, which helps business users to understand the business process operations.

Business Analyst will create the initial version from SMEs or Users with few meetings, and based on the feedbacks from the Stakeholders or Business, diagrams will be updated to synchronize with the requirement/ideas which helps Business or Technical folks who are responsible for implementing the technology to reach the final goal.

Last modified on Monday, 10 April 2017 18:23
Share this article

Contact info

About us


Join the network: We are Business Folks, analyzing IT projects.
We use cookies to improve our website. By continuing to use this website, you are giving consent to cookies being used. More details…