System Development Life Cycle

Systems Development Participants

 Steering committee- The firms that take system strategy seriously establish a steering
committee, Usually includes the CEO, CFO, CIO, senior management from user areas and
computer services, and internal auditors
- Typical responsibilities: provide guidance, resolve conflicts, review projects and
assigning priorities, budget and allocate funds, review the status of projects,
determine whether projects should be continued
 Systems Professionals – analyze problems in current systems and formulate solutions
◦ systems analysts
◦ systems designers
Programmers

 Client – the person or organization contracting to have the work done

 User – the people who will have contact with the system
 Stakeholders: individuals who have an interest in the system but are not end users

Accountants must understand the entire systems development process, since they
are involved in several ways:
◦ Helping to specify their needs.
◦ As members of the development team.
◦ As auditors after the fact.
 Accountants also help keep the project on track by:
◦ Evaluating and measuring benefits.
◦ Measuring costs.
◦ Ensuring the project stays on schedule.
SDLC
The systems approach can be applied to the solution of many types of problems. When this
involves the development of information system solutions to business problems, it is called
information systems development or application development. Most computer-based
information systems are conceived, designed, and implemented using some form of systematic
development process. In this process, end users and information specialists design information
systems based on an analysis of the information requirements of an organization. Thus, a
major part of this process is known as systems analysis and design.

When the systems approach is applied to the development of information system solutions, a
multistep process or cycle emerges. This is frequently called the information systems
development cycle, also known as the systems development life cycle (SDLC).

 SDLC is the process of developing information systems through investigation, analysis,

design, implementation and maintenance.
The Different phases in system development life cycle are
1. System Investigation
2. System Analysis
3. System Design
4. System Development
5. System Implementation
6. System maintenance
 1. System Investigation
The first step in the systems development process is the systems investigation stage. This step
may involve consideration of proposals generated by an information systems planning
process. It is the way of handling the users request to change, improve or enhance an existing
system.
The preliminary investigation includes two stages
a) Problem Definition
b) Feasibility Study

a)Problem Definition:
 The first responsibility of Analyst is to prepare a written statement of the objectives and
scope of the problem
 Conducts interviews with user
 Writes brief description of understanding of the problem and reviews it with both groups
i.e. users/information analyst meeting.

b) Feasibility study:
Because the process of developing a major information system can be costly, the systems
investigation stage frequently requires a preliminary study called a feasibility study.
A feasibility study is a preliminary study which investigates the information needs of
prospective users and determines the resource requirements, cost, benefits, and feasibility
of a proposed project.

Steps of a feasibility study:

1. Gather information/data for a feasibility study.
2. Formalize a written report including the preliminary specifications and a developmental plan
for the proposed system.
3. Submit the report management for approval.
4. Begin system analysis (if management approves the recommendations of the feasibility
study).

The goal of feasibility studies is to:

1. Evaluate alternative systems
2. Propose the most feasible and desirable systems for development.
Feasibility of a system can be evaluated in terms of four major categories:
 Organizational Feasibility - focuses on how well a proposed information system supports
the objectives of the organization and its strategic plan for information systems.
 Economic Feasibility - focuses on whether the tangible costs and benefits of the proposed
system will exceed the costs of developing and operating it.
 Technical Feasibility - focuses on the reliable/capabilities of the hardware and software to
meet the needs of the proposed system, and whether they can be acquired or developed
in the required time.
 Operation Feasibility - focuses on the willingness and ability of the management, employees,
customers, suppliers, and others to operate, use, and support the proposed system.
 Legal feasibility – whether there are laws and regulations that may prevent or limit the
system development project.
 Schedule Feasibility- Focuses on whether the software development work is completed in
scheduled time.

2.System Analysis
Systems analysis is an in-depth study of end user information needs which produces functional
requirements that are used as the basis for the design of a new information system.

The objective of this phase is to determine

-What must be done to solve the problem?
 Understand the existing system.
 The information needs of the organization and the end users.
 The activities, resources, and products of any present information systems
 The information systems capabilities required to meet the information needs of end users.

Two tasks are involved

– Data gathering
– Data analysis
Data Gathering
A number of techniques can be used
 Interviews with users and managers
Structured interview – includes only questions that have been written out in advance
Unstructured interview – interviewer has a general goal but few, if any questions prepared
 Examining current business and systems documents and output
– may include current order documents, computer systems procedures and reports used by
operations and senior management
 Sending out questionnaires
 Observation of current procedures
– by spending time in various departments; a time and motion study can show where
procedures could be more efficient, or to detect bottlenecks
Data Analysis
 Data are collected from the available files, decision points and transactions handled by
current system
 Tools used in data analysis are Data Flow Diagram’s, ERD, Decision Tables, Decision
trees, written reports
After analysis a document is prepared by the analyst, which is called as ‘Software requirement
Specification(SRS) Document’. This document specifies in detail all the functionalities of the
proposed system (i.e. “What the system does?”). These requirements are used in the next
phase, which is the Systems Design phase.
Once the Analysis is completed, the analyst understands that WHAT is to be done?

3.System design
 System Design describes HOW the system will accomplish this objective? “Design” refers
to the technical specifications that will be applied in construction of a system.
 Systems design consists of design activities, which produce systems specifications
satisfying the functional requirements developed in the systems analysis stage. These
specifications are used as the basis for next phases of SDLC.

