263
Management of Information Systems

Management of Information Systems

Embed Size (px)

Citation preview

Page 1: Management of Information Systems

Management of

Information Systems

Page 2: Management of Information Systems

Syllabus

Introduction to MIS, IS/IT strategy

Strategic IS/IT planning

MIS applications and SDLC

Alternatives to SDLC

Operations Management

Controls & IS’s

Measuring IT investment and their returns

Page 3: Management of Information Systems

Reference Books:

Management of Information

Technology

Carroll W. Frenzel & John C. Frenzel

Management Information Systems

Laudon & Laudon

Page 4: Management of Information Systems

Assessment %

Presentation 10

Pre-Course Assignment 20

Main Assignment 20

End-of Term Exam 50

Page 5: Management of Information Systems

Introduction to MIS, IS/IT

Strategy

Page 6: Management of Information Systems

References

Management of Information

Technology - chapter 1,2,3

Carroll W. Frenzel

Management Information Systems –

chapter 1,2

Laudon & Laudon

Page 7: Management of Information Systems

Information System (IS) Aggregation of components that work

together to process data and produce information

IS can be defined technically as a set of interrelated components that collect (retrieve),process, store & distribute information to support decision making & control in an organization

[Laudon,1998]

Page 8: Management of Information Systems

Globalization

Transformation of industrial

economies

Transformation of the environment

Why do we need

Information Systems?

Page 9: Management of Information Systems

Globalization

Success of organizations depends on

their ability to operate globally.

24/7 global service requirements

Global Competition

Global delivery systems

Page 10: Management of Information Systems

Transformation of Industrial

Economies

Information has become a basic resource

in today’s society – information society

Some services would not exists or would

be too expensive without information.

Page 11: Management of Information Systems

Transformation of the Enterprise

The traditional hierarchical, centralized

organizations:

Employees are specialists

Operates based on standard rules

Mass produces a standardized product

Can operate without IT

Page 12: Management of Information Systems

The new flattened, decentralized

organization:

Employees are generalists

Operates on access to real time

information

Produces mass customized products or

services

Relies on IT

Page 13: Management of Information Systems

Manual

(Pens paper)

Information Systems

Informal Formal

Computer Based

(CBIS)

(Hardware/software)

Page 14: Management of Information Systems

Types of Information

Systems

Page 15: Management of Information Systems

Groups

Served

Knowledge &

Data Workers

Type of Information System

Senior Managers

Middle

Managers

Operational

Managers

Strategic

Level

Management

Level

Sales &

marketingManufacturing Accounting HR

Knowledge

Level

Operational

Level

Page 16: Management of Information Systems

Mangers at different levels of an

organization make different kinds of

decisions

Kind of information necessary to

support their decisions are also different

Therefore, different types of

information systems have to be

designed to meet the various needs

Page 17: Management of Information Systems

Types of IS

ESS - Strategic level

MIS - Management level

DSS

KWS - Knowledge level

OAS

TPS - Operational level

Page 18: Management of Information Systems

Transaction Processing

System (TPS)

Page 19: Management of Information Systems

Found at the operational level of an

organization.

Supports operational Managers &

operations personnel.

It is a computerized system that records the

daily routine transactions necessary to

conduct business.

Page 20: Management of Information Systems

Main purpose: To answer routine questions

(What happened to Mr. XXX’s payment?) and

to track the flow of transactions through the

organization.

Information must be easily available, current

and accurate.

Usually has high volumes of inputs and

outputs.

Page 21: Management of Information Systems

Examples: Hotel reservation systems,

order entry systems, banking systems,

airline reservation systems etc.

Page 22: Management of Information Systems

Main Features :

TPS spans the boundary between the

organization and the environment.

TPS produce information for the other

types of systems.

Page 23: Management of Information Systems

A failure in the TPS often means

disaster for the organization

Imagine what will happen if:

A reservation system at an airline

fails.

When a bank’s TPS crashes.

Page 24: Management of Information Systems

Knowledge Work Systems

(KWS)

Page 25: Management of Information Systems

Supports skilled knowledge workers in

creating and integrating new knowledge.

Examples:

CAD systems used by product designers,

simulation systems, financial systems etc.

Page 26: Management of Information Systems

Knowledge Workers are people who

create, use and distribute information

such as executives, accountants,

engineers, lawyers etc.

Page 27: Management of Information Systems

Office Automation Systems

(OAS)

Page 28: Management of Information Systems

Supports general office work for handling and

managing documents and facilitating

communication.

Used mainly by data workers (clerical staff) to

produce professional documents and to control

the flow of paper work in an organization.

Page 29: Management of Information Systems

Examples:

Word processors, Spreadsheet

packages, presentation packages,

note taking packages (notepads,

appointment books) etc.

Communication systems for

transmitting messages such as E-mail

and teleconferencing systems etc.

Page 30: Management of Information Systems

Management Information

Systems (MIS)

Page 31: Management of Information Systems

Serves the management level of an

Organization.

MIS extracts, process and summarizes data

from the TPS and provides periodic

(weekly, monthly, quarterly) reports to

managers for monitoring, controlling,

decision making and administrative

activities of the organization.

Page 32: Management of Information Systems

Features of an MIS:

Contains only company internal data

Uses simple routines (summaries and

comparisons )

Relies on existing past & present data

Page 33: Management of Information Systems

Examples:

Sales management systems,

inventory control systems, annual

budgeting systems etc.

Page 34: Management of Information Systems

Decision Support Systems

Page 35: Management of Information Systems

Helps managers make decisions

Have more analytical power than other

systems. These systems use sophisticated

analysis and modelling tools such as what-if

analysis, Goal-seeking /optimization

analysis

Offers users flexibility, adaptability and

quick response.

Page 36: Management of Information Systems

Use internal information from TPS and MIS

but often brings in information from

external sources (eg: Stock prices or prices

of competitors)

Example: Production scheduling systems,

Pricing analysis systems etc

Page 37: Management of Information Systems

Executive Support Systems

Page 38: Management of Information Systems

Helps senior managers address strategic

issues and long term trends, in the

organization and the external environment.

Help answer questions like:

What are the long term industry trends?

What products should we be selling in five

years?

Main purpose: match changes in the external

environment with existing organizational

capabilities

Page 39: Management of Information Systems

These systems are designed to incorporate

data about external events.

Draws summarizing information from MIS &

DSS.

User friendly, but very expensive to

maintain.

Page 40: Management of Information Systems

Concepts of Information

Systems

