System Development Life Cycle
System Development Life Cycle
System analysis and design is a series of processes for analysing and designing computer-
based information systems. Systems design allows a development team to roughly see what
and how their system will look like. An important result of systems analysis and design is
application software, that is, software designed to support a specific organizational function
or process.
One or more of the following situations will initiate an individual application or project:
Techniques – Particular processes that an analyst will follow to ensure that the work
is well thought-out, complete and comprehensible to others on the project team.
Tools – Computer programs that make it easy to use and benefit from the techniques
and to faithfully follow the guidelines of the overall development methodology.
System analysts use the system analysis and design process to develop new systems. They
study the organization’s present systems and suggest actions to be taken after doing
preliminary investigations.
Different approaches to system development are:
1. System Development Life Cycle (SDLC)
2. Structured Systems Analysis Design Methodology (SSADM) – Data driven methodology
3. Prototyping Method – User driven method
4. Rapid Application Development (RAD)
1. Preliminary survey/study
2. Feasibility study
3. Facts finding and recording
4. Analysis
5. System design
6. System development
7. System implementation
Preliminary study
This stage involves determination of whether there is need to change the existing system or
business procedures. It may require management requests for a change of the existing
system to give an organization a competitive advantage or to improve the staff morale. The
user department should be involved during the definition of the problem. The problem to be
solved should be very specific, clear and precise. It should not be too broad to cause
ambiguities in its solution.
Terms of reference
It is a documentation prepared by steering committee to act as a reference document
throughout system development stages. Its contents include:
Project title
Subject of study
Purpose of study
Personnel
Departments
Sections affected or involved during the system implementation
Available resources and constraints, the analyst, the project leader should consider
The projects estimated duration and schedule
Steering committee
It is formed by two or three people to oversee the system development project from its
initiation to its completion. It comprises of the system analyst as the project leader and a
representative of the user department. They should understand all the processing objectives
and procedures within the affected department. A management representative and
accountant or auditors may be incorporated to advise initially on financial aspects on the
project.
Technical Feasibility
Technical questions are those that deal with equipment and software e.g. determination of
whether the new system can be developed using the current computer facilities within the
company. Technical feasibility is thus aimed at evaluation of the following:
Social Feasibility
This is also known as operational feasibility. It mostly deals with the effect of the system on
the current society within the company. It is carried out on the following areas:
i. The reaction of individuals both inside and outside the company as a result of the
new system.
ii. The effect of the system on the existing organizational structure.
iii. The effect of the system on the current working practices and management levels
i.e. whether there would be any change required and if so the cost of the change
socially.
iv. Redundancy or retrenchment, implication to the company as a result of the new
system.
v. Implication of the system on existing staff development programmes.
The social feasibility is carried out along with technical feasibility such that the social
implications of every alternative technical solution to the problem that emerges are
evaluated. Areas to consider include:
Group relationships
Salary levels
Job titles and job descriptions
Social costs to be evaluated e.g. cost of user training, consultancy that may be
engaged during development of the new system, job improvements and salary
changes.
Legal Feasibility
The new systems legal implications should be evaluated e.g. if it requires that the computer
should be insured or whether the stored data should be registered with the government
registrar before use. The copyright implication for restriction should be assessed before the
new system is implemented. Generally any legal aspects associated with the new system
should be assessed, and adequate measures taken to protect the interest of the user
company.
Economic Feasibility
Economic feasibility is aimed at determination of whether or not to continue with the project,
depending on whether the project is economically viable. The systems benefits and
estimated implementation cost should be determined before any further resources can be
spent on the project.
A cost benefit analysis (CBA) is carried out to determine whether the new system is
economically viable.
i. Direct (Tangible)–fall under two categories: measurable benefits and direct savings.
Measurable benefits are those that can be quantified in monetary terms e.g. increase in
working capital as a result of purchasing of computer systems or reduction of delays in
decision making which is obtained through improved procedures e.g. invoicing procedures
and credit control procedures.
ii. Intangible benefits – they are benefits that cannot be quantified in monetary terms or
those that are difficult or impossible to quantify in monetary terms.
They are clearly desirable but very difficult to evaluate in terms of money value e.g.
improved customer satisfaction, better information, improved organizational image,
increased staff morale, a competitive advantage to an organization etc.
Cost Analysis: Costs are expenses or expenditure which are incurred by a system. These
may include equipment cost, development cost, operation cost and software cost. During
cost analysis one should consider both the new and the existing system. The cost of retaining
and operating the existing system should be compared to the cost of introducing and running
the computerized information system.
a) The cost of running the existing system. This is calculated from the past records. The
items to consider include:
i. Man power cost – which is extracted from the budgets and payroll reports
ii. Material cost – which includes consumables e.g. stationery, work in progress and
current stock
iii. Operational cost e.g. the equipment cost expressed in terms of unit rate. Others to
consider include the duration the project takes to be completed and initial
replacement cost.
iv. Overhead costs – which are direct expenses incurred by the company on behalf of
all departments e.g. rent, electricity, telephone bill etc. These can easily be
extracted from departments or centres to which they are allocated.
v. The intangible cost of existing system e.g. loss of sales or cost of sales as a result
of inappropriate stock levels or loss of interest in bank as a result of improper credit
control system.
b) The cost of operating the proposed system – this is likely to include all the areas covered
above i.e. manpower, materials, overheads and the intangible costs. However there are
additional costs associated with computerized systems e.g. service contracts for the
computer system, insurance of the computer system, cost of data transmission, cost of
consumables like printer cartridges, ribbons etc. All these costs should be evaluated or
estimated as accurately as possible.
c) The cost of new system development – Includes the cost incurred for any consultancy
services that may have been hired during development. Allowances given to the system
development team members fall under this category. Overall effects of the system
development and implementation should be determined and any cost associated
established. These estimates are based on both time and activities involved in the project.
Staff training cost, recruitment costs and retrenchment costs should be considered under
system development cost.
Cost benefit analysis should be conducted on each alternative solution to the problem. This
enables the analyst to make recommendation on a suitable cost effective alternative solution
to the problem.
The report is submitted to the management for approval. After approval a more detailed
survey is conducted on the existing system mostly to establish its weaknesses and strengths.
Fact finding/investigation
This involves collection of information about the existing system on which to base analysis in
order to determine whether users current needs are being met. The following are some of the
activities that are looked at:
Fact-finding techniques
a) Use of questionnaires
A questionnaire is a special document that allows the analyst to ask a number of standard
questions set to be asked to a large number of people in order to gather information from
them. It is used when:
- the system analyst is located at a considerably long distance from the
respondent
- there is a large number of respondents such that interviewing them will be
limited by time
- the questions to be asked are simple and straight forward and require direct
answers
- limited information is required from a large number of people
- it is used as a means to verify facts found using other methods.
b) Interviewing
This is a direct face-to-face conversation between the system analyst (the interviewer) and
users (interviewees). He obtains answers to questions he asks the interviewee. He gets the
interviewee’s suggestions and recommendations that may assist during the design of the
proposed system.
Interviews serve the following purposes:
Acts as a method of fact-finding to gather facts about the existing system.
Used for verifying facts gathered through other methods.
Used for clarifying facts gathered through other methods.
Used to get the user involved in the development of the new system.
e) Sampling
Disadvantages include:
The sample may not be representative enough which may lead to incorrect and bias
conclusions
The expertise of the analyst is required since sampling involves a lot of mathematical
computation
Analysis
A system analysis involves evaluation of the current system using the gathered facts or
information. One should evaluate whether the current and projected user needs are being
met. If not, he should give a recommendation of what is to be done. Analysis involves
detailed assessment of the components of the existing system and the requirements of the
system.
Once all the facts are analysed and documented a formal report is written called statement
of requirements.