The systems design concept focuses on three major products or deliverables that should result
from the design stage. System design consists of three activities:
1. User Interface Design
2. Data Design
3. Process Design
User Interface Design:
User interface design focuses on supporting the interactions between end users and their
computer-based applications. Designers concentrate on:
 The design of attractive and efficient forms of user input and output, such as easy-to-use
Internet or intranet web pages
 Designing methods of converting human-readable documents to machine-readable
input, such as optical scanning of business forms.
 Design tips to keep in mind:
o Keep it simple
o Keep it clean
o Organize logically
User interface design is frequently a prototyping process, where working models or prototypes
of user interface methods are designed and modified with feedback from end users. User
interface design produces detailed specifications for information products such as:
1. Display screens
2. Interactive user/computer dialogues
3. Audio responses
4. Forms
5. Documents
6. Reports.
Data Design
The data design activity focuses on the design of the structure of databases and files to be used
by a proposed information system. Data design frequently produces a data dictionary, which
catalogues detailed descriptions of the:
1. Attributes or characteristics of the entities (objects, people, places, events) about which
the proposed information system needs to maintain information.
2. Relationships these entities have to each other.
3. Specific data elements (databases, files, records, etc.) that need to be maintained for
each entity tracked by the information system
4. Integrity rules that govern how each data element is specified and used in the
information system.
Process Design
The process design activity focuses on the design of software resources, that is, computer
programs and of procedures needed by the proposed information system. It concentrates on
developing detailed specifications for the program modules that will have to be purchased as
software packages or developed by custom programming. Process design produces:
1. Detailed program specifications and procedures needed to meet the user interface and
data design specifications that are developed.
2. Produces specifications that meet the functional control and performance requirements
developed in the analysis stage.
System Specifications
System specification focuses on defining the systems specifications required for the proposed
information system. Typically, it specifies:
1. Hardware resources (machines and media)
2. Software resources (programs and procedures)
3. Network resources (communications media and networks)
3. People resources (end users & information systems staff).
4. How resources will be used to convert data resources (stored in files and databases they
design) into information products (displays, responses, reports, and documents).
5.System development(coding and testing)
Coding
 After designing the input and output, the analyst begins developing the software
using a programming language.
 This is the phase when the programmers play their major role in development.
 They start designing of data structures and writing of programs as per documents
prepared during design phase.
This phase can be categorized into two sub-phases
 Database design
 Program design
Database design: Database design is the most important aspect of developing a new
system. As data is the basic component or raw material of any information system, it is
needed to be stored in an organized way. How data to be organized depends on the
requirement specifications, hardware configurations and the features of programming
language and DBMS used.
Program design; Program design is mainly concerned with writing of programs (coding),
editing, debugging and finally testing them.
Testing:
When the software is ready, it is sent to the testing department where Quality Analysts
test it thoroughly for different errors by forming various test cases. They either test the
software manually or using automated testing tools and ensure that each and every
component of the software works fine. Once the QA makes sure that the software is error-
free, it goes to the next stage, which is Implementation.

Using the test data following test runs are carried out
 Unit testing – verifies that individual program units work
◦ Perform testing with test data
 System testing – determines whether all program units work together as planned
 Volume testing – uses real data in large amounts
◦ Determines whether the system can handle a large volume of data
6. System Implementation
Once a proposed information system has been designed, it must be implemented. The systems
implementation stage involves:
 Hardware and software acquisition
 Software development
 Testing of programs and procedures
 Development of documentation
 Installation activities
 Education and training of end users and specialists who will operate the new system.
 Converting from the use of the present system to the operation of a new or improved
system.
-Four approaches in system conversion
o Direct conversion – the user simply stops using the old system and starts using
the new one
o Parallel conversion – the old and new systems are both used until users are
satisfied with the new system works
o Phased conversion – the system is implemented one part at a time
o Pilot conversion – the entire system is used by a designated set of users

7. System Maintenance
Systems maintenance is the final stage of the systems development cycle. It involves the
monitoring, evaluating, and modifying of a system to make desirable or necessary
improvements. This may include:
 Post implementation review process to ensure that the new system meets the
objectives established for it.
 Error detected in the development or use of the system is corrected.
 Later modifications to a system may also become necessary due to changes within the
business or the business environment.
Balanced score card
The balanced scorecard (BSC) is a management system that enables organizations to clarify their
vision and strategy and translate them into action.

It identifies four major where improvement can lead to business success. These are linked two each other,
improvement of one also leads to improvement of others (improvement in innovation and learn can lead to
improvement in internal business processes).

These four perspectives are as follows

1. Financial perspective
2. Customer satisfaction
3. Internal business perspective
4. Learning and innovation

Let see, each of them turn by turn.

1. Financial perspective.
This perspective reflects the performance of the other three areas. This is traditional used for
performance management purpose. Senior management takes strategic decisions based on
financial information presented to them. It includes performance measures such as profitability,
sales growth, ROI

2. Customer satisfaction.
Customers are increasingly being considered important aspect of the business performance. Lack of
customer satisfaction means reduced profitability in future. It includes performance measures such
as repeat business from customer, no of complaints.

3. Internal business perspective.

For customer satisfaction internal business processes needs to work properly. This means there is
formal procedures and processes for material handling, manufacturing and quality inspection. It
includes performance measures such as no of warranty claims, no of projects completed on time
and in budget, no of pieces reworked.

4. Learning and innovation.

It helps to improve internal business perspective. New products, markets and ideas are needed to
achieve competitive advantage and ensure business growth and survival. It includes performance
measures like no of new products vs existing products, no of employees received training, time to
market new product.
Double click to play the ppt slide