Page 41: Management of Information Systems

Critical Success Factors

Critical Success Factors are those few areas in

which results, if they are satisfactory, will

ensure successful competitive performance for

the organization.

CFS identifies the areas where things MUST

go right - the necessary conditions for

success

Page 42: Management of Information Systems

Examples:

The executives of a department store

would probably consider factors such as

its sales promotion efforts to be critical

to its survival and success

Automotive Industry- Styling, Energy

Standards

Hospital- Cost control, healthcare

standards

Page 43: Management of Information Systems

The CSF method is applied in the form of

interviews usually conducted in two or three

sessions.

1. Goals of the managers are discussed and

recorded. CSF’s that affects these goals are

brought forward.

2. Information needed about these CSFs and

how and where to obtain these information

are established.

Page 44: Management of Information Systems

Information

Technology’s Strategic

Importance

Page 45: Management of Information Systems

Strategic Information Systems

Page 46: Management of Information Systems

• A SIS is an information system which

supports an organization in fulfilling it’s

business goals.

• Information systems whose unique

function or specific application shapes

the organization’s competitive strategy

and provides competitive advantage

for the company.

Page 47: Management of Information Systems

• Systems that fundamentally change the

organization itself.

• It is not an ESS……

– SIS can be at any level

– SIS achieves competitive advantage

– SIS cannot be outsourced

• Examples: American airlines reservation

system, Stock Brokerage System of Merrill

Lynch.

Page 48: Management of Information Systems

External Environment

Page 49: Management of Information Systems

• Refers to the forces and institutions

outside the organization that can

affect the firm’s performance.

• External environment is made up of:

– General environment

– Task environment

Page 50: Management of Information Systems

General Environment

• Includes everything outside the

organization such as:

– Political environment.

– Economic forces.

– Socio- cultural influences.

– Technological factors.

Page 51: Management of Information Systems

Task Environment

• The layer of external environment that

directly influences the organization’s

operations and performance.

• This includes sectors that have a direct

working relationship with the

organization. Eg: suppliers, customers

etc.

Page 52: Management of Information Systems

Porter’s Model

Page 53: Management of Information Systems

• The model helps to understand the

basic forces affecting an

organization in a competitive

environment.

Page 54: Management of Information Systems

• These forces include:

– Threat of Potential new entrants into its

industry

– Companies offering substitute products

and services

– Firm’s Suppliers

– Firm’s customers (buyers)

– Firm’s competitors

Page 55: Management of Information Systems
Page 56: Management of Information Systems

Threat of new entrants

• If an industry is very profitable, then the

expectation is that new firms may attempt to

enter into the industry

• Threat of new entry is largely determined by

the presence of barriers to entry and exit.

• Barriers of entry are obstacles which prevent

the entry of firms into an industry.

Page 57: Management of Information Systems

• There are several sources of barriers

to entry:

– Economies of scale

• As a firm grows in size, or as the scale of

production increases, certain economies

occur which serve to reduce the average

cost of production.

– Initial capital requirements

– Legislation/govt regulations

– Advertising and branding etc…

Page 58: Management of Information Systems

• Barriers to exit refer to the cost of

leaving an industry. The cost of exit

depends upon how industry-specific the

assets of the firm are.

Page 59: Management of Information Systems

Competition from substitutes

Competition from substitutes depend on:

• Relative price performance of substitutes

• Switching costs

• Brand loyalty of customers for the

product.

Page 60: Management of Information Systems

Bargaining Power of Suppliers

• Suppliers can exert bargaining powers on buyers by raising prices or reducing quality.

• A supplier group is powerful if:

– Industry is dominated by a few companies

– Product is unique or if it has built up

switching costs

– The industry is not an important customer

of the supplier group.

– If the brand of the supplier is powerful.

Page 61: Management of Information Systems

Bargaining powers of the buyers

• A buyer group is powerful if:

– Purchases in large volumes.

– Standard products where the buyers can

find alternatives

– The industry’s product is unimportant to

the quality of the buyer’s product or

service

– Buyers pose a threat to making the

industry’s product.

Page 62: Management of Information Systems

Rivalry between Established Firms

• Numerous equally balanced competitors

create intense rivalry.

– This can be due to lack of differentiation or

switching costs etc.

• Use tactics like:

– Price competition

Sometimes competition can be so fierce between

firms that prices are driven below costs

– Product introduction

– Advertising

Page 63: Management of Information Systems

• The model shows that competitors must take

strategic actions to:

• Diminish customer or supplier power

• Lower the possibility of substitute

products entering the market

• Discourage new entrants

• Gain competitive edge within the

existing industry

Page 64: Management of Information Systems

Competitive Strategies

Page 65: Management of Information Systems

Strategic Thrusts (Wiseman)

• Strategic thrusts are major

competitive moves made by a firm.

These thrusts are:

– Product differentiation

– Cost

– Innovation

– Growth

– Alliance

– Time –added by Frenzel

Page 66: Management of Information Systems

Product Differentiation

• Create unique new products & services

that can easily be distinguished from those

of the competitors

– Examples:

• Volvo better safely features

• Whirlpool dishwashers that run

quietly …

Or….Perceive products as different from

and better than those of competitors

Page 67: Management of Information Systems

Differentiation variables….

• Product –

– Design, style, features, performance,

repairability etc

• Service –

– Ordering ease, delivery method,

training, maintenance & repair etc

• Personnel –

– Competency, courtesy, credibility,

reliability, responsiveness etc

Page 68: Management of Information Systems

Cost

• Reduce costs to the firm

• Increase costs to competing firms

• Make a more upscale product at

lower costs than the makers of

other brands with comparable

features and attribute

Page 69: Management of Information Systems

• Save costs through:

–Economies of scale through

automation, specialization etc.

–Economies of scope through

extension into additional

operations which can share

infrastructure costs.

Page 70: Management of Information Systems

Innovation

• Developing new products and

services

• Two kinds:

– Product innovation

• Creation of new products

• New features in existing products

– Process innovation

• To improve efficiency and effectiveness of

a process.

Page 71: Management of Information Systems

Growth

• Product growth

• Functional growth

– Advantage through expansions,

forward & backward integration

• Geographic growth

Page 72: Management of Information Systems

Alliance

–Advantage is attained by reaching

agreements , forming joint

ventures, or making strategic

acquisitions

• Improved Cash Flow

• Innovative Products

• Credibility etc.

Page 73: Management of Information Systems

Time

• Competitive advantage is secured

by rapid responses to changing

