Dynamic and Static Modeling

113,236 views 13 slides Jul 10, 2013
Slide 1
Slide 1 of 13
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13

About This Presentation

No description available for this slideshow.


Slide Content

UML- Static modeling and Dynamic Modeling

What is Static Modeling? Static Modeling is used to represent the static constituents of a Software such as : 1.Classes, 2.Objects, 3.Interfaces and 4.Their relationship with each other.

Diagrams used in Static Modeling Static Modeling include two diagrams 1.Class Diagram – these diagrams are used to represent the static elements such as : a. Classes, b. Attributes and c. Relationship between classes 2.Object Diagram – these diagrams are used to represent the instance of the static elements and it also represent the properties of particular instance of a class.

Class Diagrams The class Diagram has three compartment First compartment represents the name of the class. Second compartment represents the attributes of the class. Third compartment represents operation of the class. Class Name Attributes of the class Functions/Methods of the class Class Diagram

Object Diagram These diagram are used to represent the properties of a particular instance of a class, these diagrams are in rectangular shape include two compartments. First compartment represents the name of the Object and the class. Second compartment represents the attributes and the values of the object. Object Name : Class Name Attribute Name=Current Value Object Diagram

Relationships between class and object Diagram All the elements in any software system are connected to each other either physically or logically. So the relationship among classes and object are divided into six forms : Association, Dependency, Generalization, Realization, Recursive aggregation and Qualified association

What is Dynamic Modeling? Dynamic Modeling is used to represent the behavior of the static constituents of a software , here static constituents includes, classes , objects, their relationships and interfaces Dynamic Modeling also used to represents the interaction, workflow, and different states of the static constituents in a software.

Diagrams used in Dynamic Modeling Dynamic Modeling include three diagrams 1.Interaction Diagram 2.Object Diagram 3.Activity Diagram Dynamic Modeling Interaction Diagram Object Diagram Activity Diagram Sequence Diagram Communication Diagram

Interaction Diagram Interaction Diagram –The interaction diagrams are used to visualize the interactive behaviour of the system. So to visualize the interactive behaviour of the dynamic system there's a need to use : Sequence diagram-  The sequence diagram captures the time sequence of message flow from one object to another Collaborative/Communication diagram-   Collaboration diagram describes the organization of objects in a system taking part in the message flow.

Sequence Diagram Sequence Diagram – The sequence diagram captures the time sequence of message flow from one object to another

Communication Diagram Collaborative/Communication diagram-  Collaboration diagram describes the organization of objects in a system taking part in the message flow.

State machine Diagram State machine diagram-  State machine represents the various states of an object that change in response to events during its lifetime. Here, a state refers to the condition of an object during its existence in memory. The state of the object would not change until there’s no relative event occurs. The object have only two state Initial state (starting state)-Represented by a black circle Final state (completion of execution)- Represented by a black circle surrounded by a ring.

Activity Diagram Activity diagram-   Activity diagrams are not only used for visualizing dynamic nature of a system but they are also used to construct the executable system by using forward and reverse engineering techniques. Activity diagram also considered as flow chart just because of visual style but it is not an Flow-Chart.