BCS: Certificate in

Software
Development

System Development Life Cycle (SDLC)

 Approaches to Systems Development

1) Process-Oriented Approach
 Focus is on flow, use and transformation of data in an information system
 Involves creating graphical representations such as data flow diagrams and
charts
 Data are tracked from sources, through intermediate steps and to final
destinations
 Natural structure of data is not specified
 Look at all of our
processes

 Processes take
precedence over
data

 Get the processes

correct first

 Worry about the

data after
 2) A Data-oriented approach

• Depicts ideal organization of data, independent of where and how data are
used

• Data model describes kinds of data and business relationships among the data

• Business rules depict how organization captures and processes the data

• Create User Stories

 Forget the processes,
look at the data

 Data comes first, get

the data correct

 Once the data have

been defined
correctly, look at how
the processes actually
use the data
 3) Object Oriented Approach

 Define the objects that are

part of the system first
 Identify use cases; What
happens and what are the
responses to those actions
 Build the remainder of
systems once use cases are
identified
 THE SYSTEMS DEVELOPMENT
LIFE CYCLE
 In many ways, building an information system is similar to building a house.

1. First, the owner describes the vision for the house to the developer.
2. Second, this idea is transformed into sketches and drawings that are shown to the
owner and refined (often, through several drawings, each improving on the other) until
the owner agrees that the pictures depict what he or she wants.
3. Third, a set of detailed blueprints is developed that presents much more specific
information about the house (e.g., the layout of rooms, placement of plumbing fixtures
and electrical outlets, and so on).
4. Finally, the house is built following the blueprints—and often with some changes and
decisions made by the owner as the house is erected.
 All systems have a life cycle or a series of stages they naturally undergo.

 The number and name of the stages varies, but the primary stages are conception,
development, maturity and decline.

 The systems development life cycle (SDLC) therefore, refers to the development
stage of the system’s life cycle.
 SDLC vs. System Development Methodologies

 There is a difference between the term SDLC and the term ‘methodology’.
 The term SDLC is frequently used synonymously with the waterfall or traditional
approach for developing information systems.
o SDLC: refers to a stage all systems naturally undergo,
o A Methodology refers to an approach invented by humans to manage the
events naturally occurring in the SDLC.
 Fundamental phases of SDLC

 Building an information system using the SDLC follows a similar set of four
fundamental phases:

Planning  analysis  design  implementation.

 Each phase is itself composed of a series of steps, which rely on techniques

that produce deliverables (specific documents and files that explain various
elements of the system).
Phases
of SDLC
 1. Planning

 The planning phase is the fundamental process of understanding why an

information system should be built and determining how the project team will
go about building it.
 It identifies whether or not there is the need for a new system to achieve
business’ strategic objectives.
 The system’s business value to the organization is identified — how will it lower
costs or increase revenues?
 Most ideas for new systems come from outside the IS area (from the marketing
department, accounting department, etc.) in the form of a system request.
 A system request presents a brief summary of a business need, and it explains how
a system that supports the need will create business value.
 The IS department works together with the person or department generating the
request to conduct a feasibility analysis.
 The system request and feasibility analysis are presented to for approval
 FEASIBILITY STUDY
 A feasibility study is carried out after real problems have been identified so as to
determine the most favourable solution.
 An analyst should list all possible solution objectives and analyse each solution
objective in detail.
 Some of the areas looked at for each alternative are as below:
i. Economic feasibility
ii. Social feasibility
iii. Technical feasibility
iv. Operational feasibility
v. Schedule feasibility
 i) Economic Feasibility

 Economic feasibility aims at justifying the costs of implementing the new

system by looking at the available financial resources.
 It aims to prove that the new system will return funds invested in a favourable
period of time.
 It also assesses whether operational inputs are far below outputs produced.
 If so, then the system is said to be feasible.
 Such financial analysis is done using like ROI and NPV.
 a) Return on investment (ROI)

 Return on investment (ROI) measures the gain or loss generated on an

investment relative to the amount of money invested.
 ROI is usually expressed as a percentage and is typically used for personal
financial decisions, to compare a company's profitability or to compare the
efficiency of different investments.
 The return on investment formula is:

ROI = (Net Profit / Cost of Investment) x 100

 b) Net present value (NPV)

 Net present value (NPV) is the present value of an investment's expected cash
inflows minus the costs of acquiring the investment.
 The formula for NPV is:

