COMPUTER STUDIES (3rd TERM) – SS2, WK 1

TOPIC: SYSTEM DEVELOPMENT LIFE CYCLE

INSTRUCTIONAL OBJECTIVES

a) Define system development cycle

b) Describe system development cycle
c) Draw a system development cycle
d) List stages in system development cycle
e) Describe briefly, each of the stages involved

INTRODUCTION
At some stage, most businesses, institutions and organizations will need a new
computerized system to help them with their day to day tasks. This could be a system to
keep track of all the students’ information, financial systems, systems used in
manufacturing etc. Often systems analysts are employed by organizations/businesses to
help them improve their systems and so become more efficient and for businesses, more
profitable. Systems Development Life Cycle (SDLC) is a process used by a systems analyst
to develop an information system, including requirements, validation, training, and user
(stakeholder) ownership. Any SDLC should result in a high quality system that meets or
exceeds customer expectations, reaches completion within time and cost estimates, works
effectively and efficiently in the current and planned Information Technology
infrastructure, and is inexpensive to maintain and cost-effective to enhance

DEFINITIONS

System: A system can be defined as a set of components that interact together to achieve
a common goal.
Systems Analyst: A systems analyst is the specialist who develops information system by
performing analysis, designs and implementation. He studies an organization’s
information and communication needs and determines what changes can be made to
deliver better services to the users.
System development: This can be defined as a conceptual model used in project
management that describes the stages involved in an information system development
project from an initial feasibility study through maintenance of the completed application.
In other words, it is a structured step-by-step approach to the establishment and
improvement of an information systems.
SYSTEM DEVELOPMENT LIFE CYCLE

Preliminary Study

Study Review Feasibility Study

System

Development
Maintenance Investigative Study
Life

Cycle
Analysis
Implementation
1

Design
This presents a structure through which all phases of a proposed system can be addressed
starting from conception to the end of the life of the system. The phases/stages involved
are:

i. Preliminary study iv. Analysis vii. Maintenance

ii. Feasibility study v. Design viii. Study review
iii. Investigative study vi. Implementation

1. Preliminary study: The purpose of this stage is to establish whether there is a need for
a new system to be developed or not. If the need is established, you specify the objectives
of the system. Three primary tasks are: 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. This brings about the proposal of a new system.

2. Feasibility study: In case the new system proposed is accepted, the next phase is the
feasibility study phase. This is the test of the new system in terms of workability, meeting
user’s requirements, and effective use of resources and of course, cost effectiveness. In
other words, this tests to ascertain the chances that a system development project will
succeed. The purpose of this phase is to enable the system analyst provide information
that will either justify the development of a new system or show how the project is to be
cancelled. The findings are presented to the management in form of a report. If the report
is in favour of the project, the management may decide to move to the next phase.

3. Investigative Study/Detailed system study: The purpose of this study is to fully

understand the existing system and to identify the basic information requirement. This
requires contribution from the users of the system. A detailed study of the existing system
showing their strengths and weaknesses will enable you to know what to propose as the
new system. It will also require you to observe how the organization uses the existing
system.

4. Analysis: System analysis is the study of sets of interacting entities/bodies that are
required to develop a complete system. At this stage, the system analyst is to perform
detailed analysis activities: study current system, determine user requirements and
recommend solution. The purpose of this stage is to gather data, analyse the data and
hence, write a report. The report should state the following: explain how the existing
system works, explained the problems identified in the existing system and describe the
requirements for the new system and make recommendations on what to do next.

5. Design: This is the process of defining and developing systems to satisfy specified
requirements of the user. This phase involves: defining the requirements for the output,
input, storage, processing system controls and back-up. Project management software
tools such as flow chat, algorithm etc are used to create the system drafts. At the end of
this stage, a report is presented showing all that is required to transform the user’s needs
to a working.

6. Implementation: This is the actual realisation of an application, or execution of a plan,

idea, model, design, specification, standard, algorithm or policy. It involves transforming
the details set out in the system specification to a functioning system. Three important
tasks are carried out in this phase, namely: develop a program using any programming
language or acquire the software (also known as the build phase), acquire the hardware
and test (also known as the test phase) the system.

7. Maintenance: The objective of this phase is to adjust and improve the system. The
system must be monitored to ensure that it is successful. Maintenance includes: keeping
the hardware and software running, updating and upgrading the system to keep pace with
user’s requirement.
8. Study review: From time to time, the requirements of an organization will change and
the system will have to be examined to see if it can cope with the changes. At some point,
the organization may be spending too much in maintaining the existing system and as
such, there may be the need to start the entire systems development cycle all over again.

BENEFITS OF SDLC

SDLC done right can allow the highest level of management control and documentation.
Developers understand what they should build and why. All parties agree on the goal up
front and see a clear plan for arriving at that goal. Everyone understands the costs and
resources required.

Several pitfalls can turn an SDLC implementation into more of a roadblock to development
than a tool that helps us. Failure to take into account the needs of customers and all users
and stakeholders can result in a poor understanding of the system requirements at the
outset. The benefits of SDLC only exist if the plan is followed faithfully.

ASSIGNMENT

Group work: Give a case study of a system (in any walk of life) and describe its development
life cycle with the aid of a diagram