Posts

Is UML a programming language?

The UML stands for Unified Modeling Language. It is christened a “language” since the representation involves predefined notations, semantics and rules – so all participants involved – stakeholders, analysts, developers, testers all interpret these diagrams the same way.

uml_logoIt is not a programming language (such as C, C++, Java) or a sub-language (such as SQL) and does not have a set of ‘command keywords’.

The UML is a representation method, providing for different views to detail the software system under design. Just like we have front elevation, floor plan, electrical plan, plumbing plan, in the construction industry, to document different aspects of the same building, UML offers a set of diagrams to represent varied views for a software system. Each of these diagrams have a specific perspective to deliver to the reader, and it makes sense to overlay multiple diagrams to get the complete picture. The UML was architected by the Object Management Group (OMG) and they continue to maintain the definition for the later releases. Visit OMG.org and UML.org for more information.

The UML is an analysis toolbox that allows authoring of specific details of the system, such as business processes, state changes of key objects in a system, etc.

What is UML? From UML.org

 

Please ask your questions, using the comments. Thanks!

Difference between Use Cases and Use Case Diagrams

Use Case Model vs. Teztual Use CaseUse Cases are meant to represent the high level functional areas of the system, as represented in a ULM Use Case Model (or use case diagram).  Primarily meant to analyze the different parts of the system and their relationships and dependencies.

Each ‘textal’ use case is then blown into its own ‘user manual’ style document detailing the dialogue between the ‘system’ (the software you are developing) and the ‘actors’ (people, things or other software that interact with your software).

More:

youtube
please specify correct url

Key Differences between Include and Extend Stereotypes in Use Cases

Include and Extend are two key constructs in UML Use Case Diagrams. Learn about the two constructs, the differences and how to use them in your model!

vimeo
please specify correct url