market conditions or by supplying a

more timely flow of products or

services

Page 74: Management of Information Systems

Other Considerations…..

• Organization and Environment

• Financial Implications

• Legal Considerations

Page 75: Management of Information Systems

Developing the Organization's IT

Strategy

Page 76: Management of Information Systems

Some definitions

Page 77: Management of Information Systems

Mission

Overriding purpose in line with the

values or expectations of the

stakeholders.

Johnson & Scholes

Communicates “Who we are, what we

do, and where we are headed”

Page 78: Management of Information Systems

Therefore, the key elements of a

mission statement can be identified as:

– Obligations to the stakeholders

– Scope of the business

– Sources of competitive advantage

– View of the future

Page 79: Management of Information Systems

“We are in the business of developing

competencies in people and

organizations through training and

consultancies”

NIBM

Page 80: Management of Information Systems

Goal

A broad statement of long-term (typically

a time horizon of one year or more)

accomplishments an organization wishes to

attain.

Example:

– To increase the market share

Page 81: Management of Information Systems

Objective

Specific commitment to achieving a measurable result within a specific period of time , usually a year or less.

An objective should be:

– Specific

– Measurable

– Related to time

Page 82: Management of Information Systems

Therefore,

– Test 1: does the statement tell what the

intended result is?

– Test 2: does the statement specify when

the intended result is to be accomplished?

– Test 3: can the intended result be

measured?

Page 83: Management of Information Systems

Examples:

–To achieve an 18% increase in brand

X sales by December 2010.

–To reduce bad-debt loss by Rs

50,000 during the next 6 months.

Page 84: Management of Information Systems

Mission Increase shareholder's wealth.

Goal Obtain a satisfactory return on

investment (ROI).

Objective A ROI of 16% by the end of year

2010.

Example:

Page 85: Management of Information Systems

Strategy

A collection of statements that express

or propose a means through which an

organization can fulfill its primary

purpose or mission.-Frenzel

Page 86: Management of Information Systems

Can be seen as the matching of resources

and activities of an organization to the

environment

A company must either fit its strategy to the

industry environment in which it operates, or

be able to reshape the industry environment

to its advantage through its chosen strategy.

A strategy ….

Page 87: Management of Information Systems

Strategic Management

Process of formulating and implementingstrategies to advance an organization’s mission and objectives and secure competitive advantage.

Process by which an organization establishes its objectives, formulates actions designed to achieve these objectives in the desired timescale, implements the actions and assesses progress and results.

Page 88: Management of Information Systems

Strategy Development

Process

Page 89: Management of Information Systems

Examine the mission statement of the

organization.

Carry out a comprehensive

environmental analysis.

Page 90: Management of Information Systems

Assess the findings in terms of opportunities

the organization can exploit and threats it

faces.

Analyze the organization’s internal

resources (financial capital, technical

expertise, skilled work force etc) and

thereby identify the Organization’s internal

strengths and weaknesses.

Page 91: Management of Information Systems

Develop set of Objectives

Formulate the strategies

Page 92: Management of Information Systems

Assess the performance of the

implemented strategies by examining

and comparing the results with the

original plans.

This will enable an organization to

determine to what level it has achieved

its goals.

Page 93: Management of Information Systems

Maintenance Process

–Review the environment and reassess

the course of action.

Page 94: Management of Information Systems

Strategy Document Outline

Page 95: Management of Information Systems

Examine the nature of business.

Environment surrounding the

business activities.

Goals and objectives the units hope

to achieve.

Strategy ingredients.

Page 96: Management of Information Systems

Strategy Ingredients

Statement of intended course of action

–Steps should lead to realize objectives

–Be consistent with other interests

–Be preferred over other alternatives

Page 97: Management of Information Systems

Assumptions

–Major assumptions the strategy

is based on

–Technical capabilities, functional

support, potential competitive

reactions

Page 98: Management of Information Systems

Risks associated with the strategy

–Nature of risks in the strategy

–Potential impact on the strategy

Available options

–What optional course of action can

offer reasonable insurance against

significant risks

Page 99: Management of Information Systems

Conditions on which the strategy

depends

–What strategies are the key

dependencies?

–Their nature and significance

Statement of required resources

–HW, SW and staff requirements

Page 100: Management of Information Systems

Financial Projections

–Revenue, cost and capital requirements.

Alternatives Rejected

–Documentation of alternatives with

reasons for their rejection.

Page 101: Management of Information Systems

Types of Strategies

Page 102: Management of Information Systems

A business strategy seeks to determine

how an organization should compete in

each of its businesses.

Strategy is about how to compete

successfully in particular market.

Business Strategies

Page 103: Management of Information Systems

Concerns are therefore about:

• How advantages could be achieved over

competitors

• What new opportunities could be

identified

• What products or services should be

developed etc.

These strategies have revenue and profit

goals

Page 104: Management of Information Systems

Functional strategies are directed at

improving the effectiveness of functional

operations within a company such as

manufacturing, marketing, HR, R & D etc

These strategies should support business

strategies.

Functional Strategies

Page 105: Management of Information Systems

A specific strategy for dealing with

unique threats/situations (usually

outside the normal planning cycle) or

Capitalize on current opportunities

Stand-alone Strategies

Page 106: Management of Information Systems

The time horizon depends upon the

business the organization is in.

It is usually an annual process

– The time periods are usually analyzed

on a rolling basis, with the horizon

constantly moving forward in

increments of the organization’s fiscal

year.

The Strategic Time Horizon

Page 107: Management of Information Systems

Strategy Maintenance

Page 108: Management of Information Systems

Business conditions change with effects on

the strategy. Therefore, strategies require

periodic examinations.

Actual developments must be tracked

against assumptions, dependencies and risks.

Periodically or when deviations arise, the

entire strategy should be re-examined and

updated.

Page 109: Management of Information Systems

IT strategy Topics

Page 110: Management of Information Systems

To address Business Aspects

– IT strategies need to be aligned

with the firm’s goals and

objectives.

Page 111: Management of Information Systems

To capitalize on Technical Issues

–Strategy should reveal the

practical utilization of technologies

in support of the organization’s

goals and objectives.

Page 112: Management of Information Systems

To comply or achieve Financial

Matters

–IT strategy must match the firm’s

financial ground rules

–Strategy must acknowledge

resource constraint

Page 113: Management of Information Systems

To address organizational Concerns

–How does IT strategy affect other

areas and vice versa

–The strategy should demonstrate IT

organization’s contribution to the firm

