Unified Modeling Language: Difference between revisions

From HaFrWiki42
Jump to navigation Jump to search
Line 11: Line 11:


== Use Case Example ==
== Use Case Example ==
{| class="wikitableharm" width="1200"
{| class="wikitableharm" width="1100"
|- style="vertical-align:top;"
|- style="vertical-align:top;"
| width="600" | http://www.uml-diagrams.org/use-case-diagrams/business-use-case-diagram-elements.png
| rowspan="2" width="600" | http://www.uml-diagrams.org/use-case-diagrams/business-use-case-diagram-elements.png
| width="200" | Components:
| rowspan="1" width="250" | '''Components'''
* Use Case
* Use Case
* Actor
* Actor
Line 20: Line 20:
* System Boundary
* System Boundary
There is a slight difference between a use case and a business use case. Same applies to Business Actor and Business boundary.
There is a slight difference between a use case and a business use case. Same applies to Business Actor and Business boundary.
| width="200" | Relations:
| width="200" | '''Stereotypes'''
* Include
* Include, usage of another use case
* Extend
* Extend, optional extension of another use case
| width="200" | Miscellaneous
|- style="vertical-align:top;"
| '''Template'''
* Number or name of the usecase
* Summary
* Actors
* Pre-condition
* Scenario
* Post-condition
* Alternatives
| width="200" | '''Miscellaneous'''
* Generalization
* Generalization
* Multiplicity
* Multiplicity

Revision as of 13:15, 3 February 2015

UML or Unified Modeling (Eglish: Modelling) Language [1].

History

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).

https://upload.wikimedia.org/wikipedia/commons/d/dc/Objektorientieren_methoden_historie.png.


Use Case Example

http://www.uml-diagrams.org/use-case-diagrams/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.

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

See also

top

Reference

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.