failures1 (1)

failures1 (1) - Systems Failures: Theory and Practice...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
Systems Failures: Theory and Practice Lecture 1
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Failure to do what? Failure to produce a working application Failure to keep the project to time and budget Failure to produce a usable application Failure to appreciate knock-on effects on the organisation
Background image of page 2
Failure of what? (1) Software Engineering and Systems Design: software has been incorrectly specified or written. Systems Analysis: understanding of the information requirements and the likely scale of information use. Evaluation of costs and benefits.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Failure of what? (2) Project Management: identifying necessary activities and monitoring them through the project. Breakdown of relations between: users and IT specialists. clients and external vendors.
Background image of page 4
type 1 — objectives not met; type 2 — undesirable side-effects; type 3 — designed failures; type 4 — inappropriate objectives. (Geoff Peters and Joyce Fortune,
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 9

failures1 (1) - Systems Failures: Theory and Practice...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online