Page 114: Management of Information Systems

Personnel Considerations

–To recruit, train and keep good

people both in the department and

across the entire firm

Page 115: Management of Information Systems

Information Technology

Planning

Page 116: Management of Information Systems

Planning is a process by which strategy is

converted to action.

Good planning is essential to continued

success in a business

Page 117: Management of Information Systems

Model for IT

Planning

Page 118: Management of Information Systems

Application Considerations

The application portfolio consists of the complete

set of application programs the firm uses to

conduct its automated business functions.

The plan should deal with the application portfolio

Selection of projects to be implemented

Which application deserves maintenance, revision, or

expansion? Which should be scraped? What new needs

are there? What resources are available to implement

the projects selected?

Page 119: Management of Information Systems

System Operations

These are the processes for running the

applications of an organization

This includes data collection, application

execution & distribution , Storage of

results etc.

Page 120: Management of Information Systems

IT managers must plan system operations

to satisfy customers. Therefore, careful

planning must be done to identify their

needs.

This is important as the organization

depends on these outputs for a successful

and efficient operation.

Page 121: Management of Information Systems

System operations planning should

include:

Service level planning, problem, change and

recovery management, capacity planning

and network planning.

Page 122: Management of Information Systems

Resource Planning

IT resource items consists of money,

equipment, people and space.

Space plans

Requirements of space and other facilities,

A/C, ventilation, electrical power, telecom

equipment etc.

Page 123: Management of Information Systems

People plans

Identifies requirements for people according

to skill level and considers their development

and deployment over the planning period.

This addresses hiring, training, re-training

etc.

Page 124: Management of Information Systems

Financial plans

Summarizes equipment, space, people and

miscellaneous costs.

Administrative Actions

Plan’s assumptions and ground rules should

be clearly laid out.

Coordinate with units that the plan affects.

Plan review meetings with functional

managers , steering committees to guide

the planning process.

Page 125: Management of Information Systems

Technology Planning

Monitor advances in technology

Assess new technologies for the firm

Evaluate benefits and problems of new

technologies

Areas such as Programming tools,

Operating systems, Vendor application

S/W, Advances in storage devices,

Telecommunication systems etc should be

addressed.

Page 126: Management of Information Systems

Other Approaches to

Planning

Page 127: Management of Information Systems

Nolan's Stages of Growth

Nolan's theory about stages of growth

can be used to determine which stage the

firm is in and then make plans according

to the movement to the next stage.

Page 128: Management of Information Systems

Stages of Growthby Richard Nolan & Cyrus Gibson

1. Initiation

2. Contagion

3. Control

Organizational use of Information Technology

tends to follow a predictable pattern over

time.

4. Integration

5. Data Administration

6. Maturity

Stages:

Page 129: Management of Information Systems

Critical Success Factors

Any plans formulated by the IT

department should cover the overall

critical success factors for the

organization, so that the necessary

conditions for success are met.

Page 130: Management of Information Systems

Business Systems Planning

Developed by IBM.

Main objective: to identify the data that is

essential to run a business. Therefore, it focuses

on data and the processes of an organization.

Defines an Information Architecture for the

organization. The basic building blocks of the

architecture are Data Classes and Business

Processes.

Page 131: Management of Information Systems

Integrated Approach (Sullivan)

BSP

Stage of

Growth

EclecticCSF

Low

Low High

High

Degree of Infusion

Degre

e o

f D

iffu

sion

Page 132: Management of Information Systems

Sullivan found two factors correlated with

planning effectiveness:

Infusion:

Degree to which IT has penetrated the firm (high

impact or low impact on the firms)

Diffusion:

Extent to which IT is disseminated throughout the

firm (concentrated or spread)

For example, CSF method is suitable if IT has

spread throughout the organization but has a low

impact.

Page 133: Management of Information Systems

The Planning Horizon

The time over which various plans are

active (time span of the plan)

Three types of plans:

Strategic plans

Tactical plans

Operational plans

Page 134: Management of Information Systems

The plans cover:

Different time periods

Different amounts of detail

Page 135: Management of Information Systems

Strategic plan

Represents long term implementation.

Typically covers a period of two years from

now and goes further into the future (about 5

years).

The plan should cover actions for achieving the

long-rang goals and objectives, allocate

resources, convert assumptions to realities,

mitigate risks etc.

Page 136: Management of Information Systems

Therefore, an organization’s strategic plan is

also a financial statement of projected

revenues, expenses, costs, investments etc.

Page 137: Management of Information Systems

Tactical Plans (intermediate-range plans)

Covers from now to about two years into the

future.

These plans are usually used to measure

manager performance.

Page 138: Management of Information Systems

Operational Plans

Short-range, from now to 3 months, based on

prior tactical planning

Provides direction on a day-to-day/week-to-

week basis

Plans are detailed, subject to frequent

modifications.

Used by first-line, non managerial employees

Page 139: Management of Information Systems

Planning Time

Planning schedules for an organization

should be closely related to its fiscal

calendar.

The entire process is cyclical and

repetitive.

Page 140: Management of Information Systems

Managing Application

Development

Page 141: Management of Information Systems

Reasons for development difficulties

• Those associated with programming.

• Problems related to the firm or its

management.

– Inadequate development tools

– Improperly skilled developers

– Environmental factors

• Schedule pressures, unrealistic expectations, company

policies etc

– Weak management controls

Page 142: Management of Information Systems

Application Project

Management

Page 143: Management of Information Systems

• Business case development

• Phase review process

• Managing reviews

• Resource allocation and control

• Risk analysis

• Risk reduction actions

• Development managers use these items as a decision-making framework

Steps in application project management

Page 144: Management of Information Systems

List outs:

• Investment resources and investment returns

– Benefits (tangible and non-tangible)

– Expected costs

In preparing the document:

– State objectives of the project

– Carry out a cost benefit analysis. Use standard

financial analysis methods. (eg: NPV, IRR, PB

methods) for alternative courses of action.

– Calculate ROI

Business Case Development

Page 145: Management of Information Systems

Phase Review Process

• Occurs when each phase in the SDLC ends.

• End result is a decision to continue the

project, continue with modifications or

terminate it. Therefore, managers require

significant amount of critical information to

accurately assess the project’s progress and

make judgments

Page 146: Management of Information Systems

The phase review must cover

– Project description

– goals, objectives

– Budget and staffing plans

– Plans Vs. actual accomplishments etc

The review is conducted by:

– IT manager or his representative

– Client

