Activity Diagram, Swim-lane Diagram, Sequence Diagram

1. Software Engineering Modeling and Design
State Machine Mr. N. L. Shelake Department of Information Technology
INTERACTION AND BEHAVIOR MODELING

2. Software Engineering Modeling and Design
Activity Diagram:
 Activity and actions
 Initial and Final Activity
 Activity Edge
 Decision and Merge Points
 Fork and Join
 Input and Outputs Pins
 Activity Groups
 Activity Partitions, Constraints on Action
State Machine Mr. N. L. Shelake Department of Information Technology

3. Software Engineering Modeling and Design
Activity Diagram
 supplements the use case by providing a graphical representation of the
flow of interaction within a specific scenario
 uses rounded rectangles to imply a specific system function
 arrows to represent flow through the system
 decision diamonds to depict a branching decision
 solid horizontal lines to indicate that parallel activities are occurring
 adds additional detail not directly mentioned by the use case
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

4. Software Engineering Modeling and Design
Activity Diagram Notation’s
 Initial state
 Activity Diagrams start from this step.
 Also known as the entry state.
 Start Node is the starting point of any activity
 Action state/ Activity
 A step in which the users or software performs a certain
task.
 It represents an action that is going to take place at this
stage of the software system
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

5. Software Engineering Modeling and Design
Activity Diagram Notation’s
 Control Flow/ Connectors
 Shows the directional flow, or control flow, of the
activity.
 Also known as control flow
 Decision Node
 A conditional node or a decisional node is one where
there are multiple options available
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

6. Software Engineering Modeling and Design
Activity Diagram Notation’s
 Fork Nodes
 A fork node has one incoming edge and numerous
outgoing edges.
 Splits a single activity flow into two concurrent activities
 Join Node
 Combines two concurrent activities and re-introduces
them to a flow where only one activity occurs at a time
 A join is one where two results of concurrent activities
add and form a single result.
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

7. Software Engineering Modeling and Design
Activity Diagram Notation’s
 End State
 Marks the end state of an activity and represents the
completion of all flows of a process
 Flow Final
 Represents the end of a specific process flow.
 should be placed at the end of a process in a single
activity flow.
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

8. Software Engineering Modeling and Design
Activity Diagram Notation’s
 Note
 Allows the diagram creators or collaborators to
communicate additional messages that don't fit within
the diagram itself.
 Flow Final
 Allows the creator to model a repetitive sequence within
the option loop symbol.
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

9. Software Engineering Modeling and Design
Activity Diagram Notation’s
 Send Signal Symbol
 Indicates that a signal is being sent to a receiving
activity.
 Receive Signal Symbol
 Demonstrates the acceptance of an event.
 After the event is received, the flow that comes from this
action is completed.
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

10. Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

11. Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

12. Software Engineering Modeling and Design
Swimlane Diagram
 useful variation of the activity diagram and allows you to represent the flow
of activities described by the use case and at the same time indicate which
actor or analysis class has responsibility for the action
 Responsibilities are represented as parallel segments that divide the diagram
vertically, like the lanes in a swimming pool
 Three analysis classes—Homeowner, Camera, and Interface—have direct
or indirect responsibilities in the context of the activity diagram
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

13. Software Engineering Modeling and Design
Swimlane diagram for access camera surveillance
via internet
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

16. Software Engineering Modeling and Design
Swimlane diagram for ATM System
Unit-II Requirement Analysis Mr. N. L. Shelake Department of Information Technology

17. Software Engineering Modeling and Design

18. Software Engineering Modeling and Design

19. Software Engineering Modeling and Design

20. Software Engineering Modeling and Design