CS-101 Introduction to Computers F.

E (IM) Session 2011

Introduction to Software Development Process Course Instructor: Syed Jaseemuddin

INTRODUCTION TO SOFTWARE DEVELOPMENT PROCESS

Systems Development Life Cycle (SDLC)

The formal process by which organizations build systems is known as Systems Development Life Cycle
(SDLC). The extent to which your job brings you in contact with your organization’s SDLC will depend
on a number of factors such as:

 The size of organization.

 Your job description.
 Your relevant experience.
 Your educational background.

In large companies SDLC usually involves clearly defined standards and procedures.

Ways of Participation:

 You will be required to inform the programmers about the manual procedures you use, or the
routines that you follow on an existing system.
 Management may require employee input in developing new system, through a process called JAD
(Joint Application Development).
 You may be required to provide system analyst and designers with departmental objectives and
requirements.
 You may be involved in approval of budgets.
 As the development of new system nears completion, you will probably help evaluate it and test
whether it works as expected.
 You will attend briefings and training sessions to learn how new system will effect your job and what
its new operating procedures will be.
 You will end up using the new.

Causes of System Failure:

 Lack of communication.
 Continuation of a project which should have been cancelled (aborted).
 The failure of two or more portions of new system to fit together properly (compatibility issues).
 Company Politics.
 Lack of Management support.
 Technological incompetence.
 Lack of user training.

Page 1 of 4
CS-101 Introduction to Computers F.E (IM) Session 2011
Introduction to Software Development Process Course Instructor: Syed Jaseemuddin
Software Development Life Cycle:

Phase I
Preliminary Investigation Approved Feasibility
Study

Phase II
System Analysis
Problem Specification

Phase III
System Design Design Specification

Phase IV
System Development/
Aquisition Coded and Tested
System

Phase V Documentation Complete,

System Implementation Users Trained, System in
Operation

Phase VI
ABORT Maintenance

System Analyst:

The computer professional generally in-charge of the SDLC is the head System Analyst, also called
System Engineer of Project Leader.

Steering
Commitee
Information
Users Tehnology
Vendors

Management
| System
System Application
Programmers
Owner
Analyst
Database Network
Admin Admin
Interface
Design
Expert

Page 2 of 4
CS-101 Introduction to Computers F.E (IM) Session 2011
Introduction to Software Development Process Course Instructor: Syed Jaseemuddin

Phase I: Preliminary Investigation

 Conduct preliminary analysis. This includes stating the objectives, defining nature and scope of
the problem.
 Propose alternative solutions:
 Leave system alone.
 Upgrade previous system (make more efficient).
 Build a new system.
 Describe cost and benefit of each solution.
 Submit a preliminary plan (often called feasibility report or system survey) with recommendations.

Phase II: System Analysis

 Gather data, using written documents, interviews, questionnaires, observations and sampling.
 Analyze data using CASE Tools (Computer Aided Software Engineering), data flow diagrams,
system flow-chart, connectivity diagrams, grid charts and decision tables.
 Write a report with recommendations.

Phase III: System Design

 Do a preliminary design using CASE Tools and Project Management Software (e.g. Rational Rose).

o CASE Tools
CASE Tools can be used for many functions. Among these are:
 Diagramming
 Prototyping
 Throw-away Prototyping
 Evolutionary Prototyping
 Reporting
 Managing Quality
 Supporting Decisions
 Organizing Documentation
 Generating Code
 Testing
o Project Management Software
Project Management Software uses Gantt and PERT (Program Evaluation Review
Technique) charts.
 Gantt chart allows you to see whether tasks are being completed on schedule.
 A PERT Chart not only shows timing but also the dependencies among the tasks
of a project.

 Do a detailed design defining requirements for output, input, storage, networking, system
control and backup.
 Write a report with recommendations.

Phase IV: System Development/ Acquisition

 Acquire Software
 Acquire Hardware
 Test the system (done in following 2 stages)

Page 3 of 4
CS-101 Introduction to Computers F.E (IM) Session 2011
Introduction to Software Development Process Course Instructor: Syed Jaseemuddin
 Unit Testing (Modules are tested individually.)
 System Testing (The system is tested completely after integration of modules).

Phase V: System Implementation

 Convert hardware, software and files through one of the 4 types of conversion:
 Direct  Parallel  Phased  Pilot

o Direct Implementation
All at once change. Old New
System System
Parallel Implementation
Both the new and the old system are functional at the same time.

Old System

New System

o Phased Implementation
Also referred to as gradual implementation, in this method, the system is implemented in
steps.
o Pilot Implementation

Old New
System System

The system is initially implemented only in one part of company on beta basis.

Old System
New System

 Compile final documentation.

 Train users.

Phase VI: Maintenance

 The sixth phase is to keep system running through system audits and periodic evaluation.
 Auditing
Auditing means an independent review of an organization’s information system, to see if all
records and systems are as they should be.
 Evaluation
Evaluation is a measure of working of the system against some present criterion. Evaluation may
be done by Head System Analyst or by a user or by some client.

Page 4 of 4