– Reps of all functions influencing or affected by

the project

Page 147: Management of Information Systems

Managing the Review Process

• Document each phase review clearly.

• Documentation should include:

– Project scope, contents, resources,

schedules

– Phase review results and conclusions

• Prepare summery reports and

distribute to all concerned parties.

Page 148: Management of Information Systems

Resource Allocation and Control

• Plans and schedules of allocation of

resources for a project.

• The phase reviews should compare

expected resource consumption to

actual

Page 149: Management of Information Systems

Risk Analysis

• Managers must search for areas of risk.

• Develop quantifiable measures for risk

measurements.

• Track risk measures to recognize trends

over the project’s life.

Page 150: Management of Information Systems

Risk Reduction

• Eliminating all project risks may be

impossible!! ……but…

• Identification of risky areas is important

• Leading indicators alert the managers

when the project is heading for trouble.

Page 151: Management of Information Systems

Development Alternatives

Page 152: Management of Information Systems

Development Choices

Build it your self

Buy it

Let some one build it for you -Outsourcing

Page 153: Management of Information Systems

End user development

In many organizations, end users are

developing systems with little or no

formal assistance from the specialists.

Examples:

Business application programs for

Accounting,marketing, finance

WP, Spreadsheet , DB design (Access)

Engineering design packages etc

Page 154: Management of Information Systems

Benefits

Improved requirements determination

User involvement and satisfaction

Breaking the barrier between the user and

the programmers

Page 155: Management of Information Systems

Problems

Cannot develop large, complex systems.

Lack of proper quality assurance standards

and controls.

Uncontrolled data.

Proliferation of “private” information

systems.

Cannot develop large, complex systems.

Page 156: Management of Information Systems

Purchased applications

When to purchase ?

Where functions are common to many

companies.

Where in-house resources are scarce.

Page 157: Management of Information Systems

Advantages

Early availability

Well-known functions

Known and verifiable quality

Lower total cost

Availability of maintenance

Periodic updates

Education and training

Page 158: Management of Information Systems

Disadvantages:

Strategic systems cannot be purchased.

Integration problems.

Difficult to customize.

Page 159: Management of Information Systems

Outsourcing

Page 160: Management of Information Systems

Advantages

Economy

Service quality.

Predictability- Reduces uncertainty of costs

Freeing up human resources for other

projects.

Freeing up financial capital

Reduce risk of failure

Page 161: Management of Information Systems

Disadvantages

Bureaucratic

Dependency

Changes to specifications - costs MONEY

Diffuses company information

Page 162: Management of Information Systems

When to outsource?

When there are limited opportunities

for the company to distinguish itself

competitively through a particular IS

application.

When the predictability of

uninterrupted IS service is not very

important.

Page 163: Management of Information Systems

When outsourcing does not strip the

company of the technical know-how

required for further IS innovation.

When the firm’s existing IS capabilities

are limited, ineffective, or technically

inferior.

Page 164: Management of Information Systems

Other Alternatives

Partnerships, JVs, alliances etc

Service Bureaus

Eliminates development, maintenance costs

Reduces in-house HW requirements

Page 165: Management of Information Systems

Developing and

Managing Customer

Expectations

Page 166: Management of Information Systems

Service Level Agreement (SLA)

It is a contract between a service provider

and the customer that specifies in

measurable terms:

The services provided

Acceptable and unacceptable service levels

Metrics associated with the services

Liabilities on the part of the service provider

and the customer, and

Actions to be taken in specific circumstances.

Page 167: Management of Information Systems

Establish acceptable service levels for IT

clients. Thereby gives a clear understanding

of what is expected from and delivered by

IT operations

Reduces conflicts, levels expectations, places

IT services on a more business-like basis and

reduces threats from competitive suppliers or

outsourcing

Purpose of a SLA

Page 168: Management of Information Systems

SLA ContentsEffective date of agreement

Agreements duration

Type of service provided

Service measures

Availability, performance, reliability, response times

Resources needed and/or costs charged

Customer duties and responsibilities

Monitoring and reviewing

Handling of disputes

Reporting mechanism

Signatures

Page 169: Management of Information Systems

SLA Service Specification - Example

Type of Service Application

Service

Hours of Use

Data entry Inventory

application

Daily

6.00am –

7.00pm

System

Availability:

Week days

Saturday

Sunday

6.00am to 7.00 pm

Can be scheduled 24hrs in

advance

Emergency service only

Page 170: Management of Information Systems

Problem, Change and

Recovery Management

Page 171: Management of Information Systems

Problem, change and recovery mgt

ensure service level attainment

Purpose is to correct deviations from

the norm and prevent future deviations

Page 172: Management of Information Systems

Problem Management

Page 173: Management of Information Systems

Problem

An incident, event or failure that

negatively impacts the ability to

deliver the services committed in SLA

Page 174: Management of Information Systems

Process of minimizing the impact of a

problem affecting the service levels

Method for detecting, reporting and

correcting problems affecting the

service-level attainment.

Problem Management

Page 175: Management of Information Systems

Goals of problem management

Reduce service defects & incidents

Reduce defect cost

..and thereby achieve committed service

levels

Page 176: Management of Information Systems

Problem Sources

Hardware, Software, Network, Human or

procedural errors, Environmental

conditions

Page 177: Management of Information Systems

Problem Management

Process

Page 178: Management of Information Systems

Problem Reports

The purpose is to record the status of

incidents from detection through solution.

The report should include:

Time and duration of incident, description,

category, severity code, individuals

responsible for the solution, estimated repair

date, action taken to recover, actual repair

date, final resolution action.

Page 179: Management of Information Systems

Problem Logs

Records all problems/incidents and the

actions assigned during some fixed period

( eg: last 12 months).

Page 180: Management of Information Systems

Problem Determination

Problem Status Meetings

The committee clarifies the problem based on

description, category and severity etc.

Assign priorities, draw up action plans,

decide responsibilities and target dates for

resolution

Page 181: Management of Information Systems

Status reporting

Resolution status is reported to the

committee

If satisfactory, the problem report is

closed

If change is required change management

process is invoked

Page 182: Management of Information Systems

Problem Management Reports

Summery reports must be prepared

documenting the effectiveness of the

problem management process.

The summery data can be used to reveal

trends that will enable service providers to

set new service levels.

Page 183: Management of Information Systems

Benefits of using a formal approach

There is a standard way to approach every

problem. This saves time.

The solutions will be permanent.

The number of incidents will reduce.

Page 184: Management of Information Systems

