0% found this document useful (0 votes)
9 views22 pages

Chapter 5

Chapter Five discusses the management of information systems, focusing on how they can redesign organizations and facilitate change. It outlines various system-building approaches, including traditional methods and newer alternatives like prototyping and outsourcing. The chapter also details the systems development lifecycle (SDLC) with its six phases, emphasizing the importance of aligning information systems with organizational needs and goals.

Uploaded by

Ahmed Updirahman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views22 pages

Chapter 5

Chapter Five discusses the management of information systems, focusing on how they can redesign organizations and facilitate change. It outlines various system-building approaches, including traditional methods and newer alternatives like prototyping and outsourcing. The chapter also details the systems development lifecycle (SDLC) with its six phases, emphasizing the importance of aligning information systems with organizational needs and goals.

Uploaded by

Ahmed Updirahman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 22

Chapter-Five

MANAGEMENT OF
INFORMATION SYSTEM
Topics

• Redesigning the organization with information systems

• Systems development and organization change

• Alternative system-building approaches

• Overview of systems development


Redesigning the organization with information
systems

Systems as Planned Organizational Change


• New information system results in:
– Change in jobs, skills, management, and organization.
– Organization conflict and change in the locus of decision
making.
– Change in the nature of work groups
…Redesigning

• Systems can be technical successes but organizational failures


b/c of failure in the social and political process of building the
system
• Analysts and designers are responsible for
– Ensuring that key member of the organization participation

– Linking Information Systems to the Business Plan


– Establishing organizational information requirements
…Redesigning

Establishing organizational information requirements


• Two principal methodologies:
− Enterprise Analysis
− Critical Success Factors

1. Enterprise Analysis
• Argues that the firm's information requirements can only be understood by
looking at the entire organization units, functions, processes, and data
elements.
…Redesigning

2. Critical Success Factors


• Approach argues that an organization's information

requirements are determined by small number of critical

success factors (CSFs) of managers.


System Development and Organizational Change

• New information systems :


– Enabling organizations to redesign their
• Structure,
• Scope,
• Power relationship,
• Workflows,
• Products, and service.
…System Development and

The Spectrum of Organization Change


– IT can promote various degrees of organizational change, ranging from
incremental to far-reaching.
– Four kinds structural organization changes
…System Development and

• Organizational Change carries risk and rewards


• The most common forms of organizational change are automation
and rationalization.
• The most common form of IT-enabled organization change is
automation.
Alternative system-building approaches

• Methods:

– The traditional systems development lifecycle,

– Prototyping,

– Application software packages,

– End-user development, and

– Outsourcing.
…approaches

The traditional systems development lifecycle


– The oldest method
– Used today for medium or large complex systems projects
– stages:
(1) Project identification and selection,
(2) Project initiation and planning,
(3) Analysis,
(4) Design,
(5) Implementation, and
(6) Maintenance
…approaches

Prototyping
– Is working version of an information system, but only a
preliminary model
– Once operational, the prototype will be further refined until it
conforms precisely to users’ requirements.
– Once the design has been finalized, the prototype can convert
to a polished production system.
– quick and inexpensive
…approaches
…approaches

Application software packages


• The company can save time and money by using the
prewritten, redesigned, protested software programs from the
package.
• If an organization has unique requirements that the package
does not address, many packages include capabilities for
customization.
…approaches

End-user development
• End user development is the development of information system
by end user with little or no formal assistance from technical

specialists.

Outsourcing
– If a firm does not wants use its internal resources to build or
operate information systems it can hire an external organization
that specializes in providing these services to do the work.
Overview of systems development

• SDLC has six phases:


Identification and
Selection

Initiation and
Planning

Systems
Analysis

Systems
Design

Implementation

Systems
SDLC
1.Project Identification and Selection
• Activities include:
– Identified need for IS
– Identified systems development projects
– Classify, Rank and Select projects
• Output:
− Projects by which IS will be developed
SDLC
2. Project Initiation and Planning
• Major activity
– Preliminary investigation of the system problem or opportunity
at hand and the presentation of reasons.
• Specific tasks:
− Assessing feasibility of the IS development project

– Listing the activities involved in the project


– Preparing a (time) schedule of the activities
SDLC
3. Systems Analysis
• Major tasks:
– Requirements determination
– Requirements structuring
– prepare initial design alternatives and choose between them

4. Systems Design
• Convert initial design into logical and then physical design
specifications
SDLC
5. Implementation
• The physical specification is turned into a working system
• This phase specifically involves:
– Coding
– Testing
– Installation
– Data conversion (data entry)
– User training
– Finalizing documentation
SDLC
6. Maintenance/User support
• Maintenance requests may arise as a result of:
– Faults found in the system by users
– Better ways of doing a task using the system or
improvements on the system thought out by users
– Change in the nature of business functions or environment
• End

End of the course


Thank you very much for your
contribution to the course

You might also like