6.

0
System
Development Life
Cycle (SDLC) 1
 Learning Outcome

a) Identify 5 steps of system development life cycle based on

activities in SDLC. (Planning, Analysis, Design,
Implementation, Support & Security) - Lecture
b) Explain the steps of system development life cycle (Planning,
Analysis, Design, Implementation and Support & Security). -
Tutorial

2
 System Development Life Cycle (SDLC)

Definition SDLC :
- collection of phases in system development activities to build
an information system
- each phase of system development consist of a series of
activities and the phase form a loop

- Information system is a
collection of hardware, software, - System development is a set of
data, people and procedures that activities used to build an
work together to produce information system
information

3
 Why do we need a System
Development Project?
What Initiates a System Development Project?

to correct a problem such as an incorrect

calculation or a security breach

to improve the information system -

modify system

to make sure the system works as

planned
4
System Development Guidelines

1. Group activities
into phases

Users include anyone for whom the system

2.Involves users is built in. e.g : Customers, employees,
students, data entry specialist

3.Define Standards are sets of rules and

procedures an organization expects
standards employees to accept and follow

5
Who participates in System
Development?

6
 Groups of people that participate
in system development

Steering committee : a group of people

Project development team : a group of
that makes decisions in an organization,
people that consists of users, the system
usually includes vice presidents,
analyst and other IT professionals.
managers, non-management users and IT
personnel.

Non Technical user and IT professionals

:Database analyst, database
administrators, web developers, software
developers, vendors and the steering
committee.
7
Phases in SDLC

1.PLANNING

5. SUPPORT &
2. ANALYSIS
SECURITY
SDLC

4.
IMPLEMENTATION
3. DESIGN
8
 Component of Information
System
Hardware : Hardware refers to the computer system that the database
system runs on. Example mainframe, minicomputer, microcomputer,
network, input/output peripherals etc.
Software : Software refers to a collection of programs used by a computer in
a database system. This includes the DBMS, the operating system of a
computer and network, application and utility program.
Data : Data comprises all facts stored in a database. This includes
operational data and metadata.
Procedures : Procedures refer to the instruction and rules that govern the
design and use of a database system
People : People encompass all users of a database system. This includes
the business analysts, database designer, data administrators, DBA,
application programmers and end-users.
9
Ongoing Activities

Project Management Documentation

Data and Information

Gathering Techniques (in
Analysis phase)

10
Project Management

the process of planning, scheduling and controlling the

activities during system development

deliver an acceptable system to the user in an agreed-upon

time frame, while maintaining cost.

Popular tools used to plan and schedule the time

relationship among project activities. Eg : Gantt and PERT
Chart

11
Project Management tools

12
Project Management tools

13
Project Management tools

14
 Feasibility Assessment

Feasibility is a measure of how suitable the development of

a system will be to the organization
Technical Economic
Schedule feasibility - feasibility / cost
Operational measures whether
feasibility - feasibility -
feasibility - the organization has
measures or can obtain the
measures
measures whether the
whether the computing
how well the resources, software lifetime benefits
established
proposed services and of the proposed
deadlines for qualified people information
information
the project are needed to develop, system will be
system work deliver and support greater than its
reasonable
the proposed lifetime course
information system

15
Feasibility Study

16
 Documentation

Documentation is a collection and

summarization of data, information and
deliverables

It is important that all documentation be

well written, thorough, consistent and
understandable
The final information system should be
reflected accurately and completely in
documentation develop throughout the
development project 17
Data and Information Gathering
Techniques
Review documentation - System analysts learn about the history of the
project such as its operation, weaknesses and strength.

Observation - Helps systems analysts understand exactly how they

perform a task.

Interview - It allows the systems analysts to clarify responses and probe

during face-to-face feedback.

Survey - to obtain data and information from a large number of

people, systems analysts distribute surveys.

JAD session - group meeting with IT professionals.

Research - reference books, newspapers, trade shows, technology

magazines and journal, the web, vendors and consultants 18
SDLC Deliverables

Deliverables are the tangible outputs produced in each

phase of the System Development Life Cycle (SDLC)

19
 Example of deliverables for each phase of SDLC

Planning Analysis Design Implementation Support and

Security
● Cost ● Analysis of ● Graphical user ● Deployment ● New or
estimation existing system interface of software modified
● Preliminary ● Analysis of ● Functional ● Code/ system
investigation intended requirement documentati
results system ● Specification on
● Approved ● Preliminary of the modified ● Training/
feasibility investigation system Procedure/
study Support

