2 of 76

Learning Outcome

Identify 5 steps of system development life cycle based on activities in SDLC. (Planning, Analysis, Design, Implementation, Support & Security) - L
Explain the steps of system development life cycle (Planning, Analysis, Design, Implementation and Support & Security). - T

3 of 76

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, data, people and procedures that work together to produce information

System development is a set of activities used to build an information system

4 of 76

Why do we need 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

What Initiates a System Development Project?

5 of 76

System Development Guidelines

Group activities into phases

2.Involves users

3.Define standards

Users include anyone for whom the system is built in. e.g : Customers, employees, students, data entry specialist

Standards are sets of rules and procedures an organization expects employees to accept and follow

6 of 76

Who participates in System Development?

7 of 76

Groups of people that participate in system development

Steering committee : a group of people that makes decisions in an organization, usually includes vice presidents, managers, non-management users and IT personnel.

Project development team : a group of people that consists of users, the system analyst and other IT professionals.

Non Technical user and IT professionals :Database analyst, database administrators, web developers, software developers, vendors and the steering committee.

8 of 76

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 of 76

Phases in SDLC

SDLC

1.PLANNING

2. ANALYSIS

3. DESIGN

4. IMPLEMENTATION

5. SUPPORT & SECURITY

10 of 76

Ongoing Activities

Project Management

Documentation

Data and Information Gathering Techniques (in Analysis phase)

11 of 76

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

12 of 76

Project Management tools

13 of 76

Project Management tools

14 of 76

Project Management tools

15 of 76

Feasibility Assessment

Feasibility is a measure of how suitable the development of a system will be to the organization

Operational feasibility - measures how well the proposed information system work

Schedule feasibility - measures whether the established deadlines for the project are reasonable

Technical feasibility - measures whether the organization has or can obtain the computing resources, software services and qualified people needed to develop, deliver and support the proposed information system

Economic feasibility / cost feasibility - measures whether the lifetime benefits of the proposed information system will be greater than its lifetime course

16 of 76

Feasibility Study

17 of 76

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

18 of 76

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

19 of 76

SDLC Deliverables

Deliverables are the tangible outputs produced in each phase of the System Development Life Cycle (SDLC)

20 of 76

Example of deliverables for each phase of SDLC

Cost estimation
Approved feasibility study

Planning

Analysis of existing system
Analysis of intended

system

Preliminary investigation report/result

Analysis

Graphical user interface
Functional requirement
Specification

of the modified system

Design

Deployment of software
Code/

documentation

Training/

Procedure/

Support

Implementation

New or

modified

system

Support and Security

21 of 76

Learning Outcome

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

22 of 76

1st Phase : Planning

Purpose

To identify the potential project and to allocated required resources

23 of 76

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

24 of 76

1st Phase : Planning

4 Major Activity

Steering Committee

Receive the project request

Consists of :

i. Managers

ii. IT Personnel

iii. Vice president

iv. Non management users

4 Major Activities

Review and approve the project request

Prioritize the project request

Allocate resource

Form a project development team

25 of 76

1st Phase : Planning

4 Major Activity

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

26 of 76

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

27 of 76

2nd Phase : Analysis

Purpose

To determine the exact nature of the problem or improvement to be made and decide whether it is worth pursuing.

28 of 76

2nd Phase : Analysis

2 Major Activity

2 Major Activities

Conduct preliminary investigation

Perform detailed analysis

System Analyst

29 of 76

2nd Phase : Analysis

Major Activity 1

Major Activity	Description
(1) Conduct a preliminary investigation (Sometimes called the feasibility study)	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 improvement & decide whether it is worth pursuing. Interview the user who submitted the project request and others users. May use other data gathering techniques such as reviewing existing documentation. Upon completion of the preliminary investigation, the systems analyst writes the feasibility report to present the team’s findings to the 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.

30 of 76

2nd Phase : Analysis

Major Activity 2

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

31 of 76

2nd Phase : Analysis

Method Used

Method used (Refer Ongoing Activity) :

Data and Information Gathering Techniques

Interviews.
Questionnaires.
Observations.
Review Documents and records.
Surveys
JAD Session

Feasibility Assessment

(Technical, Operational, Schedule, Economical)

System Analyst

32 of 76

2nd Phase : Analysis

The System Proposal

Written document. Use to convey all the feasibility of each alternatives solution and recommend the most feasible solution for the project

System Analyst

Steering committee will decide whether to ….

presents a system proposal to steering committee for an approval.

Modify existing system

Buy retail software

Build custom software

Outsource IT needs to an outside firm

33 of 76

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.

34 of 76

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.

35 of 76

3rd phase : Design

2 Major Activity

2 Major Activities

Acquiring necessary hardware and software

Develop details of new or modified information system

Identify technical specification

Soliciting vendor proposal

Test and evaluate vendor proposal

Make a decision

Obtaining additional hardware or software that meets organization’s needs by System Analyst

36 of 76

3rd phase : Design

2 Major Activity

Acquiring necessary

hardware and software

Database Design

Input Output Design

Develop details of new or modified information system

Program Design

2 Major Activities

37 of 76

3rd phase : Design

Major Activity

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

38 of 76

3rd phase : Design

Major Activity 1

Database Design

Input Output Design

Program Design

39 of 76

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)

40 of 76

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.

41 of 76

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.

42 of 76

3rd phase : Design

Method Used - Prototype

43 of 76

3rd phase : Design

Method Used - Used Case Diagram

