the traditional approach to requirements. 2 overview what the system does what an event occurs:...
TRANSCRIPT
![Page 1: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/1.jpg)
The Traditional Approach
to Requirements
![Page 2: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/2.jpg)
2
Overview
• What the system does what an event occurs: activities and interactions
• Traditional structured approach to representing activities and interactions
• Diagrams and other models of the traditional approach
• RMO customer support system example shows how each model is related
• How traditional and IE approaches and models can be used together to describe system
![Page 3: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/3.jpg)
3
Traditional and Object-Oriented Views of Activities
![Page 4: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/4.jpg)
4
Requirements Models for the Traditional and OO Approaches
![Page 5: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/5.jpg)
5
Data Flow Diagrams
• Graphical system model that shows all main requirements for an IS in one diagram
– External entity
– Data flow
– Processes
– Data storage
• Easy to read and understand with minimal training
![Page 6: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/6.jpg)
6
Data Flow Diagram Symbols
![Page 7: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/7.jpg)
7
DFD Fragment from the RMO Case
![Page 8: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/8.jpg)
8
DFD Integrates Event Table and ERD
![Page 9: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/9.jpg)
9
DFD and Levels of Abstraction
• Data flow diagrams (DFDs) are decomposed into additional diagrams to provide multiple levels of detail
• Higher level diagrams provide general views of system
• Lower level diagrams provide detailed views of system
• Differing views are called levels of abstraction
![Page 10: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/10.jpg)
10
Layers of DFD Abstraction
![Page 11: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/11.jpg)
11
Context Diagrams
• DFD that summarizes all processing activity
• Highest level (most abstract) view of system
• Shows system boundaries
• System scope is represented by a single process, external agents, and all data flows into and out of the system
• Doesn’t show data stores because they are considered to be within the system scope
![Page 12: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/12.jpg)
12
DFD Fragments
• Created for each event in the event table
• Represents system response to one event within a single process symbol
• Self contained model
• Focuses attention on single part of system
• Shows only data stores required to respond to events
![Page 13: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/13.jpg)
13
DFD Fragments for Course Registration System
![Page 14: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/14.jpg)
14
Event-Partitioned System Model
• DFD to model system requirements using single process for each event in system or subsystem
• Decomposition of the context level diagram
• Sometimes called diagram 0
• Used primarily as a presentation tool
• Decomposed into more detailed DFD fragments
![Page 15: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/15.jpg)
15
Combining DFD Fragments
![Page 16: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/16.jpg)
16
Context Diagram for RMO Customer Support System
![Page 17: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/17.jpg)
17
RMO Subsystems and Events
![Page 18: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/18.jpg)
18
Context Diagram for RMO Order-Entry Subsystem
![Page 19: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/19.jpg)
19
DFD Fragments for RMO Order-Entry System
![Page 20: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/20.jpg)
20
Decomposing DFD Fragments
• Sometimes DFD fragments need to be explored in more detail
• Broken into subprocesses with additional detail
• DFD numbering scheme:
– Does not equate to subprocess execution sequence
– It is just a way for analyst to divide up work
![Page 21: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/21.jpg)
21
Order-Entry Subsystem
Customer
Shipping
Bank
Management Accounting
Credit bureau
2
Create neworder
1
Look up itemavailability
3
Updateorder
4
Produceorder
summaryreports
5
Producetransactionsummaryreports
Oder item CatalogProduct item CustomerInventory item OrderOrder transaction
change confirmation
Order change request
Item inquiry
Item availability details
Order change details
Item availabilitydetails
Transaction
Ordersummary
reports
Ordertransaction
Order item
Transactionsummaryreports
Transaction
Creditinfo
Credit info
Catalog
Valid new order
Item availability
Customer info
Order details
New order
Order comfirmation
![Page 22: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/22.jpg)
22
Physical and Logical DFDs
• Logical model
– Does not tell how system is implemented
• Physical model
– Describes assumptions about implementation technology
– Developed in last stages of analysis or in early design
![Page 23: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/23.jpg)
23
Detailed Diagram for Create New Order
![Page 24: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/24.jpg)
24
Physical DFD for scheduling courses
![Page 25: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/25.jpg)
25
List of Activities
![Page 26: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/26.jpg)
26
Stock Log
![Page 27: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/27.jpg)
27
Current Logical System and New Logical System
Current Logical System
New Logical System
![Page 28: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/28.jpg)
28
Evaluating DFD Quality
• Readable
• Internally consistent
• Accurately represents system requirements
• Reduces information overload: Rule of 7 +/- 2– Single DFD should have not more than 7 +/-2
processes– No more than 7 +/- 2 data flows should enter or
leave a process or data store on a single DFD
• Minimizes required number of interfaces
![Page 29: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/29.jpg)
29
Data Flow Consistency Problems
• Differences in data flow content between a process and its process decomposition
• Data outflows without corresponding inflows
• Data inflows without corresponding outflows
• Results in unbalanced DFDs
![Page 30: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/30.jpg)
30
Consistency Rules
• All data that flows into a process must:
– Flow out of the process or
– Be used to generate data that flow out of the process
• All data that flows out of a process must:
– Have flowed into the process or
– Have been generated from data that flowed into the process
![Page 31: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/31.jpg)
31
Unnecessary Data Input: Black Hole
![Page 32: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/32.jpg)
32
Process with Impossible Data Output: Miracle
![Page 33: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/33.jpg)
33
Process with Unnecessary Data Input
![Page 34: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/34.jpg)
34
Process with Impossible Data Output
![Page 35: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/35.jpg)
35
Incorrect and Correct Ways to Draw DFD
![Page 36: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/36.jpg)
36
Incorrect and Correct Ways to Draw DFD
![Page 37: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/37.jpg)
37
Incorrect and Correct Ways to Draw DFD
![Page 38: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/38.jpg)
38
Balancing DFDs
• When decomposing a DFD, you must conserve inputs to and outputs from a process at the next level of decomposition
• This is called balancing
![Page 39: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/39.jpg)
39
Unbalanced Set Of Data Flow Diagrams
![Page 40: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/40.jpg)
40
Balancing DFDs
• We can split a data flow into separate data flows on a lower level diagram
![Page 41: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/41.jpg)
41
Documentation of DFD Components
• Lowest level processes need to be described in detail
• Data flow contents need to be described
• Data stores need to be described in terms of data elements
• Each data element needs to be described
• Various options for process definition exist
![Page 42: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/42.jpg)
42
Data Flow Definitions
• Textual description of data flow’s content and internal structure
• Often coincide with attributes of data entities included in ERD
![Page 43: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/43.jpg)
43
Data Flow Definition- Example
New-Order = Customer-Name + Customer-Address + Credit-Card-Information + {Item-Number + Quantity)N
1
![Page 44: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/44.jpg)
44
Data Store Definitions
• A data store on the DFD represents a data entity on the ERD
![Page 45: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/45.jpg)
45
Data Element Definitions
• Data type description
– e.g. string, integer, floating point, Boolean
– Sometimes very specific
• Length of element
• Maximum and minimum values
• Data dictionary – repository for definitions of data flows, data stores, and data elements
![Page 46: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/46.jpg)
46
A Data Structure for a Data Flow
DATA STRUCTURE
ORDER=ORDER NUMBER +ORDER DATE+[ PERSONAL CUSTOMER NUMBER, CORPORATE ACCOUNT NUMBER]+SHIPPING ADDRESS=ADDRESS+(BILLING ADDRESS=ADDRESS)+1 {PRODUCT NUMBER+ PRODUCT DESCRIPTION+ QUANTITY ORDERED+ PRODUCT PRICE+ PRODUCT PRICE SOURCE+ EXTENDED PRICE } N+SUM OF EXTENDED PRICES+PREPAID AMOUNT+(CREDIT CARD NUMBER+EXPIRATION DATE)(QUOTE NUMBER)
ADDRESS=(POST OFFICE BOX NUMBER)+STREET ADDRESS+CITY+[STATE, MUNICIPALITY]+(COUNTRY)+POSTAL CODE
ENGLISH ENTERPRETATION
An instance of ORDER consists of:ORDER NUMBER andORDER DATE andEither PERSONAL CUSTOMER NUMBER
or CORPORATE ACCOUNT NUMBERand SHIPPING ADDRESS (which is equivalent to ADDRESS)and optionally: BILLING ADDRESS (which is equivalent to ADDRESS)and one or more instances of:
PRODUCT NUMBER andPRODUCT DESCRIPTION andQUANTITY ORDERED andPRODUCT PRICE andPRODUCT PRICE SOURCE andEXTENDED PRICE
and SUM OF EXTENDED PRICES andPREPAID AMOUNT andoptionally: both CREDIT CARD NUMBER and EXPIRATION DATE
An instance of ADDRESS consists of:optionally: POST OFFICE BOX NUMBER andSTREET ADDRESS andCITY andEither STATE or MUNICIPALITYand optionally: COUNTRYand POSTAL CODE
![Page 47: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/47.jpg)
47
Data Flow Diagram and Process Specifications
![Page 48: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/48.jpg)
48
Goal of Creating Process Specifications
• Reduce process ambiguity.
• Obtain a precise description of what is accomplished.
• Validate the system design, including data flow diagrams and the data dictionary.
![Page 49: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/49.jpg)
49
Process Specification Format
• Process specifications link the process to the DFD and the data dictionary.
• The following information should be entered:– The process number, which must match the process ID on the
data flow diagram.– This allows an analyst to work or review any process and easily
locate the data flow diagram containing the process.– The process name, the same as displays within the process
symbol on the DFD.– A brief description of what the process accomplishes.– A list of input and output data flow, using the names found on the
data flow diagram.– Data names used in the formulae or logic should match the data
dictionary, for consistency and good communication.– A description of the process logic.
![Page 50: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/50.jpg)
50
Process Specification Form
![Page 51: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/51.jpg)
51
Structured English
• Method of writing process specifications
• Combines structured programming techniques with narrative English
• Well suited to lengthy sequential processes or simple control logic (single loop or if-then-else)
• Ill-suited for complex decision logic or few (or no) sequential processing steps
![Page 52: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/52.jpg)
52
Structured English Example
![Page 53: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/53.jpg)
53
Process 2.1 and Structured English Process Description
![Page 54: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/54.jpg)
54
Decision Tables
• Can summarize complex decision logic better than structured English
• Incorporates logic into the table or tree structure to make descriptions more readable
![Page 55: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/55.jpg)
55
Decision Table Format
![Page 56: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/56.jpg)
56
A Simple Decision Table
![Page 57: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/57.jpg)
57
A Simple Decision Table
![Page 58: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/58.jpg)
58
Constructing a Decision Table
1. Identify each decision variable and its allowable value (or value range)
2. Compute the number of decision variable combinations as the product of the number of values of each decision variable.
3. Construct a table with one more columns than the number of decision variable combinations computed in step 2. – The table should have a row for each decision variable and a
row for each process action or computation.
4. Assign the decision variable with the fewest values to the first row of the table. – Put the decision variable name in the 1st column. – Divide the remaining columns into sets of column for each
decision variable value
![Page 59: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/59.jpg)
59
Constructing a Decision Table (con’t)
5. Choose the next decision variable with the fewest values for the 2nd row.
– Put the variable’s name in the 1st column.– Compute the number of column groups as the product of the
number of values of this variable and all the variables above it in the table.
– Divide the remaining columns into the computed number of groups, and insert values in a regular pattern.
6. Continue inserting rows as instructed step 5 until all decision variables have been included in the table.
7. Add a row for each calculation or action. – For each calculation cell, insert the appropriate constant value
or formula for the combination of decision variable values that appear above the cell in the same column.
– For each action cell, place a check mark in the cell if that action is performed when the decision variables have the values shown in the column above the cell.
![Page 60: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/60.jpg)
60
Constructing a Decision Table- Example
• Decision variables– year to date (YTD) purchases: 2 ranges (< $250 and >= $250– number of items ordered: 2 ranges (<= 3 and >=4)– delivery day: 3 values (next day, 2nd day, and 7th day)
• Combination values: 2x2x3 = 12• YTD purchases and number of items ordered are the
fewest value, chose YTD purchases: 2 values– Create 2 groups of 12/2 = 6 columns and label one for each
possible value
• Next row, number of items => 4 group of 3 columns– Insert the value ranges for number of items into the column
groups
![Page 61: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/61.jpg)
61
Constructing a Decision Table- Example
• Delivery day, we simply insert the value of delivery date into individual column
• Insert the row containing formulas and values for the shipping charges– Each cell contains a value of formula for the
combination of decision variable values in the column above
![Page 62: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/62.jpg)
62
Reduced Decision Table
![Page 63: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/63.jpg)
63
Decision Tables
• Four main problems that can occur in developing decision tables:– Incompleteness.– Impossible situations.– Contradictions.– Redundancy.
![Page 64: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/64.jpg)
64
Impossible Situation
![Page 65: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/65.jpg)
65
Redundancy and Contradictions
![Page 66: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/66.jpg)
66
Eliminating Repetitious Rules Requiring the Same Action
![Page 67: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/67.jpg)
67
Modeling Logic with Decision Trees
• A graphical representation of a decision situation• Decision situation points are connected together
by arcs and terminate in ovals• Two main components
– Decision points represented by nodes– Actions represented by ovals
• Read from left to right• Each node corresponds to a numbered choice on
a legend• All possible actions are listed on the far right
![Page 68: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/68.jpg)
68
Generic Decision Tree
![Page 69: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/69.jpg)
69
Decision Tree for Calculating Shipping Charges
![Page 70: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/70.jpg)
70
Components of a Traditional Analysis Model
![Page 71: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/71.jpg)
71
Summary
• Data flow diagrams (DFDs) used in combination with event table and entity-relationship diagram (ERD) to model system requirements
• DFDs model system as set of processes, data flows, external agents, and data stores
• DFDs easy to read - graphically represent key features of system using small set of symbols
• Many types of DFDs: context diagrams, DFD fragments, subsystem DFDs, event-partitioned DFDs, and process decomposition DFDs
![Page 72: The Traditional Approach to Requirements. 2 Overview What the system does what an event occurs: activities and interactions Traditional structured approach](https://reader036.vdocuments.us/reader036/viewer/2022081519/56649e0b5503460f94af3b1e/html5/thumbnails/72.jpg)
72
Summary (continued)
• Each process, data flow, and data store requires detailed definition
• Analyst may define processes as structured English process specification, decision table, decision tree, or process decomposition DFD
• Process decomposition DFDs used when internal process complexity is great
• Data flows defined by component data elements and their internal structure