Download presentation
Presentation is loading. Please wait.
1
EXAMPLE way of documenting…
Driver Problem / opportunity analysis Driver: Problems that the business must solve Opportunities the business can exploit Rules that the business must conform to …etc Vision: The ideal state of the business after the drivers have been addressed Objective: The measures of success that will DEFINE if a project has been successful: Increase [measure] to the value of … Decrease [measure] to the value of … Maintain [measure] at the value of … Deliverable: The output of a project that affects the Objectives in the desired way. Function Business Procedure Technology Skill Proof of compliance Benefit: Which (and how much?) Deliverable contributes to which Objective Requirement: Functional Non-functional Scope (Org, App and Tech) Data Requirement Benefit: Which (and how much?) each Requirement contributes to which Benefit Business Rule: Process model Data model Rule definition Business logic Requirement Business Rule: Which rules are utilised within which Requirements EXAMPLE: Driver: Don’t know how to get to Olympia on the tube Taxi arriving in 20 minutes My computer is packed up Vision: I have no problems knowing which tubes to get when I arrive at Euston, and where to change, to get to Olympia Objective: I have the knowledge to get me from Euston to Olympia the time the taxi arrives Deliverable: A map of the tube stations from Euston to Olympia Requirement To know which tube line and direction I need from Euston To know at which tube station to change tube trains and lines To know what direction of travel I need To know when I have arrived at Olympia Business Rule The tube line is highlighted for all tube stations The tube lines I need to take is highlighted The tube stations I need to use are highlighted The direction of travel is indicated from any tube station I need to depart from for the relevant tube line Kensington is the tube stop for Olympia Copyright smart-BA 2008 1
2
EXAMPLE way of documenting…
EXAMPLE way of documenting… Driver Problem / opportunity analysis Addressed as measured by Project Objective SMART objectives Driver: Problems that the business must solve Opportunities the business can exploit Rules that the business must conform to …etc Vision: The ideal state of the business after the drivers have been addressed Objective: The measures of success that will DEFINE if a project has been successful: Increase [measure] to the value of … Decrease [measure] to the value of … Maintain [measure] at the value of … Deliverable: The output of a project that affects the Objectives in the desired way. Function Business Procedure Technology Skill Proof of compliance Benefit: Which (and how much?) Deliverable contributes to which Objective Requirement: Functional Non-functional Scope (Org, App and Tech) Data Requirement Benefit: Which (and how much?) each Requirement contributes to which Benefit Business Rule: Process model Data model Rule definition Business logic Requirement Business Rule: Which rules are utilised within which Requirements EXAMPLE: Driver: Don’t know how to get to Olympia on the tube Taxi arriving in 20 minutes My computer is packed up Vision: I have no problems knowing which tubes to get when I arrive at Euston, and where to change, to get to Olympia Objective: I have the knowledge to get me from Euston to Olympia the time the taxi arrives Deliverable: A map of the tube stations from Euston to Olympia Requirement To know which tube line and direction I need from Euston To know at which tube station to change tube trains and lines To know what direction of travel I need To know when I have arrived at Olympia Business Rule The tube line is highlighted for all tube stations The tube lines I need to take is highlighted The tube stations I need to use are highlighted The direction of travel is indicated from any tube station I need to depart from for the relevant tube line Kensington is the tube stop for Olympia Copyright smart-BA 2008 2
3
EXAMPLE way of documenting…
Driver Problem / opportunity analysis Addressed as measured by Project Objective SMART objectives Delivered by Business… Functional… Non-functional… …high level …mid level Change Requirement Driver: Problems that the business must solve Opportunities the business can exploit Rules that the business must conform to …etc Vision: The ideal state of the business after the drivers have been addressed Objective: The measures of success that will DEFINE if a project has been successful: Increase [measure] to the value of … Decrease [measure] to the value of … Maintain [measure] at the value of … Deliverable: The output of a project that affects the Objectives in the desired way. Function Business Procedure Technology Skill Proof of compliance Benefit: Which (and how much?) Deliverable contributes to which Objective Requirement: Functional Non-functional Scope (Org, App and Tech) Data Requirement Benefit: Which (and how much?) each Requirement contributes to which Benefit Business Rule: Process model Data model Rule definition Business logic Requirement Business Rule: Which rules are utilised within which Requirements EXAMPLE: Driver: Don’t know how to get to Olympia on the tube Taxi arriving in 20 minutes My computer is packed up Vision: I have no problems knowing which tubes to get when I arrive at Euston, and where to change, to get to Olympia Objective: I have the knowledge to get me from Euston to Olympia the time the taxi arrives Deliverable: A map of the tube stations from Euston to Olympia Requirement To know which tube line and direction I need from Euston To know at which tube station to change tube trains and lines To know what direction of travel I need To know when I have arrived at Olympia Business Rule The tube line is highlighted for all tube stations The tube lines I need to take is highlighted The tube stations I need to use are highlighted The direction of travel is indicated from any tube station I need to depart from for the relevant tube line Kensington is the tube stop for Olympia Copyright smart-BA 2008 3
4
EXAMPLE way of documenting…
Driver Problem / opportunity analysis Addressed as measured by Project Objective SMART objectives Delivered by Business… Functional… Non-functional… …high level …mid level Change Requirement Driver: Problems that the business must solve Opportunities the business can exploit Rules that the business must conform to …etc Vision: The ideal state of the business after the drivers have been addressed Objective: The measures of success that will DEFINE if a project has been successful: Increase [measure] to the value of … Decrease [measure] to the value of … Maintain [measure] at the value of … Deliverable: The output of a project that affects the Objectives in the desired way. Function Business Procedure Technology Skill Proof of compliance Benefit: Which (and how much?) Deliverable contributes to which Objective Requirement: Functional Non-functional Scope (Org, App and Tech) Data Requirement Benefit: Which (and how much?) each Requirement contributes to which Benefit Business Rule: Process model Data model Rule definition Business logic Requirement Business Rule: Which rules are utilised within which Requirements EXAMPLE: Driver: Don’t know how to get to Olympia on the tube Taxi arriving in 20 minutes My computer is packed up Vision: I have no problems knowing which tubes to get when I arrive at Euston, and where to change, to get to Olympia Objective: I have the knowledge to get me from Euston to Olympia the time the taxi arrives Deliverable: A map of the tube stations from Euston to Olympia Requirement To know which tube line and direction I need from Euston To know at which tube station to change tube trains and lines To know what direction of travel I need To know when I have arrived at Olympia Business Rule The tube line is highlighted for all tube stations The tube lines I need to take is highlighted The tube stations I need to use are highlighted The direction of travel is indicated from any tube station I need to depart from for the relevant tube line Kensington is the tube stop for Olympia Enforces Process model Process specification Non-functional specifications Data model Attribute specification …low level Business Rule Copyright smart-BA 2008 4
5
Process execution rules
EXAMPLE PROCESS RULES A BA can request one of 4 types of support: Phone or based query about a specific point Informal review of a project deliverable Formal review of full set of project deliverables Facilitated workshop of how to apply analysis to a specific project 1. In the case of phone or query about a specific point the BA poses the question and the training provider will provide guidance for how the technicalities of Business Analysis apply to the problem Informal reviews of project deliverables will be done by and will only discuss the technicalities of Business Analysis in relation to the document Formal reviews will involve the BA sending the full set of Analysis deliverables to the training provider who will critique them from a technical perspective and then deliver the feedback in a one-to-one structured feedback session on the client site Facilitated workshops will be initiated by the BA - the training provider will supply workshop agenda and prerequisites which the BA will use to organise the workshop. The training provider will then facilitate the workshop for the project. Process execution rules Who is interacts with process Where they are Availability of process Volumetrics Performance of process Security & Authorisation levels Non-functional Rules Time to start Training course BA requests support Conduct Training Provide BA support Analysis Phase Of Project concludes Monitor Analysis quality Process dependency rules
6
Data relationship rules
EXAMPLE DATA RULES Attributes Name Start Date Course duration Contact details Content Review feedback Description Course.Start Date Definition: the date/time the course is scheduled to start Data type: Numeric Size: 12 Domain: Datetime Data rules: Format is DD/MM/YYYY HH:MM When created must be in the future Cannot be a Saturday or Sunday or Bank Holiday Data content rules Who is allowed access to the data? How long must this data be kept? How many instances of it must be supported? Non-Functional Rules Course Attends Delegate Support Type receives Supplies Data relationship rules Analysis Deliverable
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.