44 of 76

3rd phase : Design

Method Used - Data Flow Diagram

45 of 76

3rd phase : Design

Method Used - Data Flow Diagram

46 of 76

4th phase : Implementation

Purpose

To construct, or build the new or modified system and then deliver it to the users

47 of 76

4th phase : Implementation

4 Major Activity

Develop

Programs and apps if necessary

Install and test the new system

Train User

1 2 3

Convert to the new system

4 Major Activities

48 of 76

4th phase : Implementation

Major Activity 1

Develop Programs and Apps if necessary

Programmers write / modify the system following the program development life cycle.

49 of 76

4th phase : Implementation

Major Activity 1

Major Activity	Description
(1) Develop programs and apps if necessary	Involves six steps: Analyze the requirements (IPO analysis) Design the solution (algorithm) Validate the design (test the algorithm) Implement the design (write program) Test the solution (run program) Document the solution (prepare documentation)

50 of 76

4th phase : Implementation

Major Activity 2

Install And Test New System

The system analyst should install and test required new hardware and software because :

To avoid error in the system after it is delivered to the users

To make sure that all the programs work together in the system

51 of 76

4th phase : Implementation

Major Activity 2

4 Test Performed

Install And Test New System

Unit test

Verifies that each individual program or object works by itself

Systems test

Verifies that all programs in an application work together properly

Integration test

Verifies that an application works with other applications

Acceptance test

Checks the new system to ensure that it works with actual data

52 of 76

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

53 of 76

4th phase : Implementation

Major Activity 3

Major Activity	Description
(3) Train user	Training involves showing users exactly how they will use the new hardware and software in the system. Examples of techniques one to one session 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.

54 of 76

4th phase : Implementation

Major Activity 4

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 of the organization

Convert To The New System

55 of 76

4th phase : Implementation

Convert to the new system

OLD SYSTEM

NEW SYSTEM

OLD SYSTEM			NEW SYSTEM
OLD SYSTEM		NEW SYSTEM
OLD SYSTEM	NEW SYSTEM

OLD SYSTEM	NEW SYSTEM
OLD SYSTEM	NEW SYSTEM
NEW SYSTEM

Direct Conversion

Parallel

Conversion

Phased Conversion

Pilot Conversion

Convert To The New System

TIME

56 of 76

4th phase : Implementation

Convert to the new system

57 of 76

4th phase : Implementation

Conversion 1

Conversion	Description
(1) Direct conversion	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 requires no transition costs. Disadvantage : Extremely risky and can disrupt operations seriously if the new system does not work correctly the first time.

58 of 76

4th phase : Implementation

Conversion 2

Conversion	Description
(2) Parallel conversion	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. Advantage : It is less risky as users can revert to the old system if the new system has problems. Disadvantage : It is costly to operate two systems at the same time.

59 of 76

4th phase : Implementation

Conversion 3

Conversion	Description
(3) Phased conversion	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 implemented part by part. (ii) Users will also have time to 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.

60 of 76

4th phase : Implementation

Conversion 4

Conversion	Description
(4) Pilot conversion	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 implemented at one location only. Any problem found in the 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.

61 of 76

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

Provides ongoing assistance for an information system and its users after the system is implemented

62 of 76

5th phase : Support and Security (Maintenance)

3 Major Activity

Performed maintenance activity

Monitor system performance

Assess System Security

3 Major Activities

63 of 76

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

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

64 of 76

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

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

65 of 76

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

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

66 of 76

Comparison Between Detailed Analysis And Detailed Design

called logical design

systems analysts develop the proposed solution without regard to any specific hardware or software.

Activities :

study how the current system works
determine the users’ wants, needs & requirements
recommend a solution.

Tools used :

ERD
Class diagram

Detailed analysis

(in Analysis Phase)

Detailed design

(in Design Phase)

called a physical design

it specifies hardware & software - the physical components required - for automated procedures.

Activities

include developing designs for the databases, inputs, outputs & programs.

Tools used :

Prototyping - is a working model of the proposed system and involved in the design phase.
DFD
CASE tool - Computer - aided software engineering (CASE) tools are designed to support one or more activities of system development.It contain diagrams to support both process and object modeling

67 of 76

Explain the steps of system development life cycle (Planning, Analysis, Design, Implementation and Support & Security).

Planning

Support & Security

Design

Implementation

Analysis

Prioritize and Obtain approval for project request or business problem, Plan and schedule and develop a project team.

to gather information about existing system in order to determine the requirements for enhanced system (modify system ) or new system.

Define solution modify / new system (by design interface, input,output, form,build prototype).

Describe how the enhances or modify or new system will resolve the business problem based on requirements and decision made during analysis.

Coding , then construct/ build and install modify/new system, train user, test and convert to new/modify system.

Keep modify/new system healthy and improve and productive.

68 of 76

Summary of SDLC

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

69 of 76

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

70 of 76

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

71 of 76

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”

72 of 76

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 identifying the problem and later detailed analysis will be produced”	Analysis
“Many activities are involved. For instance, we are developing the program and test it before delivering to the users”	Implementation
“We evaluate the system and make some recommendations when necessary”	Support and Security
“In this phase, we are basically identifying key person and all stakeholders of the system”	Planning

73 of 76

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

74 of 76

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 / she is the users’ primary contact person	System analyst
Converts the system design into the appropriate programming language such as C++, C#, Java etc	Programmer

75 of 76

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.

76 of 76

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