Chapter-5 103338

Download as pdf or txt
Download as pdf or txt
You are on page 1of 11

School of Informatics

Department of Information Technology


Course: Information System Management
Course Code: (MSIT 7103)
Degree Program: MSc IT Year 2 Sem II

Compiled by: Siraj Sebhatu (PhD)



 E-mail – [email protected]

10:25:23 PM 1
Chapter Five Information Systems Evaluation

• Information Systems Evaluation (ISE) is defined as evaluation of


performances in hardware, software, networks, data and people.
• The main purpose of ISE is upgrading and improving quality of IS.
• ISE assesses how successfully IS fulfills its objectives.
• The evaluation process gathers information about the functionality of the
evaluated IS or its components.
Strategies for IS evaluation
• Goal-based evaluation
• Goal-free evaluation
• Criteria-based evaluation
Information Systems Evaluation
Strategies for IS evaluation
• Goal-based evaluation
• IS evaluation is driven by explicit goals from organizational context
• These goals measure the IT-system
• Measures if predefined goals are achieved or not
• Goal-based evaluation means that explicit goals from the
organizational context drive the evaluation. These goals are used to
measure the IT system.
• According to Patton (1990) goal based evaluation is described as
measuring the extent to which a program or intervention has
attained clear and specific objectives.
Goal-free evaluation
• Goal-free evaluation
• No explicit goals are used for IS evaluation
• Inductive and situation ally driven strategy
• The aim of this strategy is:
• To avoid narrowly studying program objectives thereby
missing unexpected outcomes
• Eliminate biases introduced in evaluation process by “knowing
the goals”
Cont..
• The goal-free evaluation means that no such explicit goals are used.
Goal-free evaluation is an inductive and situationally driven strategy.
• The major objective of this interpretive evaluation is to gain thorough
understanding of the nature of what is to be evaluated and to create
motivation and commitment (Hirschheim and Smithson, 1988).
Cont..
• The aim of goal-free evaluation is to avoid the risk of narrowly
studying stated program objectives and thereby missing important
unanticipated outcomes, eliminate the negative connotations attached
to discovery of unanticipated effect:
• "The whole language of side-effected or secondary effect or even
unanticipated effect tended to be a put-down of what might well be a
crucial achievement, especially in terms of new priorities."
Criteria-based evaluation
• Criteria-based evaluation: Criteria-based evaluation means that
some explicit general criteria are used as an evaluation yardstick.
There are numerous criteria-based approaches around such as
checklists, heuristics, principles or quality ideals.
• These criteria mainly stem from some specific theories as well as sets
of guidelines, standards or even legal requirements.
• In this approach, the IT-systems interface and/or the interaction
between users and IT-systems acts as a basis for the evaluation
together with a set of predefined criteria.
Information Systems Evaluation
Strategies for IS evaluation
• Criteria-based evaluation
• Explicit general criteria are used as evaluation measurement
• These criteria are adapted from some perspectives or theories
• Unlike goal-based, the criteria are general, not restricted to an organization’s
particular context
• The following are crucial factors that affect success of Information Systems:
1. Functionality/performance of IS
2. Data quality
3. Usefulness of IS
4. Usage simplicity of IS
5. Self-efficiency of IS user
6. Influence of IS on users
7. IS user’s satisfaction
THE BASIC TYPES OF IS EVALUATION
Information Systems Evaluation
• IS user satisfaction is used to assess performance of IS functionality.
• it depends on the interaction between user and IS
• User satisfaction is measured with the following instruments:
 Relation b/n user and IT professionals
 Provision of current and prompt information
 User’s level of training to use IS
 Quality of output information and documentation
 User’s level of dependence on IS
Thank You

You might also like