0% found this document useful (0 votes)
2 views

Advance Software Modeling_3_1736758654607

The document discusses events in systems, categorizing them into signal events, change events, and time events, each defined by specific conditions and representations in UML. It also explains state diagrams, which depict system behavior through finite state transitions, and introduces features like nested and concurrent state diagrams to manage complexity. Additionally, it highlights the relationship between class models and state diagrams, emphasizing how states represent allowable changes in class objects.

Uploaded by

saxehiw660
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views

Advance Software Modeling_3_1736758654607

The document discusses events in systems, categorizing them into signal events, change events, and time events, each defined by specific conditions and representations in UML. It also explains state diagrams, which depict system behavior through finite state transitions, and introduces features like nested and concurrent state diagrams to manage complexity. Additionally, it highlights the relationship between class models and state diagrams, emphasizing how states represent allowable changes in class objects.

Uploaded by

saxehiw660
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 26

Events

• Events are the incidents that take place at a particular


time. For example, a train departs from the station, a
person switches off the button and so on.
• some common type:
• 1. Signal Event
• The signal event describes, sending and receiving of
information from one object to another at a particular time.
This event specifies one-way transmission.
• 2. Change Event
• A change event is an event that occurs whenever a boolean
expression is satisfied. This boolean expression is checked
continuously and whenever the expression result changes
from true to false or from false to true the change event
occurs.
• The UML representation of the change event is as
follow:
• when(room temperature < heating point)
• In UML the change event is expressed using ‘when’
keyword followed by the boolean expression.
• Time Event
• The time event is the event that occurs at a specified
time or after the specified time elapsed. The absolute
time event is represented in the UML using the ‘when‘
keyword followed by the parenthesis with a time
expression. The Time interval event is represented by
the ‘after‘ keyword followed parenthesis with
expression evaluating the time duration.
• when(time = 18:30)
after(10 seconds)
state diagram behavior
• A state diagram is used to represent the condition of the system
or part of the system at finite instances of time. It's a behavioral
diagram and it represents the behavior using finite state
transitions. State diagrams are also referred to as State
machines and State-chart Diagrams.
Features of State Diagram

□ Two major features are introduced for


controlling complexity and
combinatorial explosion in state
diagrams Nested State
◦ Nested state diagrams Diagrams
◦ Concurrent state diagrams
□ Many other features are also added
◦ propagated transitions
◦ broadcast messages
◦ actions on state entry, exit
Concurrent State
◦… Diagrams
Super/substates
□ When one state is complex, you
can include substates in it.
◦ drawn as nested rounded
rectangles within the larger
state
Nested State Diagram
Superstates (nested states)
Concurrency in state diagrams
◦ concurrency is a property of systems in which several computations are
executing simultaneously, and potentially interacting with each other.
◦ Dashed line indicates that an order is in two different states, e.g. Checking &
Authorizing
◦ When order leaves concurrent states, it’s in a single state: Canceled, Delivered
or Rejected
◦ Concurrent Sub states - Used when two or more state diagrams
are executing concurrently within a single object.
relation of class and state model.
• A state diagram shows the behavior of the class. A class
model shows the relationship between two or more classes.
It includes its properties/attributes... A state is an allowable
sequence of changes of objects of a class model
Notations
State model case study

You might also like