MDX BIS4225.

Introduction
A system can:
totally fail
BIS4225.7 partially fail (manages to do a
fraction of the tasks)
System Failures
temporarily goes down (which
may be rectified quickly)

1 2

Introduction Common Observations

A system under Failures are usually due to
development may be complexity of situation and
deemed a failure even software.
before it is implemented. Software systems are not very
well developed.
Not much research done on
software failures.
3 4

Common Observations Impact

Most cases are unique. Examples of Impacts:
Software development Financial Depletion of
techniques have not matched losses assets
up with hardware technologies. Job losses Lowering of
Solutions that work in one Loss of morale
situation may not work in shareholder Bad press
another. confidence publicity

5 6

1
 MDX BIS4225.7
Remedial Actions
Recognize the symptoms of
failures.
Identify what is going on in
these situations.
7 8
Remedial Actions
Think about formal
systematic approaches.
Look at existing methods
used.
Predict likely problems that
may arise in future
developments.
9 10
Representation
There are a ranges of ways to
assist in understanding
symptoms.
Intention is to achieve a good
approach to examining a
problem to determine its true
characteristics.
11
Remedial Actions
Take a systematic look at
what causes the failure.
Consider some of the effects
on the business.
Determine what sort of help is
available to avoid or resolve
the situation.
Symptom
A characteristic sign or
indication of the existence
of a state (problem).
Analysis
Analyze symptoms along
with information related to
the nature of the system:
Size
Budget
Available manpower
Business requirements
12
2
 MDX BIS4225.7

Analysis Analysis
Cause and Effect Diagram Cause and Effect Diagram
A schematic technique The Effect is either the
used to discover possible quality characteristic
locations of quality under investigation, the
problems. Also known as problem to be solved, or
the Ishikawa diagram. needs/areas that are to be
improved or controlled.
13 14

Analysis Analysis
Cause and Effect Diagram The main causes to the effect
Method Manpower are written on the end of the
Zyxx
branches.
Xyyxx
Yzzxx Sub-branches from these
main branches indicate more
Yxyxz
Effect
detailed reasons (how, why,
Xzyzz Xyx

Yxzz Zzyxxy
when, etc.)
Material Machinery
15 16

Causes Causes
Causes of failures vary Need to be able to identify
considerably. the true causes of system
Three generic root causes: problems and failures.
Inadequate requirements.
Insufficient resources.
Inappropriate human actions
(mistakes).
17 18

3
 MDX BIS4225.7
Prevention
Ideas from software
development:
Goal-Question-Metric
(GQM): Identify goals, set
quantifiable questions,
deriving metrics (collect
data) to answer questions.
19
Prevention
Other Newer Ideas:
Experience Factory: Reuse
of software experiences to
improve software
processes and products.
21
Prevention
Other Newer Ideas:
Risk Handling: Pragmatic
approach involving
considerations such as
unrealistic schedules and
budgets, shortfalls in
performance.
23
Prevention
Ideas from software
development:
Capability Maturity Model
(CMM): Eliminate
chaotic/crisis management
situations, develop mature
disciplined processes.
20
Prevention
Other Newer Ideas:
Project De-Escalation:
Changes to top
management, reduce
management threats, new
goals, publicizing on
problem.
22
Prevention
Other Newer Ideas:
Organizational Focus:
Examines implications of
managerial infrastructure,
relationship between
entities, match-up with
software practices.
24