NPV = (Cash inflows from investment) – (cash outflows or costs of

investment)
 c) Cost-Benefit Analysis
 A cost-benefit analysis is a process by which business decisions are analyzed.
 The benefits of a given situation or business-related action are summed, and
then the costs associated with taking that action are subtracted.
 It is a procedure for estimating all costs involved and possible profits to be
derived from a business opportunity or proposal.
 It takes into account both quantitative and qualitative factors for analysis of the
value for money for a particular project or investment opportunity.
 ii) Social Feasibility
 This is an evaluation on effects of introducing the new system on the
organization’s human resources.
 It seeks to establish who are going to lose their jobs and won’t? What
training needs are there? What benefits will employees realise from the
new system?
 The major emphasis, however, is to concertize employees of the need to
introduce the new system and foster a positive mind in them so as to avoid
deliberate sabotage when the system is implemented.
 This is so because most workers feel threatened every time changes in their
work areas are introduced.
 iii) Technical Feasibility

 This is a study, which seeks to prove whether the technology required for
the new system is readily available.
 How efficient and effective will the targeted technology be if used as
solution gadgets?
 Other areas of consideration include the availability of backup and spares
or consultancy.
 iv) Operational Feasibility
 An evaluation of the input processing and output procedures is made on each
functional unit (subsystem).
 What changes in operational style will there be?
 The solution should not require an overhaul of management or require major
changes in management responsibilities and chains of command, and then the
system is not feasible.
 The system should not be in conflict with the way in which the organization
carries out its standard business.
 v) Schedule feasibility

 A measure of how reasonable the projected timetable is.

 The project has to be completed within reasonable time-frames
 Feasibility Study Report
 After, the feasibility study a “Feasibility Study Report” is compiled and
submitted to management for approval.
 Among the set of alternatives, the system analyst should specify a
recommended solution objective.
 Management may adopt the recommended course of action or any of the
listed solutions.
 It is possible that they may reject all listed solutions and as such may request
for new studies.
 If, however, approved then the next step commences.
Contents of the feasibility study report

1. Terms of reference giving exactly what the system areas the working group.

2. Description of the current system

3. A description of the hardware and software

4. Outline of both existing and proposed systems

5. Costs and likely benefits of the new system

6. Proposed system alternatives

7. Staff and training requirements

8. Suggested implementation timetables

9. Recommendations and justification

 4. SYSTEMS ANALYSIS
 Systems analysis is a process of collecting factual data, understand the
processes involved, identifying problems and recommending feasible
suggestions for improving the system functioning.
 This involves studying the business processes, gathering operational data,
understand the information flow, finding out bottlenecks and evolving
solutions for overcoming the weaknesses of the system so as to achieve the
organizational goals.
 System Analysis also includes subdividing of complex process involving the
entire system, identification of data store and manual processes.
Major objectives of systems analysis
 The major objectives of systems analysis are to find answers for each business
process:

1. What is being done?

2. How is it being done?

3. Who is doing it?

4. When is he doing it? Why is it being done?

5. How can it be improved?

 SYSTEMS ANALYSIS
 It is more of a thinking process and involves the creative skills of the System
Analyst.
 It attempts to give birth to a new efficient system that satisfies the current
needs of the user and has scope for future growth within the organizational
constraints.
 The result of this process is a logical system design.
 System analysis is an iterative process that continues until a preferred and
acceptable solution emerges.
 Analysis stage in summary
 In summary, the analysis stage involves the detailed study of;

1. The information needs of the organization and end users

2. The activities, resources, and products of any present information system

3. The information system capabilities required meeting your information

needs, and those of other end users.
 5. System Design
 After analysing the analyst is now able to made the final solution selection or
refinement. He then begins to build a design of the system.
 Considered here are the physical design and logical design.
 The physical design refers to the physical layout of buildings, equipment, office
arrangement, etc.
 The logical design maps out the logic in processing procedures. This includes program
design.
 Also included is the development of specifications for the hardware, software, people
and data resources and the information products that will satisfy the functional
requirements of the proposed system.
 The design stage mainly involves the design of inputs, outputs, files, and programs.
 Logical & Physical Design
1. Logical design – this is the planning of the system, as the users require it. It
emphasizes the application as seen by those who will operate or use the
outputs of the system i.e. files needed, input forms/screens, output
forms/screens, control procedures etc.

2. Physical design – refers to the layout of office furniture, building blocks,

curtains, and other physical considerations to facilitate smooth system
operation.
“Thank You”
Compiled by f. Zinyowera