Professional Documents
Culture Documents
CH 4 BIS
CH 4 BIS
Information System
Development
Outline
IS Development Life Cycle(SDLC)
Problem Definition
Feasibility Study
System Analysis
System Design
System Development
System implementation
2
Definition of Information System Lifecycle
Deliverables
Problem
Feasibility System
Definition
Study Analysis
“To Be”
System System
System
Development Implementation
Design
space, personnel, HW, Install
Design new/alternative system – Develop Programs, test & test new system, train &
components, I/O relationships programs, documentation migrate to new system
data, program, interfaces,
Logical System
Idea changed into design (logical model) – flow of data,
Physical System
The logical design/model is changed into programs, data
5
Participants in System Development
System Stakeholders (Beneficiaries – directly or
indirectly)
Users (interact with the system)
Project leader
Systems analyst
System Designer
System Administrators
6
Problem Definition
etc.)
What Opportunities to provide? (expanding performance,
7
Cont.
Define project boundaries
Part of a system to be changed, parts outside its control
Develop terms of reference (TOR) & define resource to
be availed
Final output:
Terms of Reference (goals, bounds & resource requirements)
8
Feasibility Study
The practical utility & acceptability of the proposed
system
Can it be done?
9
Feasibility
10
Feasibility
communication, output
Availability
Within budget
Sophistication
Final Output:
•Feasibility report - GO / NOT GO decision must be made
12
System Analysis
Study of the existing system: Deals with “the way
things are”
procedures
Observation
Conducting interview – with top mgt and users
Questionnaire
14
Cont.
Results of System Analysis Detailed documentation of:
How the existing system works
requirements
15
Chapter IV
System Design
Form design
Report layouts
Processing
17
System Development
Programs:
Coordinate the data movements and
18
Cont.
Steps
Checking system specifications
Breaking system modules into smaller
programs
programs must be modular in
20
Cont.
System/Technical Documentation
Preparing documentation for each program
Requirement documentation
Source code
Testing
User Documentation
Create manual for users and operators
21
System Implementation
Procurement of HW
Installation of SW
22
Cont.
Motivation and training of selected personnel and users
Training – how to use the system, how to enter data, how to process
and generate reports
Ease into system, make them comfortable, and gain their support
Conversion of data files from old system to the new
system
23
Cont.
Final switch – approaches
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
new system launched for only one group within the business -- once new
Phased/incremental approach
individual parts of new system are gradually implemented over time, using
24
Post-implementation (maintenance & review )
Types of Changes:
Physical repair of the system
Evaluation Methods
System
Design Specifications
Design
Coded and
System Tested System
Development
Begin building
new system System System conversion
Implementation
Users trained
System
Maintenance Operational System
Documentation completed
26
Cont. Chapter IV
27