20
 Learning Outcome

a) Identify 5 steps of system development life cycle based on

activities in SDLC. (Planning, Analysis, Design,
Implementation, Support & Security) - Lecture
b) Explain the steps of system development life cycle
(Planning, Analysis, Design, Implementation and Support &
Security). - Tutorial

21
1st Phase : Planning
Purpose

To identify the potential project and to allocated

required resources

22
1st Phase : Planning

Begins when a steering committee receives project

requests from users.

Committee members usually consist of five to

nine members. These committee includes a mix of vice
presidents, managers, non management users and IT
personnel

23
 1st Phase : Planning
4 Major Activity

Steering Committee 4 Major Activities

Receive the project request
1 2 3 4
Consists of : Review Prioritize Allocate Form a
i. Managers and the resource project
ii. IT Personnel approve project develop
iii. Vice president the request ment
iv. Non management users project team
request

24
 1st Phase : Planning
4 Major Activity

Major Activity Description

(1) Review and - User’s requests to modify an existing system or to
approve the project create a new system will be reviewed by the steering
request committee and some will be approved and rejected by
others.
(2) Prioritize the - The approved project requests will be prioritized
project request according to the importance of the system requested.
(3) Allocate resources - The steering committee will decide on the resources to
such as money, people be allocated for the projects.
and equipment to - Resources include money, people, equipment and time.
approved projects
(4) Form a project - Project development team will be formed.
development team for - The team normally consists of system analysts ,
25
each approved project programmers and designers.
 1st Phase : Planning
Tool Used

- The steering committee evaluates the remaining project

request based on their value to the organization. The
steering committee approves some projects and rejects
others
- Used to identify the potential projects and to allocate
required resources.
- A project request is a request made by the users to create
a new system or to modify an existing system.

Tool used : Microsoft Project to create Gantt Chart or PERT

Chart
26
2nd Phase : Analysis
Purpose

To determine the exact nature of the problem or

improvement to be made and decide whether it is
worth pursuing.

27
2nd Phase : Analysis
2 Major Activity

2 Major Activities
System Analyst

1 2
Conduct preliminary
Perform detailed analysis
investigation

28
 2nd Phase : Analysis
Major Activity 1

Major Activity Description

- System analyst conducts a feasibility study of the project about the
existing system, benefits of a new or modified system.
- The main purpose - to determine the exact nature of the problem or
(1) Conduct a improvement & decide whether it is worth pursuing.
preliminary - Interview the user who submitted the project request and others users.
investigation - May use other data gathering techniques such as reviewing existing
documentation.
(Sometimes
called the - Upon completion of the preliminary investigation, the systems analyst
feasibility writes the feasibility report to present the team’s findings to the
study) steering committee.
- Steering Committee will decide pursuing or not
- If the project team recommends to continue and the steering
committee approves then detailed analysis begins. 29
 2nd Phase : Analysis
Major Activity 2

Major Activity Description

● Sometimes called logical design because the system analyst
develop the proposed solution without regard to any specific
hardware or software
(2) Perform ● Involves three major activities
detailed
○ Study how current system work
analysis
○ Determine user’s wants, needs and requirements
○ Recommend a solution to modify the current system or to
build a new system.

30
 2nd Phase : Analysis
Method Used

Method used (Refer Ongoing Activity) :

- Data and Information Gathering Techniques
- Interviews. System Analyst
- Questionnaires.
- Observations.
- Review Documents and records.
- Surveys
- JAD Session
- Feasibility Assessment
(Technical, Operational, Schedule, Economical)
31
 2nd Phase : Analysis
The System Proposal
2
Written document. Use to convey all the feasibility of each
alternatives solution and recommend the most feasible
solution for the project

Steering committee
presents a system
1 will decide whether
proposal to steering
to ….
committee for an approval.
Modify existing system

Buy retail software

System Analyst Build custom software

Outsource IT needs to an outside firm 32

 2nd Phase : Analysis
The System Proposal

buy packaged software

• Mass-produced, copyrighted, prewritten software available for

purchase such as word processing, desktop publishing

build custom software

• Write own applications using C++, Java, Visual Basic

• Match organization ‘s requirements.

outsource IT needs to an outside firm

• Having an outside source to develop custom software.

3rd phase : Design
Purpose

To acquire hardware and software needed

for the new system and to create the detailed
design of the new or modified information system.

34
 3rd phase : Design
