Information System Development

Need for Structured Systems Development

Evolution of IS Development

Options for obtaining IS

1. Build IS

2. Buy Pre-packaged system

3. Outsource development to third party

4. End User development.
System Development Life Cycle.
SDLC has five primary phases,

1. System Identification, Selection and Planning
2. System Analysis
3. System Design
4. System Implementation
5. System Maintenance
System Identification,
Selection and Planning

System Analysis

System Design

System Implementation

System Maintenance
SYSTEM
IDENTIFICATION
SYSTEM SELECTION
SYSTEM PLANNING
1. System Identification, Selection
and Planning

System Identification,
Selection and Planning

System Analysis

System Design

System Implementation

System Maintenance
COLLECTING SYSTEM
REQUIREMENTS
MODELING
ORGANIZATIONAL DATA
MODELING
ORGANIZATIONAL
PROCESSES AND LOGIC
2. System Analysis

Validate
Regn Informn
Class Database Register Class
Notify Student
of Success
Master Class
List
Notify Student
Of
Error
Class
Registration
Form
Class
Information
Valid
Registration
Valid
Registration
Update Class
Roster
Update
Student Billing
Registration
Error
Invalid
Registration
Completed
Registration
Registration
Success
DATA FLOWS
System Identification,
Selection and Planning

System Analysis

System Design

System Implementation

System Maintenance
Designing Forms and
Reports
Designing Interfaces and
Dialogues
Designing Databases and
Files
Designing Processing and
Logic
3. System Design
System Identification,
Selection and Planning

System Analysis

System Design

System Implementation

System Maintenance
Software Programming and
Testing
System Conversion,
Documentation, Training
and Support
4. System
Implementation
5. System Maintenance

1. Corrective Maintenance

2. Adaptive Maintenance

3. Perfective Maintenance

4. Preventive Maintenance.
Other Approaches to Designing and Building Systems
1. Prototyping
2. RAD Rapid Application Development
Collect Requirements
Develop/Refine Prototype
Review Prototype
with User
Implement and
Use System
Does User
Accept Prototype
yes
no
PROTOTYPING
Requirements and
Design are Redefined By
Analysts
Groups Define
Requirements
System is
Completed
User Reviews and Provides Additional Requirements
Rapid
Application
Development
Prototyping
Strengths: Develops close working relationship between designer and
users: works well for messy and hard-to-define problems
Weakness: Not practical with a large number of users: Systems may be
built too quickly, which could result in lower quality

Rapid Application Development
Strengths: Active user involvement in design process: easier
implementation due to user involvement

Weakness: Systems are often narrowly focused limits future evolution:
System may be built too quickly, which could result in lower quality



Need for Alternatives to In-House System
Development
Limited IS staff
IS staff has limited skill set
IS staff is over worked
Problems with performance of IS staff.

Common Alternatives to In-House System
Development
1. External Acquisition
2. Outsourcing
3. End User development.
Thanks