Imformation Technology
Introduction to Information Systems
Engineering
Information Systems
Engineering
Introduction – Why do Systems Fail?
Background to systems development • Central criticism of information systems has been (and still is) that: many systems do not do what their users require and thus fall into disuse require and thus fall into disuse.
• In order for a system to be considered successful it needs to meet quality and productivity targets
Productivity targets
• The system is delivered on time and within budget.
• These targets relate to:
– successful management of the project, from th inception to implementation
This course:
•
Examines the role of information, data and knowledge in the development of information systems
•
Looks at the role of a methodology and critically assess the benefits and limitations of the traditional systems development frameworks
•
Critically evaluates a range of approaches to aid the analyst to carry out requirements analysis
•
Examines future trends in the use of methods in developing information systems
Quality targets
• The system meets the requirements specification (i.e. it serves the purpose for which it was originally intended)
• these targets relate to targets relate to
– an understanding of the business area
– the user requirements
– the organisational constraints
– other environmental factors
Successful/unsuccessful systems • As we have already said, for a system to be deemed successful it must meet its quality and productivity targets
• A system may considered unsuccessful on a number of different levels:
1
Unsuccessful systems
• The system is never delivered to the user
– there are a number of reasons for abandoning a project.
– Often, this is a better course of action than this is better course of action than implementing a system that will never be properly used.
Unsuccessful systems
Unsuccessful systems
• The system fails one or both of its
Engineering
Information Systems
Engineering
Introduction – Why do Systems Fail?
Background to systems development • Central criticism of information systems has been (and still is) that: many systems do not do what their users require and thus fall into disuse require and thus fall into disuse.
• In order for a system to be considered successful it needs to meet quality and productivity targets
Productivity targets
• The system is delivered on time and within budget.
• These targets relate to:
– successful management of the project, from th inception to implementation
This course:
•
Examines the role of information, data and knowledge in the development of information systems
•
Looks at the role of a methodology and critically assess the benefits and limitations of the traditional systems development frameworks
•
Critically evaluates a range of approaches to aid the analyst to carry out requirements analysis
•
Examines future trends in the use of methods in developing information systems
Quality targets
• The system meets the requirements specification (i.e. it serves the purpose for which it was originally intended)
• these targets relate to targets relate to
– an understanding of the business area
– the user requirements
– the organisational constraints
– other environmental factors
Successful/unsuccessful systems • As we have already said, for a system to be deemed successful it must meet its quality and productivity targets
• A system may considered unsuccessful on a number of different levels:
1
Unsuccessful systems
• The system is never delivered to the user
– there are a number of reasons for abandoning a project.
– Often, this is a better course of action than this is better course of action than implementing a system that will never be properly used.
Unsuccessful systems
Unsuccessful systems
• The system fails one or both of its