Scenario Based Models During The Software Design Process

709 Words Jan 11th, 2016 3 Pages
3.6.2 Scenario Based Modeling
While developing a computer based system, the customer satisfaction cab be done by presenting him the scenario based models during the software design process. In UML the scenario based modeling can be done by developing the scenarios in the form of use cases, activity diagram and swim lane diagrams.
The use case diagram intended to capture the interaction between producer and consumer of the system. All the required functionalities can be exposed by creating the use case diagrams.
Activity Diagram: The activity diagram is a graphical representation for representing the flow of interaction within specific scenarios. It is similar to a flow chart in which various activities that can be performed in the system are represented. This diagram must be read from top to bottom. It consists of forks and branches. The fork is used to remember that many activities can be parallel carried out. This diagram also consists of merge, where multiple branches get combined. Before transitioning into final activity state there comes a join. A typical structure of activity diagram is shown below:

Figure 3.15: Activity Diagram

Swim lane Diagram: The activity diagram shows various activities performed, but it does not tell you who is responsible for these activities. In swim lane diagram the activity diagram is partitioned according to the class who is responsible for carrying out these activities.

Figure no 3.16: Swim lane Diagram

Open Document