2 Major Activity

2 Major Activities

1 2
Acquiring necessary Develop details of new
hardware and software or modified information
system
Obtaining additional hardware or
software that meets organization’s
needs by System Analyst

1 2 3 4
Identify Test and
Soliciting Make a
technical evaluate
vendor decision
specification vendor
proposal
proposal 35
3rd phase : Design
2 Major Activity

2 Major Activities

1 2
Acquiring necessary Develop details of new or
hardware and software modified information
system

1 2 3
Database Input Output Program
Design Design Design

36
 3rd phase : Design
Major Activity

Major Activity Description

(1) Acquire Consist of four major task
hardware and 1. Identify technical specifications
software, If 2. Solicit vendor proposals
necessary 3. Test and evaluate vendor proposals
4. Make a decision
(2) Develop all of Detailed design includes:
the details of the 1. Database design - system analyst builds upon the data
new or modified dictionary developed during the analysis phase.
information 2. Program design - system analyst identifies required
system - (Detailed programs and the relationship among the programs.
Design / Physical 3. Input & output design - system analyst carefully designs
Design) every menu, screen & report specified in the requirements.
37
 3rd phase : Design
Major Activity 1

Database
Design

Input Output
Design
Program
Design
38
 3rd phase : Design
Method Used

Method used :
- Tool used : prototyping and CASE (Computer Aided
Software Engineering) tool
- System flowchart - show the flow of input data on
processing and finally to output
- DFD (Data Flow diagram)

39
 3rd phase : Design
Method Used - Prototype

What is Prototype?

■ During detailed design, many system analysts use

a prototype which is a working model of the
proposed system.

40
 3rd phase : Design
Method Used - Prototype

Features of a prototype are :

- A prototype is as interactive as the final app.
- It mimics almost the exact user experience as the real app.
- It allows stakeholders scope for extensive testing.
- It creates ground for new ideas. Sometimes innovative ideas
shape up only when the stakeholders can interact with a
working model.

Advantage of prototype :
- users can work with the system before it is completed.
- make sure it meets their needs.
- speed up the processes of designing a new system.
41
3rd phase : Design
Method Used - Prototype

42
3rd phase : Design
Method Used - Used Case Diagram

43
3rd phase : Design
Method Used - Data Flow Diagram

44
3rd phase : Design
Method Used - Data Flow Diagram

45
4th phase : Implementation
Purpose

To construct, or build the new or modified system

and then deliver it to the users

46
 4th phase : Implementation
4 Major Activity

4 Major Activities

1 2 3 4

Develop Install and

Programs test the Convert to the
Train User
and apps if new new system
necessary system

47
4th phase : Implementation
Major Activity 1

Develop Programs and Apps if

necessary

Programmers write / modify the system following the

program development life cycle.

48
 4th phase : Implementation
Major Activity 1

Major Activity Description

Involves six steps:
1. Analyze the requirements (IPO analysis)

(1) Develop 2. Design the solution (algorithm)

programs and apps 3. Validate the design (test the algorithm)
if necessary 4. Implement the design (write program)
5. Test the solution (run program)
6. Document the solution (prepare documentation)

49
 4th phase : Implementation
Major Activity 2

Install And Test New System

The system analyst should install and test required new

hardware and software because :

a) To avoid error in the system after it is delivered to the

users

b) To make sure that all the programs work together in the

system 50
 4th phase : Implementation
Major Activity 2
Install And Test New System

4 Test Performed

Unit test Systems Integration Acceptance

test test test
• Verifies that • Verifies that • Verifies that • Checks the
each all programs an application new system to
individual in an works with ensure that it
program or application other works with
object works work together applications actual data
by itself properly

51
 4th phase : Implementation
Major Activity 3
Train User

▪ User must be trained properly on a systems functionality

(how to use new hardware and software in the system)
▪ Training methods include
• One-on-one session
• Classroom-style lectures
• Web-based training

52
 4th phase : Implementation
Major Activity 3

Major Activity Description

Training involves showing users exactly how they will
use the new hardware and software in the system.

Examples of techniques
- one to one session
(3) Train user - classroom-style lectures
- web-based training - self-directed, self-paced
online instruction technique.

Training is important to help users to be ready for the

changes and adapt quickly to the new system.
53
4th phase : Implementation
Major Activity 4
Convert To The New System

