Chapter Summary
Chapter 12
A Picture Is Worth 1024 Words
© Karl E. Wiegers
1
2
Models provide high-level view, SRS provides details. Models must be consistent with SRS and each other. Conflicts between alternative views reveal errors.
Requirements Analysis and Modeling
Modeling Techniques 12.1 Structured analysis models
1.a)data flow diagram & ER- Diagram
1.b)state-transition diagram
1.c) Flow Chart (Swimlane Diagram)
1.d) Dialog map
12.2 Object-oriented analysis models
2.a)use case diagram
2.b)class diagram
2.c)collaboration diagram
2.d)sequence diagram
2.e)state chart diagram
2.f)activity diagram
12.3 Decision Table and Decision Tree
3
1.a) Data Flow Diagram
4
5 Level 1 data flow diagram for the Chemical Tracking System
6
See Supplement
7Figure 11-2. Partial entity-relationship diagram for the Chemical Tracking System
1.b) State-Transition Diagrams
8
9
Partial state-transition diagram for a home security system
10
State-transition diagram for a chemical request in the CTS
11
1.c) Flow Chart – describes the flow of logic
12
The swim lane differs from flowcharts in that processes and decisions are grouped visually by placing them in lanes. Parallel lines divide the chart into lanes, with one lane for each person, group or sub-process. Lanes are labeled to show how the chart is organized.
1d) Dialog Map
13
Represents a user interface design at high level of abstraction.
It shows the dialog elements in the system and the navigation links among them without showing the detailed screen design.
14
15
16
17
Find incorrect or missing transitions early Find incorrect or missing requirements early Find navigation dead-ends Define user back-out and cancellation routes Spot reuse opportunities or redundancies in UI design Can partition the user interface into components Can draw dialog maps hierarchically, to control scope and complexity
Benefits of Dialog Map
2.a) Use Case Diagram (as discussed in chapter 8)
18
2.b) Class Diagrams
19
20
Class diagram for part of the Chemical Tracking System
21
2.c) Collaboration Diagram (interaction 1)
Ex. Library Management
22
2.d) Sequence Diagram (interaction 2)
Ex. ATM
23
See Supplement
24
2.e) State Chart Diagram (similar to “State-Transition-Diagram”)
ATM example
25
Check Events in S.D.
26
2.f) Activity diagram is a flowchart-based diagram showing flow of control from activity to activity. It shows concurrency, branch, control flow and object flow.
27
Swim-lane, furthermore, is used for partitioning the activity states.
28
Summary
State Chart Diagram
3.b) Decision Tables and Decision Trees
Techniques for representing what the system to do when complex logic and decision come into play.
29
A Sample Decision Table
30
31
Decision Tree
A Sample Decision Tree
32
Ex. Sample Decision Tree for CTS
END
33