Beruflich Dokumente
Kultur Dokumente
22 October 2014
Risks associated with IT in an organization
One way to minimize the risk associated IT is to outsource it.
Outsourcing leads to loss of control.
Business Analyst falls between business and development. It is a
communication role. They retain the corporate knowledge of the
organization.
Internal Business Analyst provides continuity
See page 4, Business Analysis reader. Lifecycle for business
change.
Alignment = making changes to the structure of the organization to
meet the challenges of the changing environment.
Business Case plan for change
The cycle then follows around.
The process continues around to meet the changes in the business
environment.
A company has to be constantly changing in a structured way,
rather than in a slapdash way.
Most business analysts work within the project process although
some work in other areas.
What do Business Analysts do? (See page 17, ring binder, page
10 book)
Involved in helping to define the business case
Define the functional and non functional requirements
Excludes :
Project management
Planning techniques
IT service or infrastructure management
They are trusted advisors
Business case can advise things that may not seem to be obviously
in the interests of the business
Day 2, 23 October
Modelling Business Systems
Terms of reference are the terms of reference to write a business
case.
TOR should be provided but often arent. May have to create terms
of reference.
OSCAR
Objectives
Scope
Constraints
Authority
Resources
Visualise the scope. Create a context diagram. Includes things out
of scope because they may have to interface with them.
Constraints are not solutions. Following the law is a constraint, but it
doesnt necessarily suggest a solution.
Investigate situation
Rich picture or mind map
Gap analysis = where you started from and where you want to get
to
Options for change
Consider Perspectives
Power Interest grid PIG for stakeholder analysis
Links to STOP triangle
S set strategy
T middle managers
OP operational staff
Business Process
Input
Output
-------------------
Added value
Outcome
10
World view
Transformation
Customers
Actors
Owner
Environment
Does not show who carries out the activities or where they are
carried out
11
12
13
Loan
item
Register
borrower
Accept
returned item
Issue
reminder
External measures
Process and task measures
Performance issues
Six Sigma
Six sigma (standard deviations) to the right of the mean =
99.99966% defect free
Options Analysis
Option Evaluation
For a daily event once every 806
Business Case
years
Presentation
5 Step DMAIC approach
Define the problem
Measure the data
Analyse the results
Improve the process
Control
Evaluate Options
Inputs?
Outputs?
Techniques
15
High
Medium
Low
Low
medium
Probability
High
Payback calculation
Payback period = how long it takes to recoup your initial investment
However, two ideas might have the same payback period but one
ultimately makes more money than another.
Discounted cash flow
Takes into account the future value of money.
Using 10% interest rate per year
2014
2015
100
110
2016
121
2017
133
16
Item
Hardware
purchase
Hardware
maintenance
Software
purchase
Software
support
Staff savings
Cash flow for
year
Cumulative
cash flow
Year 1
Year 2
Year 3
Year 5
Year 6
31000.0
0
32000.0
0
33000.0
0
34000.0
0
31000.0
0
150000.
00
32000.0
0
150000.
00
33000.0
0
150000.
00
34000.0
0
150000.
00
88000.0
0
172000.
00
86000.0
0
86000.0
0
84000.0
0
82000.0
0
2000.00
80000.0
0
200000.0
0
30000.00
150000.0
0
30000.00
150000.0
0
260000.0
0
260000.0
0
17
18
Requirements
elicitation
Requirements
analysis
Requirements
validation
Requirements documentation
Requirements management
Page 137 ring binder
Business Case already contains the high level requirements
These then need to be analysed further in order to find out the
atomic requirements
Requirements come in a number of flavours
Business requirements
Solution requirements
Requirement
Requirement
s
Business
General
General
Solution
Technical
Technical
Functional
Functional
NonFunctional
Functional
19
Data maintenance
Changes to data, including data
deletion
Retrieval requirements
Reporting, responding to
enquiries
Non-functional requirements
P141 ring binder
Performance
Speed of processing
transactions
Backup & recovery
Protection against
loss of data
Availability
Timeframe
Security
Security levels for
protection of data
Archiving and
retention
Duration, methods,
eventual deletion
Usability
Ease of learning
Ease of use
Requirements Document
Types of Requirement
Business
o General
o Technical
Solution
20
o Functional
o Non-functional
For every objective there should be a business requirement
For most business requirements there may be a solution but some
may not be provided through IT, some are performed manually
A sample requirement is on p145 ring binder
Hierarchy of requirements
Prioritising Requirements
MOSCOW
M must have
S should
have
C could have
W want to
have
Documenting a requirement
Requirements
elicitation
Requirements
analysis
Requirements
validation
Requirements documentation
Requirements management
Requirements
Identification
Requirements origin and
ownership
Change control
Requirements crossreferencing
Software support
(CASE/CARE)
Configuration
management
21
Day 3, 24 October
Strategic document (Business Case) Defining business
requirements System requirements
Breadth before depth
SWOT analysis provides the information used to create the strategic
document
2 Techniques for internal evaluation
Boston Box
Wild cat
Star
Dog
Cash cow
Resource audit
Tangible resources
o Buildings
o Money
o Staff
Intangible resources
Brand
IP
2 Techniques for external evaluation
PESTLE
Political
Economic
Socio cultural
Technological
Legal
Environmental
Porters five forces left to right is supply chain. Top to bottom are
New entrants and substitute products and services
All this feeds into the MOST
Mission
Objective
Strategy
Tactic
Feeds into the balanced business scorecard (BBS)
Mnemonic CLIF
Customer
22
Rich picture
(or mind map)
+
Consensus
BAM
Stage
Investigate
Consider
perspectives
using
CATWOE
WTCAOE
The T
(transformation)
is important
here
Analyse needs
As Is process
map
To Be process
map p131
Like a BAM but
defining who,
Outptut
Rich picture (or mind
map)
Business Activity
Models
(Built backwards)
1. Plan
2. Enable
3. Do
(transformation)
4. Monitor
5. Control
Consensus BAM
High Level
Requirements
23
High level
requirements
TOR
OSCAR
Stakeholder
analysis
Business Case
Options that make
sense from a business
and technical
perspective
Then do the financial
feasibility
Risk analysis and
impact analysis.
PRESENT TO BOARD
APPROVAL OF AN OPTION
Define
Atomic requirements
requirements
Take high level
requirements
and turn them
into atomic
requirements
(Object
Orientated
approach)
Requirements
engineering
p136
Modelling requirements
CRUD
Capture
Read
Use
Delete
Use cases are named verb noun, so you could use the ones above,
Create Data, Delete file etc.
Solution requirements
24
Record
rental
Record
Return
Bar staff
Prepare drinks
25
Customer
Number
First Name
Last Name
Age
Gender
Date of Birth
getAge()
setAge()
getDateofBirth()
Customer Class
:Customer Object
Customer
Requests
1
1..
Quote
*Multiplicity min..max
Entity relationship diagrams
Custom
er
Quot
e
Reques
ts
26
Lorry
AxleWeight
Car
Roof
Bus
Floors
27
28