8/13/2019 3309 Requirements Gathering1
1/37
Systems Engineering Process:
Requirements Gathering
8/13/2019 3309 Requirements Gathering1
2/37
Topic Agenda
Recall: Basics of Requirements Gathering
Its All About the C u s t o m e r
Process Mapping
Process Analysis
Requirements Documentation
Recall: Basics of Requirements Gathering
8/13/2019 3309 Requirements Gathering1
3/37
Requirements Gathering
Preliminary Investigation
Requirements Gathering
Operations & Support
Global Deployment &Change Management
Scale & Scope
System & Data Analysis
Requirements Determination RequirementsAnalysis
What is done? Why is it done? What should be done?
Where is it done? Why is it done there? Where should it bedone?
When (how often)is it done?
Why is it done then? When (how often)should it be done?
Who does it? Why does this (these)person do it?
Who should do it?
How is it done? Why is it done thatway?
How should it bedone?
Design & Development
8/13/2019 3309 Requirements Gathering1
4/37
Key to Requirements Gathering?
Good Communication!
Two volunteers please..
8/13/2019 3309 Requirements Gathering1
5/37
Topic Agenda
Recall: Basics of Requirements Gathering
Its All About Your C u s t o m e r
Process Mapping
Process Analysis
Requirements Documentation
Its All About Your C u s t o m e r
8/13/2019 3309 Requirements Gathering1
6/37
Create a Customer Partnership!(Extending the Preliminary Investigation Findings)
Step 1: Obtain authorization to proceed
Step 2: Identify the necessary information
Step 3: Initiate a fact-finding search
Obtain & analyze org charts to determine WHO to interview Conduct interviews with appropriate departments/customers Review current system documentation Observe current operations/process If necessary, conduct brief survey
Step 4: Analyze collected information
Step 5: Present findings & recommendations to management
Identify Next Level Info Needed
Cross-Functional Steering Team Develop Current State Process Docs
(include strengths & weaknesses) Develop Current Functionality Docs Observe Current State & Adjust Doc Validate w/End Users & Adjust Docs
Develop Next Gen Process Docs Develop Next Gen Functional Docs Validate w/End Users & Adjust Docs
8/13/2019 3309 Requirements Gathering1
7/37
8/13/2019 3309 Requirements Gathering1
8/37
Typical Grocery Complex Supply Chain
Vendors/Markets
Private LabelPlants
Raw MaterialSuppliers
DC
DC withMerchandising
Office
DC
Corporate/Merchandising Office
Corporate/MerchandisingOffice
Corporate/MerchandisingOffice
Acquired Business NAcquired Business 2
Acquired Business 1
Division 1Stores
Division 2 Stores
Division MStores
8/13/2019 3309 Requirements Gathering1
9/37
Typical Grocery Supply Chain Elements
8/13/2019 3309 Requirements Gathering1
10/37
DSD Grocery Supply Chain Elements
8/13/2019 3309 Requirements Gathering1
11/37
DSD System Steering Team
Corporate Buyer w/Dept Management & DSD Background*
Information Technology Lead
Supply Chain Management Analyst*
Warehouse Asst Manager*
Technical Documentation Specialist
Potentially, a Vendor Representative*
* Subject matter experts
8/13/2019 3309 Requirements Gathering1
12/37
Current Typical Process Diagram
Deliveries (large vendor) twice a week according to schedule Transmit from store to corporate by delivery close of business Invoice & payment within 3-4 weeks
8/13/2019 3309 Requirements Gathering1
13/37
Current Process Strengths & Weaknesses
Time for Store
Inventory Costs Risk of Non-Sale
Shelf Hogging
Backroom Dumping Control of Product Mix
BOL Data Entry Error
Invoice Matching Error
Advantages Disadvantages
8/13/2019 3309 Requirements Gathering1
14/37
Topic Agenda
Recall: Basics of Requirements Gathering
Its All About Your C u s t o m e r
Process Mapping
Process Analysis
Requirements Documentation
Process Mapping
8/13/2019 3309 Requirements Gathering1
15/37
Process Mapping
Choose a Process & Define its Objective
Identify the Process Owner(s)
Establish the Process Boundaries
Identify Process Customers & Suppliers
Flowchart the Process
8/13/2019 3309 Requirements Gathering1
16/37
Recall Flow Chart Guidelines
1. Boxes indicate process steps
2. Arrows indicate the process flow
3. Columns can be used to indicate function or humanrole (I.e., buyer) involved
4. Multiple entry and exit points are allowed
5. Shows cross-functional flows
6. Indicate conditional paths w/comments on arrows
8/13/2019 3309 Requirements Gathering1
17/37
Try This..
Map the process of making a peanut butter sandwich
Identify the sources of defects (failure to meet customerexpectations)
8/13/2019 3309 Requirements Gathering1
18/37
The Myth
What I do is unique
It cant be described
It cant be measured
8/13/2019 3309 Requirements Gathering1
19/37
The Facts
All work can be viewed as a process
All work can be mapped
All activities are measurable
8/13/2019 3309 Requirements Gathering1
20/37
Typical Supplier/Owner/Customer Interests
Clear understanding of steps & importance
Clear understanding of time involved
Efficiency
Reliable results
8/13/2019 3309 Requirements Gathering1
21/37
Example: Dominos Pizza
Worlds #1 Pizza Delivery
Worlds #2 Pizza Chain (behind Pizza Hut)
$1.8 Billion Sales; 12,500 Employees
Founded in 1960 w/$500 investment
7100 Stores in 65 Countries
85% of Stores are Franchised 18 Distribution Centers Throughout US
7+ Million Pizzas/Week; 340M Lbs. Dough/Year
8/13/2019 3309 Requirements Gathering1
22/37
WHO influences what to DO
Dominos Order Taking: Customer View Customer Dominos
Place Order Take Order
Deliver OrderReceive Order
Collect PaymentPay Driver
8/13/2019 3309 Requirements Gathering1
23/37
Order Taking: Dominos View
Customer CookPlace Order
Manager DriverTake Order
Make PizzaScheduleOrder
PackageOrder
ScheduleDelivery
RequestFeedback
GiveFeedback
Return toStore
CollectPaymentPay Driver
ReceiveOrder
DeliverOrder
Feedback
CustomerSwim Lane
DriverSwim Lane
8/13/2019 3309 Requirements Gathering1
24/37
Topic Agenda
Recall: Basics of Requirements Gathering
Its All About Your C u s t o m e r
Process Mapping
Process Analysis
Requirements Documentation
Process Analysis
8/13/2019 3309 Requirements Gathering1
25/37
Process Performance
Number of Defects(Failure to Meet Customer Expectations)
Cycle Time
Effort/Energy
8/13/2019 3309 Requirements Gathering1
26/37
Identify Next Level Info Needed
Develop Next Gen Process Docs Develop Next Gen Functional Docs Validate w/End Users & Adjust Docs
Process Mapping & Analysis
Current FutureImprovements
What is the current cycle time & defect* rate?
With current resources, whats the best? What is very best that could be achieved?
* Defect is any failure to meet customerexpectations
Identify Steering Team Develop Current State Process Docs
(include strengths & weaknesses) Develop Current Functionality Docs Observe Current State & Adjust Docs
Validate w/End Users & Adjust Docs
8/13/2019 3309 Requirements Gathering1
27/37
Identifying Next Generation Processes
Type Performance
Description Complexity
Size VariabilitySuppliers CustomersSteps
Defects Cycle-TimeRepetitive Non-Repetitive
Process
8/13/2019 3309 Requirements Gathering1
28/37
Topic Agenda
Recall: Basics of Requirements Gathering
Its All About Your C u s t o m e r
Process Mapping
Process Analysis
Requirements Documentation Requirements Documentation
8/13/2019 3309 Requirements Gathering1
29/37
Identify Next Level Info Needed
Identify Steering Team Develop Current State Process Docs
(include strengths & weaknesses) Develop Current Functionality Docs Observe Current State & Adjust Docs Validate w/End Users & Adjust Docs
Develop Next Gen Process Docs Develop Next Gen Functional Docs Validate w/End Users & Adjust Docs
Recall: Process Mapping & Analysis
V i f C D
8/13/2019 3309 Requirements Gathering1
30/37
Variety of Common Documents
High-Level Requirements Document
Functionality Hit List
Use Cases
Hi h L l S (P /F i li ) D
8/13/2019 3309 Requirements Gathering1
31/37
High-Level System (Process/Functionality) Doc
Typically in MS Word or Adobe PDF
Typically 20-40 pages in length (max 50 pages)
Provide general flavor of system objectives, expected use &
functionality information
Release priority if appropriate
Clear indication of people processing vs. automated
C f Hi h L l R i D
8/13/2019 3309 Requirements Gathering1
32/37
Contents of High-Level Requirements Doc
Document Edit Log Table of Contents Executive Summary (1-2 paragraphs)
Business Attributes Summary User Roles Involved Supply Chain &/or Product Attributes Summary 1-4 Most Critical Processes/Steps
Business Process Step General Information User Actions, Frequency, Functionality Required Small Examples to Articulate Desired Support
Appendices with Really Detailed Stuff (I.e, Report List)
F ti lit Hit Li t
8/13/2019 3309 Requirements Gathering1
33/37
Functionality Hit List
Line items of functionality needs
Content: Functional Item ID
Process & Sub-Process
Functionality Group
Functionality Description
Functionality Priority
Targeted Release
U C
8/13/2019 3309 Requirements Gathering1
34/37
Use Cases
Represents steps in a specific process
External entity ( actor or role ) requests system to perform process or function
Examples:
Buyer orders a book on Amazon.com
Driver pulls in & requests a car wash
Student shows up for a class
Use cases can be linked or referenced to other use cases
Use Case Documents
8/13/2019 3309 Requirements Gathering1
35/37
Use Case Documents
Summary List
High Level Process Use Cases
Detailed Process Use Cases
Special Function/Exception Handling Use Cases
Use Case Summary List
8/13/2019 3309 Requirements Gathering1
36/37
Use Case Summary List
Process or Processes Use Case Category
High Level Process
Detailed Process Special Function/Exception Handling Process Integration (Data)
Role Targeted Release Solution Components
Example of Detailed Process Use Cases
8/13/2019 3309 Requirements Gathering1
37/37
Example of Detailed Process Use Cases
Top Related