Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-1

MIS
Information System Design &
Development

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-2

What is System Development Life Cycle

Systems development life

cycle (SDLC) a highly
structured approach for
development of new customized
software applications

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-3

Stages Of System Development

Preliminary Investigation
Assesses feasibility and practicality of system
System Analysis
Study old system and identify new
requirements
Defines system from user's view
System Design
Design new/alternative system
Defines system from technical view

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-4

Stages Of System Development (Conti)

System Development
New hardware and software is acquired,
developed, and tested
System Implementation
System installation and training
System Operation & Maintenance
Daily operation
Periodic evaluation and updating

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-5

SDLC Phases

Preliminary
Investigation
System
Analysis

System Operation
& Maintenance

System
Implementation
n

System
Design

System
Development
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-6

Phase 1:
Preliminary Investigation
Determine if a new system is needed
Three primary tasks:
Define the problem
By observation and interview, determine
what information is needed by whom,
when, where and why
Suggest alternative solutions
Prepare a short report
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-7

Phase 2:
System Analysis
In depth study of the existing system to
determine what the new system should do.
Expand on data gathered in Phase 1

In addition to observation and interviews,

examine:
Formal lines of authority (org chart)
Standard operating procedures (SOPS)
How information flows
Reasons for any inefficiencies
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-8

Phase 2: System Analysis

Tools Used
Checklists - list of questions
Top-down analysis - start with top level
components, break down into smaller
parts through each successive level
Grid charts - to show relationship between
inputs and outputs
System flowcharts - charts flow of input
data, processing, and output which show
system elements and interactions
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4-9

Phase 2: System Analysis

Documentation Produced
Complete description of current system and its
problems
Requirements for new system including:
Subject
Scope
Objectives
Benefits

Possible development schedule

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 10

Phase 3:
System Design
Uses specifications from the systems analysis
to design alternative systems
Evaluate alternatives based upon:
Economic feasibility - Do benefits justify costs?
Technical feasibility - Is reliable technology and
training available?
Operational feasibility - Will the managers and
users support it?
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 11

Phase 3: System Design

Tools Used
Computer-Aided Software Engineering (CASE)
tools are software-based products designed to help
automate the production of information systems.
Examples:

Diagramming Tools
Data Repositories
Prototyping Tools
Test Data Generators
Documentation Tools
Project Management Tools

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 12

Phase 3: System Design

Documentation Produced
System Design Report
Describe Alternatives including:
Inputs/Outputs
Processing
Storage and Backup

Recommend Top Alternative based upon:

System Fit into the Organization
Flexibility for the future
Costs vs. benefits
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 13

Phase 4:
System Development
Build the system to the design specifications
Develop the software
Purchase off-the-shelf software OR
Write custom software

Acquire the hardware

Test the new system
Module (unit) test - tests each part of system
Integration testing - tests system as one unit

Create manuals for users and operators

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 14

Phase 5:
System Implementation
Convert from old system to new system
Train users
Compile final documentation
Evaluate the new system

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 15

Phase 5: System Implementation

Types of Conversion
Direct/plunge/crash approach entire new system
completely replaces entire old system, in one step
Parallel approach - both systems are operated side by
side until the new system proves itself
Pilot approach - launched new system for only one
group within the business -- once new system is
operating smoothly, implementation goes company-wide
Phased/incremental approach - individual parts of new
system are gradually phased-in over time, using either
crash or parallel for each piece.

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 16

Phase 5: System Implementation

User Training
Ease into system, make them comfortable,
and gain their support
Most commonly overlooked
Can be commenced before equipment
delivery
Outside trainers sometimes used

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 17

Phase 6: Operations & Maintenance

Types of changes:
Physical repair of the system
Correction of new bugs found (corrective)
System adjustments to environmental
changes
Adjustments for users changing needs
(adaptive)
Changes to user better techniques when they
become available (perfective)

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 18

Phase 6: Operations & Maintenance

Evaluation Methods
Systems audit - performance compared to
original specifications
Periodic evaluation - checkups from time to
time, modifications if necessary

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 19

SDLC Advantages and Disadvantages

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 20

MIS
Various Approaches to
System development

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 21

Systems Development Approaches

Traditional
Alternatives

Prototyping
Rapid Application Development
CASE-based
Time-boxing

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 22

The Traditional Approach

Often called Waterfall Approach/ Model
Investigation

Design

Construction

Implement
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 23

The Traditional Approach (Conti)

There are four phases
One phase is completed before beginning
next phase
Emphasis on documentation and
checkpoints
Detailed planning and budgeting at each
phase

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 24

Pros and Cons of Traditional Approach

Advantages
Lends itself to good control
Phase deliverables well defined
Facilitates contracting

Clear checkpoints makes reviews easy

Creates detailed documentation which is
valuable for maintenance

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 25

Pros and Cons of Traditional Approach (Conti)

Disadvantages
Time and cost estimation difficult
Can be very slow
Requires that requirements are defined
abstractly, without interaction with system
Overall ownership usually on systems
people

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 26

Prototyping Approach

Prototyping approach:
Takes advantage of availability of fourth
generation procedural languages and
relational database management systems
Enables creation of system (or part of
system) more quickly, then revise after
users have tried it
Is a kind of evolutionary development
process
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 27

Prototyping Approach (Conti)

Prototyping examples:

Input and output screens developed for users to

test as part of requirements definition

First-of-a-series a completely operational

prototype used as a pilot

Selected features only some essential

features included in prototype, more added later

Prototyping used as a complete alternative to

traditional SDLC methodology

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 28

Prototyping Approach (Conti)

Good when requirements hard to define
Good when system needed quickly
Impractical for large, complex
applications

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 29

The prototyping process

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 30

Prototyping Advantages and Disadvantages

Advantages:

Only basic requirements needed at front end

Used to develop systems that radically change how work is

done, so users can evaluate

Allows firms to explore use of new technology

Working system available for testing more quickly

Less strong top-down commitment needed at front end

Costs and benefits can be derived after experience with initial

prototype

Initial user acceptance likely higher

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 31

Prototyping Advantages and Disadvantages

Disadvantages:

End prototype often lacks security and control features

May not undergo as rigorous testing

Final documentation may be less complete

More difficult to manage user expectations

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 32

MIS
End User Systems
Development

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 33

End User Systems Development

End-user systems development: is a
term that was originally used to describe
the development of information systems
by individuals outside of the formal IS
planning and departmental structure.

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 34

Potential Problems for

Systems Development

Solving the wrong problem.

Poor problem definition and analysis.
Poor communication.
A project that is too ambitious.
A lack of top management support.
A lack of management and user
involvement

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 35

Potential Problems for

Systems Development (Conti)

Failure to use a standard systems

development approach.
Inadequate or improper systems design.
Poor testing and implementation.
A lack of concern for maintenance.

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 36

Success Factors in
Systems Development
Clearly defined organizational goals.
A sharp focus on, and clear
understanding of, the most important
business problems or opportunities.
Clearly defined systems development
objectives.
Support of top-level managers.
Involvement of users at all stages.
Use of a proven systems development
method.
Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 37

Success Factors in
Systems Development
Creating or aligning incremental systems
benefits with normal user work activities
so as to provide incentives for effective
system interaction.
Managing change.
A simple and straightforward design.
Good training programs for all involved

Copyright 2006, The McGraw-Hill Companies, Inc. All rights reserved.

4 - 38