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.

Event And States-

Events-

• Events are some occurrences that can trigger state transition of an object or a group of objects. Events have a location in time and space but do not have a time period associated with it.

        Examples of events are mouse click, key press, an interrupt, stack overflow, etc

States-

• State transition diagrams or state machines describe the dynamic behavior of a single object. It illustrates the sequences of states that an object goes through in its lifetime, the transitions of the states, the events and conditions causing the transition and the responses due to the events.

Operations-

• Activity is an operation upon the states of an object that requires some time period. They are the ongoing executions within a system that can be interrupted. Activities are shown in activity diagrams that portray the flow from one activity to another.

Nested State Diagrams and Concurrency-

In addition to states of an order that are based on the availability of the items, there are also states that are based on payment authorization. If we look at these states, we might see a state diagram like the one in Figure.

Advanced Dynamic Modeling Concepts-

•  Entry and exit actions are features of advanced dynamic modelling.
•  An entry action is performed when any transition enters the state and an exit action is performed when a state is exited.

A Sample Dynamic Model-

• The dynamic model is used to express and model the behaviour of the system over time. ... Sequence diagrams are used to display the interaction between users, screens, objects and entities within the system. It provides a sequential map of message passing between objects over time.

Functional Modeling

Data Flow Diagram-

•  A Data Flow Diagram (DFD) is traditional visual representation of the information flows within a system.
•  It shows how information enters and leaves the system, what changes the information and where information is stored.
•   It may be used as a communications tool between a systems analyst and any person who plays a part in the system that acts as the starting point for redesigning a system.

Specifying Operations-

•  Functional Modelling gives the process perspective of the object-oriented analysis model and an overview of what the system is supposed to do.
•  It defines the function of the internal processes in the system with the aid of Data Flow Diagrams (DFDs).
•  It depicts the functional derivation of the data values without indicating how they are derived when they are computed, or why they need to be computed.

Constraints-

• A constraint is a packageable element which represents some condition, restriction or assertion related to some element (that owns the constraint) or several elements. Constraint is usually specified by a Boolean expression which must evaluate to a true or false.

OMT(Object modeling techniques)Methdologies-

•  The object modeling techniques is an methodology of object oriented analysis, design and implementation that focuses on creating a model of objects from the real world and then to use this model to develop object–oriented software.
•  Object modeling technique, OMT was developed by James Rambaugh.
• Now-a-days, OMT is one of the most popular object oriented development techniques.
•  It is primarily used by system and software developers to support full life cycle development while targeting object oriented implementations.