Improved quality of IT services.

Learn from the mistakes. This will minimize

failure and reduce the impact of failure.

Obtain a better “first-time fix” rate of

incidents.

Page 185: Management of Information Systems

Problem Management Success

Process is designed to solve problems and

not to evaluate people.

Managers must foster a free and open

atmosphere.

Participants should take the responsibility of

resolution; not equivalent to accepting

responsibility for causing the incident.

Page 186: Management of Information Systems

Change Management

Page 187: Management of Information Systems

Why do we need change

management?

Changes tend to generate problems

Change is a way of life for IT …

Page 188: Management of Information Systems

Change Management

It is a disciplined approach to analyzing

and implementing system changes.

It is a management technique for

planning, coordinating, handling and

reporting system changes that could

negatively impact service delivery

Page 189: Management of Information Systems

Goal –

To minimize risks associated with system

changes and in turn..

Maintain highest possible service levels

Page 190: Management of Information Systems

Change Sources

Hardware changes

OS changes, application software changes

Environmental changes

Procedural changes

Equipment relocation

Problem management-induced changes

Page 191: Management of Information Systems

Change Management Process

Change Request

Records details of change actions from initiation

through implementation.

The report records:

Description of change, risk assessment, testing

procedure, recovery procedure, implementation

plans etc.

Page 192: Management of Information Systems

Change Analysis

Prioritization and Risk Assessment

Planning for Change

Management Authorization

Page 193: Management of Information Systems

Change Management Team

Consists of IT Personnel, HW and SW

vendor liaisons, facility manager etc.

Page 194: Management of Information Systems

Reporting Change Management

Results

Communicate successful change

implementation to all relevant parties

Periodically assess process effectiveness and

trends using log

Areas requiring change, problem areas,

expectation Vs results, emergency action taken

etc

Page 195: Management of Information Systems

Change Management benefits

Reduce adverse impact of change on the

quality of the SLA.

Better assessment of cost of proposed

change.

Greater ability to absorb a larger volume

of change.

Page 196: Management of Information Systems

Recovery Management

Page 197: Management of Information Systems

Recovery management is the process of

planning to provide services to the

users in the event of a failure or

disaster.

Page 198: Management of Information Systems

Recovery management needs to examine all

possible “what-if? ” scenarios.

Classify them by severity and potential

occurrence and come up with plans for

dealing with the various scenarios.

Page 199: Management of Information Systems

High Recovery Planning

Low Contingency

Management

Problem

Management

Risk of Loss

High Low

Page 200: Management of Information Systems

Plans that deal with potential situations that

have a high probability of occurrence with

risk of loss varying from low to high.

These plans provide backup resources to

help restore services.

Recovery Plans

Page 201: Management of Information Systems

Contingency Plans

Plans that deal with potential situations that

have a high risk but have a low probability

of occurrence.

The plans ensure successful performance of

critical jobs during periods when services

and resources are lost or damaged.

Page 202: Management of Information Systems

Crucial Applications

The applications most critical to the firm’s

operation should be identified to enable

prioritization for recovery planning and

implementation.

Understand the tradeoffs that may be

necessary to enable recovery to occur.

Page 203: Management of Information Systems

Environment

Plans should include all environmental

parameters needed for a successful

operation of every application.

Environmental factors can include:

H/W components, software, communication

resources, new data, knowledgeable

personnel etc

Page 204: Management of Information Systems

Emergency planning prepares for natural

and man-made disasters and catastrophic

events and must include the entire firm.

Steps should be taken to limit the damage,

solve problems and resume normal business

activities.

Emergency Planning

Page 205: Management of Information Systems

In emergency planning, early detection &

containment is important to limit the

damage.

Therefore, plans should include procedures

for evacuations, shelter, containment, and

suppression.

Page 206: Management of Information Systems

Plans must be clearly and concisely

documented, frequently tested, made

known and trained, the potential

personnel.

Page 207: Management of Information Systems

Strategies

Several strategies may be available

for coping with emergencies and

disasters:

Manual procedures

Back-up systems

Data services

Page 208: Management of Information Systems

Manual procedures

Least efficient and least desirable.

Suitable for small outages or simple systems

Back-up systems

Back up systems may be located in-house or at

cooperating firms

Service bureau firms can also be used to

handle processing in emergencies.

Page 209: Management of Information Systems

When planning….

Personnel strategies

In-house staff/external staff

Provisions for notifying key people

Equipment and space planning

Written emergency processes

Emergency personnel roster and

responsibilities

Recovery plan testing

Page 210: Management of Information Systems

Measuring IT Investments and

Their Returns

Page 211: Management of Information Systems

Many firms spend around 2-5% of

revenue on IT every year.

Most organizations treat IT expenses as

overheads.

Page 212: Management of Information Systems

Accounting for IT resources is complex

IT resources take different forms (H/W,

S/W, maintenance, labor, N/W

operations etc)

Many hidden costs (eg: administrative

OH)

Resources are scattered throughout the

organization.

Page 213: Management of Information Systems

Due to these reasons, IT investments are

restrained due to the incapability of

quantifying the returns.

Therefore, a sound IT cost accounting system

is critical.

Page 214: Management of Information Systems

Measure progress towards objectives

Provide basis for financial control

Communicate important information to

managers

Measure individual and unit performances

Objectives of Resource Accountability

Page 215: Management of Information Systems

Recovering Costs from

Client

Page 216: Management of Information Systems

Helps clarify costs and benefits of IT

services

Strengthen communication between IT

service provider and client.

Reduce unnecessary expenses and thereby

improve the overall effectiveness.

Benefits of IT Cost Recovery

Page 217: Management of Information Systems

Encourages effective resource use.

Enables IT benchmarking.

Page 218: Management of Information Systems

Disadvantages

Administrative overheads

Some organizations may not be

intellectually prepared to operate an

effective charge-back system.

Page 219: Management of Information Systems

Charge-back

It is an alternative IT accounting method which

distributes all costs of IT to users as accurately

as possible, based on actual costs and usage

levels.

Although accurate allocation sounds desirable in

principle, it can create problems in practice.The

most accurate measures of use may reflect

technological factors that are totally

incomprehensible to the user.

Page 220: Management of Information Systems

Goals of Charge-back Systems

Ease in administration cost effective

Easily understood by customers

Simple parameters make the charging

process easy to administer

Equitable distribution of costs

Page 221: Management of Information Systems

Promote effective use of IT resources

Provide incentives towards newer

technologies.

