Razvan’s 5x5x1 (aka. The Nigeria) BA model+example
Click here to load reader
-
Upload
why-what-how-consulting-llc -
Category
Business
-
view
162 -
download
0
description
Transcript of Razvan’s 5x5x1 (aka. The Nigeria) BA model+example
![Page 1: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/1.jpg)
Razvan’s BA ExamplesA very small selection
![Page 2: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/2.jpg)
The (5 x 5) x 1 Model [ a.k.a. The Nigeria model ]Use/combine 2 perspectives: TOPIC & APPROACH
5 TOPICS:1. WHY:
Business Requirements/Objectives
2. WHO+WHAT: Stakeholder/User Requirements
3. HOW: Solution Requirements• Function(al) & Non-Function(al)
• Transition
4. DATA
5. RULES
5 APPROACHES:1. Identify
(name)
2. Describe(high-level/short)
3. Define (main characteristics/details)
4. Elaborate(additional details)
5. Establish Relationships (Traceability)
![Page 3: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/3.jpg)
(5 x 5) x 1 Identify Describe Define Elaborate Trace
WHYBusiness Reqs/ Objectives
WHOActors
& WHATProcesses/ Use Cases
HOWSolution Reqs
DATA
RULES
The BA Scope/Progress Matrix
APPROACH
TOP
IC
![Page 4: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/4.jpg)
(5 x 5) x 1 Identify Describe Define Elaborate Trace
WHYBusiness Reqs/ Objectives
Must: 4Should: 1Could: 2
310
210
-Bus Reqs to: • SH Reqs, Bus Rules, Data, Actors,
Systems/Applications
WHOActors
Primary: 7Supporting: 5
54
32
-Actors to:• Use cases, Bus rules, Data, Training
curricula
& WHATProcesses/ Use Cases
Must: 17Should: 3Could: 13
1523
810
200
Use cases to:• Bus. Rules, Data, GUI, other Use Cases,
Test Cases, Training units
HOWSolution Reqs
Must: 63Should: 15Could: ?
2560
1110
-Functional Reqs to:• System componentsNon-Functional Reqs to: ?
DATA 80% done 80% done 40% done 20% ? Data to: …
RULES 67 43 7 - Rules to: Use cases, Data…
Example…
APPROACH
TOP
IC
![Page 5: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/5.jpg)
Example using Actors & Use Cases…
• Similar approach for other Business Design Elements (topics)
![Page 6: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/6.jpg)
[WHO:ID] Identifying Actors and other Stakeholders
Sales Rep
Customer Service
![Page 7: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/7.jpg)
PROCESSES/USE CASES
Out-of-scope:
[WHO:Describe] Actor[WHAT:ID] Identify Actors’ Goals/Responsibilities
ACTORS
Buyer
Customer Service
BuyerA Buyer is a person/ organization that buys items from the Online store. Only buyers with an active account can…
![Page 8: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/8.jpg)
[HOW:Define] Use Cases Header Info & Main Success Scenarios (Alternates identified)
USE CASE DIAGRAM
Online Store (Rel. 1)
Buyer
Customer Service
Credit Card Company
UC-007: Place OrderPrimary Actor: BuyerPre-Conditions: • Buyer has active account (UC-029)• Buyer is logged in (UC-001)
Post-conditions:• Success: Order placed• Unsuccessful: Payment declined, Order cancelled• Unsuccessful: Item not available, Order on backorder
Trigger: • Buyer selected Check-out
MAIN SUCCESS SCENARIO:1. Buyer reviews/confirms Order details2. System validates Order (see Business rules 023, 074)3. Buyer provides payment info (credit card):
• Credit card name, number, expiration date…4. Credit card company authorizes transactions5. Buyer provides shipping information…6. …ALTERNATE SCENARIOS:2a: Item out-of stock…4a: Credit card declines transaction…
![Page 9: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/9.jpg)
[HOW:Elaborate] Alternate & Exception Scenarios
UC-007: Place OrderPrimary Actor: BuyerPre-Conditions:
• Buyer has active account (UC-029)• Buyer is logged in (UC-001)
Post-conditions:• Success: Order placed• Unsuccessful: Payment declined, Order cancelled• Unsuccessful: Item not available, Order on backorder
Trigger: • Buyer selected Check-out
MAIN SUCCESS SCENARIO:1. Buyer reviews/confirms Order details2. System validates Order (see Business rules 023, 074)3. Buyer provides payment info (credit card):
• Credit card name, number, expiration date…4. Credit card company authorizes transactions5. Buyer provides shipping information…6. …
ALTERNATE SCENARIOS:2a: Item out-of stock…4a: Credit card declines transaction…
UC-007: Place Order…ALTERNATE SCENARIOS:
2a Item out-of-print (can order from Publisher):…
4a Credit card declines transaction (1st attempt):1. System informs Buyer that Credit Card
declined transaction2. Buyer provides alternate Credit Card3. Return to MSS@4
EXCEPTION SCENARIOS:1a Buyer cancel Order
…2b Item out-of-print (can’t order from Publisher):
…4b Credit card declines transaction (2nd attempt):
1. System informs Buyer that both attempts have been declined, order is placed on hold for 1-hour, and that buyer should contact Customer service to complete the Order
2. Use case ends
![Page 10: Razvan’s 5x5x1 (aka. The Nigeria) BA model+example](https://reader038.fdocuments.net/reader038/viewer/2022100506/548841c9b47959e20c8b56c1/html5/thumbnails/10.jpg)
PHYSICAL DATABASE MODEL (build by Technical Engineers)
LOGICAL DATA MODEL
Example for Data (to be finalized)• Identify:
• Identify Business Data Objects (e.g. Order, Item, Account, Buyer, etc.)
• Identify relationships between these Business Data Objects
• Describe:• Brief description (1-2 paragraphs) of most or all Business
Data Objects (especially those that may be use inconsistently or that may generate confusion)
• Define: • Add data Attributes
• Elaborate:• Refine Relationships (e.g. Cardinality,
Generalization/Specialization, Aggregation, etc.)• Refine Attributes types & Data Rules (e.g. defaults,
calculated, mandatory/optional, multiple vs. single values, valid values, etc.)
• Establish Relationships:• With other Business Design Elements (e.g. Use Cases, User
Interfaces, etc.)
CONCEPTUAL DATA MODEL