27-08-2014, 11:17 AM
STATE CHART DIAGRAM
STATE CHART.docx (Size: 274.93 KB / Downloads: 8)
AIM:
To draw the STATE CHART DIAGRAM for the software personnel management system.
Theory:
State chart diagrams model the dynamic behavior of individual classes or any
other kind of object. They show the sequences of states that an object goes through, the events that cause a transition from one state to another, and the actions that result from a state change.State chart diagrams are closely related to activity diagrams. The main difference between the two diagrams is state chart diagrams are state centric, while activity diagrams are activity centric. A state chart diagram is typically used to model the discrete stages of an object’s lifetime, whereas an activity diagram is better suited to model the sequence of activities in a process. Each state represents a named condition during the life of an object during which it satisfies some condition or waits for some event. A state chart diagram typically contains one start state and multiple end states. Transitions connect the various states on the diagram. As with activity diagrams, decisions, synchronizations, and activities mayalso appear on state chart diagrams.
State
Definition
A state represents a condition or situation during the life of an object during
which it satisfies some condition or waits for some event. Each state represents the cumulative history of its behavior.
Naming
The name of a state should be unique to its enclosing class, or if nested, within the state. All state icons with the same name in a given diagram represent the same state
Actions
Actions on states can occur at one of four times:
• on entry
• on exit
• do
• on event.
An on event action is similar to a state transition label with the following syntax:
event(args)[condition] : the Action
You must add actions through the Action Specification. States may also appear
on activity diagrams.
Start state
A start state (also called an "initial state") explicitly shows the beginning of a
workflow on an activity diagram or the beginning of the execution of a state machine on a state chart diagram. You can have only one start state for each state machine because each workflow/execution of a state machine begins in the same place. If you use multiple activity and/or state chart diagrams to model a state machine, the same start state can be placed on the multiple diagrams. When you model nested states or nested activities, one new start state can be created in each context.Normally, only one outgoing transition can be placed from the start state. However, multiple transitions may be placed on a start state if at least one of them is labeled with a condition. No incoming transitions are allowed. You can label start states, if desired. State Specifications are associated with each startstate.
Graphical Depiction
The start state icon is a small, filled circle that may contain a name (Begin Process):
End State
An end state represents a final or terminal state on an activity diagram or state
chart diagram. Place an end state when you want to explicitly show the end of a
workflow on an activity diagram or the end of a state chart diagram. Transitions can only occur into an end state; however, there can be any number of end states per context.You can label end states, if desired. State Specifications are associated with each end state.
Graphical Depiction
The end state icon is a filled circle inside a slightly larger unfilled circle that may contain a name (End Process):
State Transition
Definition
A state transition indicates that an object in the source state will perform certain
specified actions and enter the destination state when a specified event occurs or when certain conditions are satisfied. A state transition is a relationship between two states, two activities, or between an activity and a state.You can show one or more state transitions from a state as long as each transition is unique. Transitions originating from a state cannot have the same event, unless there are
conditions on the event.
Naming
You should label each state transition with the name of at least one event that
causes the state transition. You do not have to use unique labels for state transitions because the same event can cause a transition to many different states or activities.Transitions are labeled with the following syntax:
event (arguments) [condition] / action ^ target.sendEvent (arguments)
Only one event is allowed per transition, and one action per event.
Events, conditions and actions must be added by editing the label or through the State Transition Specification.
Nested States
States may be nested to any depth level. Enclosing states are referred to as super states, and everything that lies within the bounds of the super state is referred to as its contents.Nested states are called sub states.
STATE CHART DIAGRAM FOR SOFTWARE PERSONNEL MANAGEMENT SYSTEM
8 DRAW THE PARTIAL LAYERED, LOGICAL ARCHITECTURE DIAGRAM WITH UML PACKAGE DIAGRAM NOTATION
AIM:
To draw the partial layered, logical architecture diagram with UML package diagram notation
Theory:
Package diagram is UML structure diagram which shows structure of the
designed system at the level of packages. The following elements are typically drawn in a package diagram: package, packageable element, dependency, element import, package import, package merge.
PACKAGE DIAGRAM Modelling:
Model diagram is UML auxiliary structure diagram which shows some abstraction or specific view of a system, to describe architectural, logical or behavioural aspects of the system. It could show, for example, architecture of a multi-layered (aka multi-tiered) application - multi-layered application model.
The diagram shows some major elements of the model diagram. Layered
Application is a "container" model which contains three other models – Presentation Layer, Business Layer, and Data Layer. There are dependencies defined between these contained models.
UML Package Diagrams Reference
Package is namespace used to group together elements that are semantically related and might change together. A package could be shown as a rectangle with a small tab attached to the left side of the top of the rectangle.
Package URI Attribute
Package has optional URI attribute which serves as unique identifier of the package. This attribute was introduced in UML 2.4 mostly to support exchange of profiles using XMI. UML 2.4 requires this URI attribute to follow the rules and syntax of the IETF URI specification RFC 2396 (while the more recent version of the URI syntax RFC 3986 released in 2005 rendered the RFC 2396 obsolete). The URI attribute of a package may be rendered in the form {uri=<uri>} after the package name.
Element Import
If element import is public, the imported element will be added to the namespace and made visible outside the namespace. Keyword «import» indicates public element import.
MODEL
Model is a package which captures a view of a system. View is some abstraction of the system describing only those aspects of the system that are relevant to the purpose of the model, at the appropriate level of detail, describing logical or behavioral aspects of the system to a certain category of readers. Model is notated using the ordinary package symbol (a folder icon) with a small triangle in the upper right corner of the large rectangle