Direct conversion :
● Abandoning the old and starting up the new
Parallel conversion :
● Old and new systems are operated side by
new ones proves to be reliable
Phased conversion :
● The new system is implemented gradually
over a period time
Pilot conversion :
● The new system is tried out in only one part
54
of the organization
4th phase : Implementation
Convert to the new system
Convert To The New System
Direct
OLD SYSTEM
Conversion
Parallel OLD SYSTEM
Conversion NEW SYSTEM

OLD SYSTEM NEW SYSTEM

Phased
OLD SYSTEM NEW SYSTEM
Conversion
OLD SYSTEM NEW SYSTEM

OLD SYSTEM NEW SYSTEM

Pilot
OLD SYSTEM NEW SYSTEM
Conversion
NEW SYSTEM
TIME 55
4th phase : Implementation
Convert to the new system

56
 4th phase : Implementation
Conversion 1

Conversion Description
- The users stop using the old system and begin the use
of the new system all at once / on a fixed date.
- Advantage : The fastest implementation technique and
(1) Direct
requires no transition costs.
conversion
- Disadvantage : Extremely risky and can disrupt
operations seriously if the new system does not work
correctly the first time.

57
 4th phase : Implementation
Conversion 2

Conversion Description
- The users run the old system alongside the new system
for a specified time and only stop the old system when the
new system functions as expected.
(2) Parallel
- Advantage : It is less risky as users can revert to the old
conversion
system if the new system has problems.
- Disadvantage : It is costly to operate two systems at the
same time.

58
 4th phase : Implementation
Conversion 3

Conversion Description

- Parts of the new system are phased in separately at

different times until the new system is fully implemented.
- Advantage : (i) It is less risky as the new system is
(3) Phased implemented part by part. (ii) Users will also have time to
conversion adapt better to the new system.
- Disadvantage : Slow implementation technique as it will
take some time before the new system is implemented as
a whole.

59
 4th phase : Implementation
Conversion 4

Conversion Description

- Only one location in the organization uses the new system,

so that it can be tested.
- After the pilot site approves the new system, other sites
convert using one of the other conversion strategies
- Advantage : It is less risky as the new system will be
(4) Pilot
implemented at one location only. Any problem found in the
conversion
new system will be fixed before implemented at all other
locations.
- Disadvantage : Slow implementation technique as it will
take some time before the new system is implemented at
all locations.

60
5th phase : Support and Security
(Maintenance) - Purpose

Provides ongoing assistance for an information system

and its users after the system is implemented

61
5th phase : Support and Security
(Maintenance)
3 Major Activity

3 Major Activities

1 2 3

Performed Monitor system Assess

maintenance performance System
activity Security

62
 5th phase : Support and Security
(Maintenance) - Major Activity 1
Major Activity Description
- To determine initial maintenance needs, the system
analysts meet with users to discover whether the
information system is performing according to the
users’ expectations.
(1) Perform
maintenance
- fixing errors and improving systems operations
activities
- corrective maintenance - process of identifying and
correcting errors in an IS
- adaptive maintenance - process of including new
features/capabilities in an IS

63
 5th phase : Support and Security
(Maintenance) - Major Activity 2
Major Activity Description
- determine whether the system is inefficient or
unstable at any point
(2) Monitor - Perform perfective maintenance (if any).
system - If this occurs, system analysts will investigate
performance solutions to make the information system more
efficient and reliable. This process is known as
perfective maintenance

64
 5th phase : Support and Security
(Maintenance) - Major Activity 3

Major Activity Description

- Responsible for physical security of an organization's property
and people and also is in charge of securing computing
(3) Assess resources
system security - Responsible by CSO – Chief Security Officers

65
 Comparison Between Detailed
Analysis And Detailed Design
Detailed analysis Detailed design
(in Analysis Phase) (in Design Phase)

called logical design called a physical design

it specifies hardware & software - the physical
systems analysts develop the proposed solution components required - for automated procedures.
without regard to any specific hardware or software. Activities
➔ include developing designs for the databases,
Activities : inputs, outputs & programs.
➔ study how the current system works
➔ determine the users’ wants, needs & Tools used :
requirements - Prototyping - is a working model of the proposed
➔ recommend a solution. system and involved in the design phase.
- DFD
- CASE tool - Computer - aided software engineering
Tools used :
(CASE) tools are designed to support one or more
- ERD activities of system development.It contain
- Class diagram diagrams to support both process and object
modeling
66
 Explain the steps of system development life
