Unified Modeling Language: Difference between revisions
Jump to navigation
Jump to search
imported>Eric Evers (New page: Unified Modeling Language Or UML for short is a standard for diagramming program design and development. The main types of diagrams that belong to UML are) |
mNo edit summary |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Unified Modeling Language | {{subpages}} | ||
The '''Unified Modeling Language (UML}''' is a standard for diagramming program design and development. | |||
The main types of diagrams that belong to UML are: | |||
class diagrams --------- to show the relationships between objects and classes | |||
[[Unified_Modeling_Language/Class_diagram|In Detail + Examples]] | |||
sequence diagrams ------ to show time dependency of information flow | |||
[[Erlang_programming_language/Tutorials/Processes|Example]] | |||
collaboration diagrams - to show time dependency of information flow between objects | |||
use case diagrams ------ to show a high level example of system functionality as it relates to | |||
information flow between a system and its users | |||
state diagrams --------- to show how messages change the state of objects over time | |||
[[State_diagram|Example]] | |||
component diagrams ----- to show how objects are contained | |||
deployment diagrams ---- to show time dependencies in deployment | |||
entity relationship diagrams - | |||
James Rumbaugh, Ivar Jacobson and Grady Booch are together considered the main | |||
contributors to UML historically. Together they formed Rational Software. | |||
[[Category:Suggestion Bot Tag]] | |||
Latest revision as of 16:01, 2 November 2024
The Unified Modeling Language (UML} is a standard for diagramming program design and development.
The main types of diagrams that belong to UML are:
class diagrams --------- to show the relationships between objects and classes
In Detail + Examples
sequence diagrams ------ to show time dependency of information flow
Example
collaboration diagrams - to show time dependency of information flow between objects
use case diagrams ------ to show a high level example of system functionality as it relates to
information flow between a system and its users
state diagrams --------- to show how messages change the state of objects over time
Example
component diagrams ----- to show how objects are contained
deployment diagrams ---- to show time dependencies in deployment
entity relationship diagrams -
James Rumbaugh, Ivar Jacobson and Grady Booch are together considered the main contributors to UML historically. Together they formed Rational Software.