Posted on July 27, 2008 by afruj
State Machine Diagrams
A state machine diagram models the behaviour of a single object, specifying the sequence of events that an object goes through during its lifetime in response to events.
As an example, the following state machine diagram shows the states that a door goes through during its lifetime.
The door can be in one of three [...]
Filed under: software engineering | Tagged: Choice Pseudo-State, Compound States, Concurrent Regions, Diagrams, Entry Point, Exit Point, History States, Initial and Final States, Junction Pseudo-State, Self-Transitions, State Actions, State Machine Diagrams, States, Terminate Pseudo-State, Transitions | Leave a Comment »
Posted on July 27, 2008 by afruj
Activity Diagrams
In UML, an activity diagram is used to display the sequence of activities. Activity diagrams show the workflow from a start point to the finish point detailing the many decision paths that exist in the progression of events contained in the activity. They may be used to detail situations where parallel processing may occur [...]
Filed under: software engineering | Tagged: Action Constraints, Actions, Activities, Activity Diagrams, Control Flow, Decision and Merge Nodes, Exception Handlers, Expansion Region, Final Node, Fork and Join Nodes, Initial Node, Interruptible Activity Region, Objects and Object Flows, Partition | Leave a Comment »
Posted on July 27, 2008 by afruj
Use Case Diagram
Use Case Model
The use case model captures the requirements of a system. Use cases are a means of communicating with users and other stakeholders what the system is intended to do.
Actors
A use case diagram shows the interaction between the system and entities external to the system. These external entities are referred to as [...]
Filed under: software engineering | Tagged: Actors, Constraints, Diagram, Extending Use Cases, Extension Points, Including Use Cases, Name and Description, Requirements, Scenarios, System Boundary, Use case, Use Case Definition, Use Case Model | Leave a Comment »
Posted on July 27, 2008 by afruj
Component Diagrams
Component diagrams illustrate the pieces of software, embedded controllers, etc., that will make up a system. A component diagram has a higher level of abstraction than a Class Diagram – usually a component is implemented by one or more classes (or objects) at runtime. They are building blocks so a component can eventually encompass [...]
Filed under: software engineering | Tagged: Artifact, Assembly Connector, Association, Component Diagrams, Components with Ports, Deployment Diagrams, Node, Node as Container, Node Instance, Node Stereotypes, Representing Components | Leave a Comment »
Posted on July 27, 2008 by afruj
Object Diagrams
An object diagram may be considered a special case of a class diagram. Object diagrams use a subset of the elements of a class diagram in order to emphasize the relationship between instances of classes at some point in time. They are useful in understanding class diagrams. They don’t show anything architecturally different to [...]
Filed under: software engineering | Tagged: Collaboration, Composite Diagrams, Delegate, Diagrams, Interfaces, Object Diagrams, Occurrence, Part, Port, Represents, Role Binding | 1 Comment »
Posted on July 27, 2008 by afruj
Class Diagrams
The class diagram shows the building blocks of any object-orientated system. Class diagrams depict a static view of the model, or part of the model, describing what attributes and behavior it has rather than detailing the methods for achieving operations. Class diagrams are most useful in illustrating relationships between classes and interfaces. Generalizations, aggregations, [...]
Filed under: software engineering | Tagged: Aggregations, Association Classes, Associations, Class Notation, classes, Dependencies, Diagrams, Generalizations, Interfaces, Nestings, Realizations, Tables, Traces | Leave a Comment »
Posted on July 27, 2008 by afruj
UML is an industry standard modeling language with a rich graphical notation, and comprehensive set of diagrams and elements. A comprehensive UML modeling tool is Enterprise Architect . With UML you can :
Build highly detailed UML 2.1 models.
Manage project complexity.
Reverse engineer legacy code and database schema.
Produce great looking reports.
[...]
Filed under: software engineering | Tagged: Diagrams, UML | 1 Comment »
