Unified Modeling Language

From HaFrWiki
Revision as of 12:38, 3 February 2015 by Hjmf (talk | contribs) (Activity Diagram)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Access-rights violation
The requested action is not allowed by this wiki website.
See the description below for detailed information.

Detailed Access-rights violation
The requested action has been read access for ⧼wikirbac-title-page (history-access)⧽ Unified Modeling Language.
The webmaster/administrator has restricted access to this information using the Role Based Access Control (RBAC).
An entry of this violation has been created in the Log-file with timestamp 27 January 2023 15:52:36.
Details access limitation.
  • No-Super-UserGroup 4 All Categories.
  • No-Super-UserGroup 4 All Categories.
  • Restriction for all usergroups's (*) found for cat Index.
  • No access credentials found for Access: History



RBAC-Documentation
See the the website documentation (HaFrWikiCommunity Portal) for more information.

Suggested continuation

Return to Main Page.

UML or Unified Modeling (Eglish: Modelling) Language [1] is a meta language which uses mainly diagrams [2] to describe a system.

History[edit]

The authors of UML are Grady Booch, James Rumbaugh en Ivar Jacobson (The Three Amigo's). They had all three their own specialism which has been standardized in UML.

  • Booch had Booch 95,
  • Rumbaugh had Object Modelling Technique (OMT)
  • Jacobson had Object Oriented Software Engineering (OOSE).

Objektorientieren_methoden_historie.png.


Use Case Example[edit]

business-use-case-diagram-elements.png Components
  • Use Case
  • Actor
  • Association
  • System Boundary

There is a slight difference between a use case and a business use case. Same applies to Business Actor and Business boundary. Business can be recognized by the cross line.

Stereotypes
  • Include, usage of another use case
  • Extend, optional extension of another use case
Template
  • Number or name of the usecase
  • Summary
  • Actors
  • Pre-condition
  • Scenario
  • Post-condition
  • Alternatives
Miscellaneous
  • Generalization
  • Multiplicity

Activity Diagram[edit]

activity-frame.png Components
  • Start point
  • Transition
  • Action
  • Merge
  • Decision and Guards
  • Split (fork) and Synchronization (join)
  • Input / Ouput
  • Event
  • Swimlane

See also[edit]

top

Reference[edit]

top

  1. UML-Diagrams, uml-diagrams.org is an excellent Website with lots of information on UML. The content of this Website is used for this Article.
  2. Visual Paradigm, UML-Diagrams.