Page 222: Management of Information Systems

Methods for handling IT cost

recovery

Page 223: Management of Information Systems

Profit Center

An organizational unit or department

designated as a separate entity for the

purpose of revenue generation and

cost collection with decision-making

capabilities.

Page 224: Management of Information Systems

It is like a business within a business.

Therefore, has its own revenue/profit

targets and expenses.

IT recovers its’ costs and expenses by

charging the clients-> Can develop

profits or losses on its operations

Page 225: Management of Information Systems

Advantages

Platform for education- Promote business

management

Users and IT managers gain exposure to

financial consequences of otherwise

hidden issues.

Page 226: Management of Information Systems

Provide benchmarks and comparisons

Helps measure IT effectiveness

Improves financial management

Real costs helps in SLA negotiations, to

make develop/buy decisions of

application portfolio

Page 227: Management of Information Systems

Disadvantages

Administrative overheads

Not necessarily improve overall

performance

Internal competition, internal friction

Profit itself can be a problem

Page 228: Management of Information Systems

Cost center

These are divisions that add to the cost

of the organization, but only adds

indirectly to the profit of the

organization.

For example: R & D, marketing,

customer service.

Page 229: Management of Information Systems

Promotes intensely interactive planning and

budgeting by IT providers and client.

Due to budget mismatches, the planning

process will be iterative.

In the ideal situation:

IT budget = Client’s budget for IT services.

But in actual practice variances will exists.

Page 230: Management of Information Systems

Variances can be handled by:

Carrying the variance at a higher level

Distributing profit/loss to clients

Adjusting rates

Page 231: Management of Information Systems

Relationship to Client Behavior

To promote IT use or new technology adoption,

firm can increase IT funding but bare the cost at

corporate level

As the firm mature in IT use, cost-center approach

can be used to improve the effective use of IT

Mature sophisticated firms with attractive IT assets

can adopt profit-centers approach and sell the

services outside

Page 232: Management of Information Systems

Controls and Information

Systems

Page 233: Management of Information Systems

Why are computerized systems more

vulnerable than manual systems?

Complex IS cannot be replicated

No visible changes

Procedures are invisible -> not easily

understood or audited

Easy to abuse

Page 234: Management of Information Systems

Effect of disaster can be more

extensive than in a manual system

Accessible by many individuals

Easy access -> difficult to control

Online systems are even more difficult

to control

Page 235: Management of Information Systems

Threats to Information Systems

Hardware, software failures.

Personal actions, user errors.

Terminal access penetration, theft of

data, services and equipment.

Electric problems, Fire and other disaster

situations.

Telecommunication problems

Page 236: Management of Information Systems

New threats

Risk of the Web

Confidential information (credit card

numbers) could be intercepted

Hacking

Computer Viruses and Worms

Page 237: Management of Information Systems

Creating a Control Environment

Controls: all methods, policies and

organization procedures that ensure

the safety of the organization’s assets,

accuracy and reliability of its records

and operational adherence to

management standards.

Page 238: Management of Information Systems

Systems are controlled by:

General controls

Application controls

Page 239: Management of Information Systems

General Controls

Those that control:

The design, security and use of computer

programs and

Security of data files throughout the

organization.

Page 240: Management of Information Systems

Consists of a combination of system

S/W and manual procedures.

Ensures the effective operation of all

programmed procedures throughout the

organization

Page 241: Management of Information Systems

General controls are classified as:

Implementation controls

Software controls

Hardware controls

Computer operations controls

Data security controls

Administrative controls

Page 242: Management of Information Systems

Implementation controls

Examine the system development

process at various points to ensure

that the process is well managed and

controlled.

Use of formal review points to approve

or disapprove system implementation

Establish system feasibility

Documentation of the system

Page 243: Management of Information Systems

Software controls

Ensures the security and reliability of

software.

Monitors the use of software and

prevents unauthorized access to S/W

Page 244: Management of Information Systems

Hardware Controls

Ensures the physical security and correct

performance of H/W.

Equipment can be physically secured by:

Restricting access

Protecting from adverse environmental factors

Provision of emergency backups

Use of mechanisms to check H/W malfunction etc.

Page 245: Management of Information Systems

Computer Operations Controls

Ensures that the programmed procedures

are consistently and correctly applied.

Controls can be applied to:

Computer operations, backup and recovery

procedures, storage, processing of data etc.

Instructions should be fully documented,

reviewed and approved by a responsible

official.

Page 246: Management of Information Systems

Data File Security Controls

Ensures data files are not subject to

unauthorized access, change or

destruction.

Data can be protected by:

Restrict access to computer terminals

Use of passwords

Restrictions to files etc.

Page 247: Management of Information Systems

Administrative controls

Formalized standards, rules, procedures

and disciplines to ensure that the controls

are executed and enforced.

Administrative controls include:

Segregation of functions

Written policies/procedures

Supervision

Page 248: Management of Information Systems

Application Controls

Specific controls unique to each computerized

application

Objectives:

Completeness

All transactions must be entered/recorded.

Accuracy

Data must be accurately captured /recorded

Validity

Maintenance

Page 249: Management of Information Systems

Application controls are classified as:

Input controls

Processing controls

Output controls

Page 250: Management of Information Systems

Input Controls

To check data for accuracy and

completeness when data is entered.

Input controls can be for:

Input authorization, data conversions,

data editing etc.

Page 251: Management of Information Systems

Processing Controls

Routines for establishing that data

are complete and accurate during

updating.

Eg: Run control totals, edit checks

Page 252: Management of Information Systems

Output Controls

Ensures that the results of computer

processing are accurate, complete and

properly distributed.

Eg: Balance O/P with processed and

I/P, audits of output reports,

specifications of output recipients.

Page 253: Management of Information Systems

/ University College Dublin An Cotaiste Ollscoile, Baile Atha Cliath

WINTER EXAMINATION - 2006

BACHELOR OF SCIENCE (SRI LANKA) SSc 10

Management Of Information Systems

MIS 2721

Professor Lucas Introna

Professor Andrew Deegan

Ms. Gangani Wickramasinghe *

Time Allowed: 3 hours

Instructions for Candidates

Answer any FIVE questions

All questions carry equal marks

Page 254: Management of Information Systems

1. Explain the characteristics that distinguish a Strategic Information System (SIS)

from other kinds of systems? Discuss with examples, the different strategic thrusts

an organization could pursue. How can critical success factors of an organization

be used to determine Information Systems opportunities?

