Scribd
Upload
16 views22 pages

Chapter 12

Chapter 12 discusses the systems development life cycle (SDLC) and the various reasons for changing systems, including user needs and technological advancements. It highlights the importance of planning, feasibility analysis, and managing behavioral aspects of change during system development. Additionally, it covers different development strategies such as purchasing software, in-house development, and outsourcing, along with methods for improving systems development like business process management and agile methodologies.

Uploaded by

Mashiur Rahman
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
16 views22 pages

Chapter 12

Chapter 12 discusses the systems development life cycle (SDLC) and the various reasons for changing systems, including user needs and technological advancements. It highlights the importance of planning, feasibility analysis, and managing behavioral aspects of change during system development. Additionally, it covers different development strategies such as purchasing software, in-house development, and outsourcing, along with methods for improving systems development like business process management and agile methodologies.

Uploaded by

Mashiur Rahman
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 : 12

Systems Development, Organizations, and Management


Reasons for changing system:
• Changes in user or business needs.
• Technological changes.
• Improved business processes.
• Competitive advantage.
• Productivity gains.
• Systems age and need to be replaced.
SYSTEMS DEVELOPMENT

THE SYSTEMS DEVELOPMENT LIFE CYCLE


THE PLAYERS (Parties involved in system development)

A number of people must cooperate to successfully develop and implement an AIS.


• Management
• Users
• Information systems steering committee
• Project development team
• Systems analysts and programmers
• External players
Planning Systems Development
When development is poorly planned, a company must often return to a prior phase and correct errors and design flaws.
This is costly and results in delays, frustration, and low morale.

Reasons for Returning to a Prior SDLC Phase


Planning Systems Development

Two systems development plans are needed: Planning Techniques:


• Project development plan. • PERT
• Master plan • Gantt Chart

Sample Gantt Chart


Feasibility Analysis

Five important aspects to be considered during a feasibility study:


• Economic feasibility.: capital budgeting (payback period, NPV, IRR)
• Technical feasibility.
• Legal feasibility.
• Scheduling feasibility
• Operational feasibility
Behavioral Aspects of Change

Behavioral Aspects of Change: Positive and negative ways people react to change; managing these behavioral
reactions is crucial to successfully implementing a new system

Why behavioral problems occur Preventing behavioral problems


• Fear. • Obtain management support.
• Top-management support. • Meet user needs.
• Experience with prior changes. • Involve users.
• Communication • Allay fears, and stress new opportunities.
• Disruptive nature of change • Avoid emotionalism.
• Manner in which change is introduced • Provide training.
• Biases and emotions. • Reexamine performance evaluation
• Personal characteristics and background. • Keep communication lines open
• Test the system.
How people resist change
• Keep the system simple, and humanize it
• Aggression,
• Control users’ expectations.
• Projection,
• Avoidance.
AIS Development Strategies

 Purchasing Software
• Canned software- Programs for sale on the open market to a broad range of users with similar needs.
• Turnkey system- Software and hardware sold as a package such that the vendor installs the system and
the user “turns on the key;” often written by vendors who specialize in a particular industry.
• Application service provider (ASP)- Company that delivers software via the Internet; ASP owns and
hosts the software, the user accesses the software remotely via the Internet.

How organizations purchase application software, vendor services, and hardware:


• Selecting a vendor
• Acquiring hardware and software
• Evaluating proposal and selecting a system
 Development by In-House Information Systems Departments
Custom software- Software developed and written in-house to meet the unique needs of a particular
company.
End-User-Developed Software
End-User Computing (EUC) is the hands-on development, use, and control of computer based information
systems by users.
Advantages: Disadvantages:
• User creation, control, and implementation • Logic and development errors
• Systems that meet user needs • Inadequately tested applications
• Timeliness. • Inefficient systems.
• Freeing up of systems resources. • Poorly controlled and documented systems
• Versatility and ease of use. • System incompatibilities
• Duplication of systems and data; wasted
resources.
• Increased costs.

Managing and controlling end-user computing: Help-Desk


 Outsourcing the System

Outsourcing is hiring an outside company to handle all or part of an organization’s data processing activities
Advantages of Outsourcing: Disadvantages of Outsourcing:
• A business solution • Inflexibility
• Asset utilization • Loss of control
• Access to greater expertise and • Reduced competitive advantage
technology • Locked-in system
• Lower costs • Unfulfilled goals
• Less development time • Poor service
• Elimination of peaks-and-valleys usage • Increased risk
• Facilitation of downsizing
Methods for Improving Systems Development
 BUSINESS PROCESS MANAGEMENT

• Business Process Reengineering (BPR) – The thorough analysis and redesign of business processes and
information systems to achieve dramatic performance improvements; often a drastic, one-time event.

• Business Process Management (BPM) – A systematic approach to continuously improving and optimizing
business processes; a more gradual improvement facilitated by technology.

• Business Process Management System (BPMS) – A system that automates and facilitates business process
improvements throughout the SDLC.
Major Components of a BPMS:
• Process Engine – Models and executes applications, including business rules.
• Business Analytics – Identifies and reacts to business issues, trends, and opportunities.
• Collaboration Tools – Eliminates communication barriers.
• Content Manager – Stores and secures electronic documents, images, and other files.
 Prototyping
Prototyping is a systems design approach in which a simplified
working model of a system is Developed.

The Steps for Developing a System From a Prototype


AGILE METHODOLOGIES
Agile is a type of software development methodology that anticipates the need for flexibility and applies a level
of pragmatism to the delivery of the finished product. Agile software development requires a cultural shift in
many companies because it focuses on the clean delivery of individual pieces or parts of the software and not on
the entire application.

COMPUTER-AIDED SOFTWARE ENGINEERING


Computer-aided software (or systems) engineering (CASE) is an integrated package of tools that skilled
designers use to help plan, analyze, design, program, and maintain an information system. CASE software
typically has tools for strategic planning, project and system management, database design, screen and report
layout, and automatic code generation. Many companies use CASE tools.
Advantages:
• Improved productivity
• Improved program quality
• Cost savings
• Improved control procedures
• Simplified documentation
Disadvantages:
• Incompatibility
• Cost
• Unmet cost
Conceptual Systems Design
Physical Systems Design
Systems Implementation and Conversion
Operation and Maintenance

• Post implementation review


A post implementation review is conducted to determine whether the system meets its planned objectives.

• Post implementation review report

You might also like