CS603 Final Term Short Notes by Almas Afzal

CS603 SOFTWARE ARCHITECTURE & DESIGN SHORT NOTES FOR FINAL-TERM

TOPIC 77 TO 227 · Topic_77 · (Modeling State Machine) · State Machine Modeling:

State Machine Modeling is a behavioral modeling technique used in Software Design & Architecture to represent the states an object can be in and how it transitions between these states in response to events. This approach is especially useful for modeling reactive systems like user interfaces, devices, protocols, or game logic.

FOR MCQ:

State________ A specific condition or situation of an object during its life cycle. Event________An occurrence that may trigger a transition (e.g., user input, timeout). Transition________A movement from one state to another triggered by an event. Action________A behavior that occurs due to an event or transition. Initial State________The default starting point of a state machine. Final State________The terminating point of the state machine

Why Use State Machines in Software Design?

•  Clarifies complex logic through visual representation.
•  Identifies all possible states and transitions.
•  Simplifies testing and debugging.
•  Helps in managing life-cycle of objects (e.g., orders, users, devices).

UML State Machine Diagram

A UML State Machine Diagram visually represents the states and transitions of a class or system.

Basic Syntax:

•  Rounded rectangles represent states.
•  Arrows represent transitions.
•  Labels on arrows show the triggering event and action.

Sample:

Modeling Steps:

1. Identify the object or process to be modeled.
2. List all possible states the object can be in.
3. Define events that cause transitions between states.
4. Draw the state diagram using standard UML notations.
5. Add actions or activities that occur during transitions or inside states.

Topic_78 & 79 · (State Design Pattern) · Definition:

The State Design Pattern is a behavioral design pattern that allows an object to alter its behavior when its internal state changes. The object will appear to change its class.

When to Use:

Use the State Pattern when:

•  An object must change its behavior based on internal state.
•  You want to avoid large if-else or switch statements scattered across the code.
•  You have many states with distinct behaviors, and adding new states should be easy.

Advantages:

•  Simplifies complex conditional logic.
•  Makes state transitions explicit and organized.
•  Follows Open/Closed Principle (easily add new states).

Disadvantages:

•  Increases the number of classes.
•  Can be overkill for simple state logic.