Unified Modeling Language: Difference between revisions
Jump to navigation
Jump to search
imported>Eric Evers mNo edit summary |
imported>Eric Evers mNo edit summary |
||
| Line 6: | Line 6: | ||
class diagrams --------- to show the relationships between objects and classes | class diagrams --------- to show the relationships between objects and classes | ||
[[Unified_Modeling_Language/Class_diagram]] | [[Unified_Modeling_Language/Class_diagram|In Detail + Examples]] | ||
sequence diagrams ------ to show time dependency of information flow | sequence diagrams ------ to show time dependency of information flow | ||
[[Erlang_programming_language/Tutorials/Processes|Example]] | [[Erlang_programming_language/Tutorials/Processes|Example]] | ||
Revision as of 12:26, 17 November 2008
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.