cycle (Planning, Analysis, Design,
Implementation and Support & Security).
1
Planning
Prioritize and Obtain approval
for project request or
5 business problem, Plan and
Support & Security schedule and develop a project
team. 2
Keep modify/new system
healthy and improve and Analysis
productive.
to gather information about
existing system in order to
4 3 determine the requirements
for enhanced system (modify
Implementation system ) or new system.
Design
Coding , then construct/ Define solution modify / new system
build and install modify/new (by design interface, input,output,
system, train user, test and form,build prototype).
convert to new/modify Describe how the enhances or modify or
system. new system will resolve the business
problem based on requirements and 67
decision made during analysis.
Summary of SDLC

Phase Activity

- Review project request

- Prioritize project request - based on their value to the organization
Planning
- Allocate resources
- Form project development team
- Conduct preliminary investigation
- Perform detailed analysis activities
Analysis - Study current system
- Determine user requirement
- Recommend solution
- Acquire hardware and software, if necessary
Design
- Develop details of system
- Develop programs and apps, if necessary
- Install and test new system
Implementation
- Train users
- Convert to the new system
- Perform maintenance activities
Support and
- Monitor system performance 68
Security
- Assess system security
 PSPM 2012/2013 - Question

State the most suitable phase during system development

life cycle (SDLC) in the following table.

Activity Phase
System prototyping
Monitor system performance
Create data flow diagram

69
 PSPM 2012/2013 - Answer

State the most suitable phase during system development

life cycle (SDLC) in the following table.

Activity Phase
System prototyping Design
Monitor system performance Support and Security
Create data flow diagram Design

70
 PSPM 2013/2014 - Question
Identify the phase in the System Development Life Cycle
based on the following conversation among the system
development team members.
Team Member Conversation Phase
“We’re conducting some preliminary investigations in
identifying the problem and later detailed analysis will be
produced”
“Many activities are involved. For instance, we are
developing the program and test it before delivering to the
users”
“We evaluate the system and make some recommendations
when necessary”
“In this phase, we are basically identifying key person and all
stakeholders of the system” 71
 PSPM 2013/2014 - Answer
Identify the phase in the System Development Life Cycle
based on the following conversation among the system
development team members.
Team Member Conversation Phase
“We’re conducting some preliminary investigations in Analysis
identifying the problem and later detailed analysis will be
produced”
“Many activities are involved. For instance, we are Implementation
developing the program and test it before delivering to the
users”
“We evaluate the system and make some recommendations Support and
when necessary” Security
“In this phase, we are basically identifying key person and Planning 72
all stakeholders of the system”
 PSPM 2014/2015 - Question

Identify the IT positions involved in the IS development

based on the roles and responsibilities given below :
Roles and responsibilities Positions
Designing and developing an information system. He
/ she is the users’ primary contact person
Converts the system design into the appropriate
programming language such as C++, C#, Java etc

73
 PSPM 2014/2015 - Answer

Identify the IT positions involved in the IS development

based on the roles and responsibilities given below :
Roles and responsibilities Positions
Designing and developing an information system. He System analyst
/ she is the users’ primary contact person
Converts the system design into the appropriate Programmer
programming language such as C++, C#, Java etc

74
 PSPM 2016/2017 - Question
Specify the appropriate phase of System Development Life Cycle
(SDLC) for the following tasks :
Tasks Phase of SDLC

Describe desired features and operation in detail including screen layout,

business roles, process diagram, pseudocodes and other documentations.
Make changes to initial software to ensure that the system is fully accepted
by the users.
Identify current technology that has been implemented by others and make
comparisons of the performance to select a suitable approach.
Propose a workable milestone as a guideline.
Create a prototype to facilitate user understanding of the proposed system
flow.
Identify and consider stakeholders’ requirements using customers’ interviews
and surveys.
Construct the actual programming code.
75
 PSPM 2016/2017 - Answer
Specify the appropriate phase of System Development Life Cycle (SDLC) for
the following tasks :
Tasks Phase of SDLC

Describe desired features and operation in detail including screen Design

layout, business roles, process diagram, pseudocodes and other
documentations.
Make changes to initial software to ensure that the system is fully Support and Security
accepted by the users.
Identify current technology that has been implemented by others and Analysis
make comparisons of the performance to select a suitable approach.
Propose a workable milestone as a guideline. Planning
Create a prototype to facilitate user understanding of the proposed Design
system flow.
Identify and consider stakeholders’ requirements using customers’ Analysis
interviews and surveys.
76
Construct the actual programming code. Implementation