CS2353 - OOAD Lab-Ex-A-Ques 1 to 14

CS2353-Object Oriented Analysis and Design-OOAD
For Questions 1 to 10<click here>

Download Ex-A__Questions 1 to 14 <click here>

11. UML INTERACTION DIAGRAMS:

The UML includes interaction diagrams to illustrate how objects interact via messages. They are used for dynamic object modeling. There are two common types: sequence and communication interaction diagrams.                                                                     

Sequence diagram

 

Communication diagram (Collaboration)

12. UML State Machine Diagrams and Modelling:

A UML state machine diagram, as shown below, illustrates the interesting events and states of an object, and the behavior of an object in reaction to an event. Transitions are shown as arrows, labeled with their event. States are shown in rounded rectangles. It is common to include an initial pseudo-state, which automatically transitions to another state when the instance is created.

State machine diagram for a telephone

 

A state machine diagram shows the lifecycle of an object: what events it experiences, its transitions, and the states it is in between these events.

Events:

An event is a significant or noteworthy occurrence. For example:

·         A telephone receiver is taken off the hook.

State:

A state is the condition of an object at a moment in time the time between events. For example:

·         A telephone is in the state of being "idle" after the receiver is placed on the hook and until it is taken off the hook.

Transition:

A transition is a relationship between two states that indicates that when an event occurs, the object moves from the prior state to the subsequent state. For example:

·         When the event "off hook" occurs, transition the telephone from the "idle" to "active" state.

13. UML Activity Diagrams and Modelling:

A UML activity diagram offers rich notation to show a sequence of activities, including parallel activities. It may be applied to any perspective or purpose, but is popular for visualizing business workflows and processes, and use cases.

Applying activity diagram notation to show a data flow model

14. UML Component and Deployment Diagrams:

(i) Component Diagrams:

Components are a slightly fuzzy concept in the UML, because both classes and components can be used to model the same thing.

 

A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment. A component defines its behavior in terms of provided and required interfaces. As such, a component serves as a type, whose conformance is defined by these provided and required interfaces.

(ii) Deployment Diagrams:

Deployment diagram shows the assignment of concrete software artifacts (such as executable files) to computational nodes (something with processing services). It shows the deployment of software elements to the physical architecture and the communication (usually on a network) between physical elements. See figure, Deployment diagrams are useful to communicate the physical or deployment architecture.

 

Conclusion:

Thus the detailed study about Unified Model Language was done along with necessary diagrams.