This is some tinkering on my 5 (topics) x 5 (approaches) x 2 (in or out) model that can be used to plan and manage Business Analysis work. I came up with it while in Nigeria (hence the Nigeria model name) and I dedicate it to the wonderful people that attended my class in Abuja (2014). Use the model as you see fit. No copyright limitation from my side, but I would appreciate if you mention my name and/or company (Why-What-How Consulting and Training) when you refer to it. Thanks, Razvan:-) P.S. Also available on my website learn.how2analyze.com, if you are a registered user.

1. Razvan’sBA Examples
A very small selection

2. 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)

3. (5 x 5) x 1
Identify
Describe
Define
Elaborate
Trace
WHY
Business Reqs/ Objectives
WHO
Actors
&WHAT
Processes/
Use Cases
HOW
Solution Reqs
DATA
RULES
The BA Scope/Progress Matrix
APPROACH
TOPIC

4. (5 x 5) x 1
Identify
Describe
Define
Elaborate
Trace
WHY
Business Reqs/ Objectives
Must: 4
Should: 1
Could: 2
3
1
0
2
1
0
-
Bus Reqs to:
•SHReqs, Bus Rules, Data, Actors, Systems/Applications
WHO
Actors
Primary: 7
Supporting: 5
5
4
3
2
-
Actors to:
•Use cases, Bus rules,Data, Training curricula
&WHAT
Processes/
Use Cases
Must: 17
Should: 3
Could: 13
15
2
3
8
1
0
2
0
0
Use cases to:
•Bus. Rules, Data, GUI, other UseCases, Test Cases, Training units
HOW
Solution Reqs
Must: 63
Should: 15
Could: ?
25
6
0
11
1
0
-
Functional Reqsto:
•System components
Non-Functional Reqs to: ?
DATA
80% done
80% done
40% done
20% ?
Data to: …
RULES
67
43
7
-
Rules to: Use cases, Data…
Example…
APPROACH
TOPIC

5. Example using Actors & Use Cases…
•Similar approach for other Business Design Elements (topics)

6. [WHO:ID] Identifying Actors and other Stakeholders

Sales Rep

Customer Service

7. PROCESSES/USE CASES
Out-of-scope:
[WHO:Describe] Actor[WHAT:ID] Identify Actors’ Goals/Responsibilities
ACTORS

Buyer

Customer Service

Buyer
A Buyer is a person/ organization that buys items from the Online store. Only buyers with an active account can…

8. [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 Order
Primary Actor: Buyer
Pre-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.Buyerreviews/confirms Order details
2.Systemvalidates Order(see Business rules 023, 074)
3.Buyerprovides payment info(credit card):
•Credit card name, number, expiration date…
4.Credit card company authorizes transactions
5.Buyerprovides shipping information…
6.…
ALTERNATE SCENARIOS:
2a: Item out-of stock…
4a: Credit card declines transaction…

9. [HOW:Elaborate] Alternate & Exception Scenarios
UC-007: Place Order
Primary Actor: Buyer
Pre-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.Buyerreviews/confirms Order details
2.Systemvalidates Order(see Business rules 023, 074)
3.Buyerprovides payment info(credit card):
•Credit card name, number, expiration date…
4.Credit card company authorizes transactions
5.Buyerprovides 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 (1stattempt):
1.System informs Buyer that Credit Card declined transaction
2.Buyer provides alternate Credit Card
3.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 (2ndattempt):
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

10. 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