2 . What is Strategic Management? Discuss the main elements of a strategy document

with suitable examples: Explain the main types of strategies developed by an

organization. Why is strategy maintenance important?

3. Discuss the elements of an IT organization's planning model with suitable

examples. How can the Critical Success Factors (CSF) approach be used for IT

planning? For what type of company is thi s method of planning useful? Explain

the relationship between strategic and tactical plans. How are operational plans

related to tactical plans?

4. Today, Outsourcing has become a popular development choice for organizations.

Analyze the pros and cons of outsourcing contracts by an organization . What are

the possible risks an organization may face by using purchased applications?

What are its advantages?

5. What is Change Management? Explain, as an IT Manager how you would carry

out the change management process in your organization. What are the benefits

of adopting such a formal approach? How is a Service Level Agreement (SLA)

related to change management?

6. " Computer systems more vulnerable to destruction, fraud, error and abuse as

compared to manual systems". Comment. As an IT Manager, explain how

General and Application controls can help you to protect IT assets from theft,

damage and misuse?

7. What are the objectives of resource accountability? What are the disadvantages of

an IT cost recovery process? What alternatives can IT Managers use to charge for

application development? What are the characteristics of each method?

000

Page 255: Management of Information Systems

f University College Dublin An Col;iiste Ollscoile. Baile Atha Cliath

WINTER EXAMINATIONS - 2007

Bachelor of Science (Sri Lanka) BSc 11

Management of Information Systems

MIS2006L

Dr. Lucas Introna

Professor Andrew Deegan

Ms. G. Wickramasinghe*

Time Allowed: THREE (3) hours

Instructions for Candidates:

Answer any FIVE (5) questions

© UCD 2007/08/Modular Page 1 of 3

Page 256: Management of Information Systems

1. Differentiate between the characteristics of a Strategic Information System

(SIS) and an Information System at the strategic level. Discuss Porter's

model of forces governing competition, taking any industry of your choice as

an example. How can critical success factors of an organization be used to

determine Information Systems opportunities?

2. Explain the purpose of developing functional strategies. How are functional

strategies related to a company's business strategy? What are the main

ingredients a strategy statement must cover? Explain with suitable examples.

What role does an environmental assessment play in formulating strategies?

3. What is an Operational Plan? How is an Operational plan related to a

Tactical plan? ABC Ltd has not updated its IT plans for the past few years.

The IT manager has asked your help in initiating an IT planning process.

What advice would you offer to develop a good IT plan? Discuss with suitable

examples. How can Stages of Growth approach be used in IT planning? For

what type of company is this method of planning useful?

4. Discuss the main steps in an Application Project Management process.

Discuss in detail the following software development methodologies and

tools. Analyze the advantages and drawbacks of each method.

a. Object-Oriented Software Development.

b. Rapid Application Development (RAD).

c. CASE tools.

5. What are the other software development alternatives an organization can

pursue other than developing in-house? Discuss the advantages and

drawbacks of two such alternatives. What types of systems are most suitable

for outsourcing? Explain with examples

© UCD 2007/0S/Modular Page 2 of 3

Page 257: Management of Information Systems

6. What is the purpose of a Service Level Agreement (SLA)? Discuss the

relationship between the disciplines of Problem, Change and Recovery

Management and a Service Level Agreement. Explain the main steps in an

effective Problem Management process. What are the benefits of having

such a systematic approach to handle problems?

7. What are General Controls and Application Controls? As an IT Manager,

explain how General Controls will help you to protect your organization 's IT

assets. "The accuracy of a cost-recovery system is not very important to an

IT Manager". Comment on this statement. Compare and contrast Profit-center

and Cost-center methods for recovering IT costs.

000

© UCD 2007/08/Modular Page 3 of 3

Page 258: Management of Information Systems

University College Dublin An CoUiiste otlscoile. Bilile Atha Cliath

WINTER EXAMINATIONS 2008

BACHELOR OF SCIENCE (Batch 12) SRI LANKA

Management of Information Systems

Professor Lucas Introna

Professor Andrew Deegan

Mrs. G. Wickckramasignhe •

Time Allowed: 3 hours

Instructions for Candidates:

Answer FIVE (5) questions

All questions carry equal marks

Page 259: Management of Information Systems

1. "Information and Information Systems have become increasingly important with the

transformation of Industrial Economies". Comment on this statement. What are the main

characteristics of a Strategic Information System? Discuss with examples how "Innovation"

can be used as a competitive move by an organization. Explain the term "Critical Success

Factor". How can organizatious use critical success factors to determine InfOlmation Systems

needs?

2. Explain the terms "Strategy" and "Strategic Managemenf'. Explain the purpose of developing

stand-alone strategies. Why is it important to analyze the environment in order to formulate

strategies? Discuss according to Porter's Model how "new entrants" can affect an organization in

a competitive environment. Consider any industry of your choice as an example.

3. What is an Operational Plan? How is it different from a Strategic Plan? Discuss the main

considerations that smTOund system operations planning? What role does "technology" play in

planning for the IT division? Explain how critical success factors of an organization are used in

IT planning. For what type of organization is this method more suitable?

4. Explain with suitable examples the various software development difficulties related to an

organization or its management. Discuss the essential areas that need to be addressed in

developing a Business Case in software project management. Explain the main objectives of a

Phase Review in Software development. What are the areas a Project Manager must consider as

sources of risk in a project?

5. Discuss in detail the fullowing software development methodologies. Analyze the advantages and

drawbacks of each method.

a. Object..()riented Software Development (OOSD).

b. Test Driven Development (TDD).

What are the other development alternatives available for an organization, other than developing

in-house? Discuss the advantages of one such alternative. What type of system is most suitable to

purchase? Explain with examples.

@ UCD 2008J09IModuiar Page 2 013

Page 260: Management of Information Systems

6. ''A Service Level Agreement reduces coriflicts between the client and the service provider and

places IT services on a more business-like basis ". Comment on this statement. Explain the

contents of a Service Level Agreement. What is Recovery Management? How is Contingency

Planning related to Recovery Management? Discuss the main considerations that snrround

Contingency Planning.

7. "A well designed cost recovery system improves IT's effectiveness". Comment on this statement.

What are the objectives of resource accountability? Explain the goals of an IT chargeback

system. Discuss the characteristics of a profit center method and cost center method of IT cost

recovery.

000

@UCD 2008AJ9lModular Page 3 of 3

Page 261: Management of Information Systems
Page 262: Management of Information Systems
Page 263: Management of Information Systems