This link has been bookmarked by 10 people . It was first bookmarked on 08 Jul 2006, by WittyGuy.
-
04 Jul 08
-
06 Mar 08
-
25 Jun 07
-
shows the grouped modules of a given system modeled using the component diagram.
-
state diagram, activity diagram, sequence diagram, and collaboration diagram
-
Class diagrams and object diagrams form the design view of the system.
-
The 4+1 view is essentially how a system can be viewed from a software life cycle perspective
-
describes the different elements required for deploying a system.
-
the ways a system behaves in response to certain events or actions
-
The static characteristics define what parts the system is made up of.
-
. This diagram is by far most useful when a system is built and ready to be deployed.
-
A component diagram depicts the components culled after the system has undergone the development or construction phase.
-
The collaboration diagram helps to identify all the possible interactions that each object has with other objects.
-
A sequence diagram represents the interaction between different objects in the system.
-
an activity diagram also consists of activities, actions, transitions, initial and final states, and guard conditions.
-
a state diagram also captures the transition of the object's state from an initial state to a final state in response to events affecting the system.
-
The object diagram captures the state of different classes in the system and their relationships or associations at a given point of time.
-
The class diagram classifies the actors defined in the use case diagram into a set of interrelated classes.
-
The use case diagram shows which actors interact with each use case.
-
UML is made up of nine diagrams that can be used to model a system at different points of time in the software life cycle of a system
-
-
22 Dec 05
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.