Unified Modeling Language: Difference between revisions
Jump to navigation
Jump to search
imported>Eric Evers mNo edit summary |
mNo edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
Unified Modeling Language | {{subpages}} | ||
The '''Unified Modeling Language (UML}''' is a standard for diagramming program design and development. | |||
UML is a standard for diagramming program design and development. | |||
The main types of diagrams that belong to UML are: | The main types of diagrams that belong to UML are: | ||
| Line 20: | Line 19: | ||
James Rumbaugh, Ivar Jacobson and Grady Booch are together considered the main | James Rumbaugh, Ivar Jacobson and Grady Booch are together considered the main | ||
contributors to UML historically. Together they formed Rational Software. | 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.