FOUNDATION OF

INFORMATION SYSTEMS
 CONTENTS

● System Development Life Cycle (SDLC)

1. Planning
2. Analysis and Specifications
3. System Design
4. Implementation
5. Maintenance/Support
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

SDLC : is a conceptual model, which includes policies and procedures for developing
or altering systems throughout their life cycles.
SDLC is a systematic approach, which explicitly breaks down the work into phases
that are required to implement either new or modified Information System
 Planning

Maintenance Analysis
System
Development
Life Cycle
PHASES OF
SDLC
Implementation Design
 01
PLANNING
 Feasibility studies
Feasibility studies are undertaken under many circumstances

• to find out whether a company has enough money for a project,

• to find out whether the product being created will sell,
• or to see if there are enough human resources for the project.
 TYPES OF FEASIBILITY STUDIES

TECHNICAL ECONOMIC
Feasibility study Feasibility study

OPERATIONAL
Feasibility study
 TYPES OF FEASIBILITY STUDIES

Technical Feasibility Study

● The assessment focuses on the organization’s technical resources.
● It helps the organization determine if resources meet capacity and if the
technical team can convert ideas into working systems
● In certain examples especially when projects are in third world countries,
technology transfer between cultures and geographical areas should be
analyzed.
 TYPES OF FEASIBILITY STUDIES

Economic Feasibility Study

● Determines whether the required software is capable of generating
financial gains for an organization.
● it is essential to consider expenses made on purchases (such as
hardware purchase) and activities required to carry out software
development.
● In addition, it is necessary to consider the benefits that can be achieved
by developing the software.
 TYPES OF FEASIBILITY STUDIES
Operational Feasibility Study

Operational feasibility also performs the following tasks.

● Determines whether the problems anticipated in user requirements are of high priority.
● Determines whether the solution suggested by the software development team is acceptable.
● Determines whether the organization is satisfied by the alternative solutions proposed by the
software development team.
 02
ANALYSIS
 Requirements Determination

The purpose of the systems analysis phase is

to understand business requirement and
build a logical model of the new system.
 REQUIREMENTS DETERMINATION

● A requirement is a vital feature of a new system, which

may include processing, or capturing of data, controlling
the activities of business, producing information and
supporting the management.
● Requirements determination involves studying the
existing system and gathering details to find out what are
the requirements, how it works, and where improvements
should be made.
 REQUIREMENTS DETERMINATION

Requirements Investigation

● It is studying the current system and documenting its features

for further analysis.
● It is at the heart of system analysis where analyst
documenting and describing system features using fact-
finding techniques, prototyping, and computer assisted tools.
 REQUIREMENTS DETERMINATION

Requirements Specifications

● It includes the analysis of data, which determine the requirement

specification, description of features for new system, and specifying
what information requirements will be provided.
● It includes analysis of factual data, identification of essential
requirements, and selection of Requirement-fulfillment strategies.
 INFORMATION GATHERING TECHNIQUES

INTERVIEWING QUESTIONNAIRES
collects information from individuals by interviewing. Using with large number of persons
Unstructured Interview −question-answer session. Open-ended Questionnaires − can be easily and correctly
Structured Interview − standard questions in either close or open format. interpreted.
Closed-ended Questionnaires - systems analyst lists all
possible responses.
DOCUMENT ANALYSIS OBSERVATION
Noticing and observing the people, events, and objects.
Review of Records, Procedures, and Forms that
The analyst visits the organization to observe the
helps to seek insight into a system, which describes the current system
working of current system
capabilities, its operations, or activities.
 System Analyst
System Analysts are IT professionals who act as a
mediator between clients and technical team.

They are responsible for integrating business

requirements into technology and ensure smooth
functioning of the business operations.

.
 SYSTEM ANALYST

Roles

Analyze problems outlined by users and

potential users of data processing;

study existing systems and procedures and the

introduction of potential data processing
systems.
 SYSTEM ANALYST

Roles
Develop detailed data flow charts of existing
system, documenting the work process;
assist with the development of system objectives
and comprehensive plans to organize work
methodology;
establish controls to assure desired output in new
and modified applications.
 SYSTEM ANALYST

Roles
Provide technical support, assistance, and
information to users;
train users in system operations as necessary;
coordinate communication and activities with users
to review and analyze user problems and needs;
provide work direction to assigned programmers.
 SYSTEM ANALYST

Roles
Compile information and data and prepare
various reports related to computer systems
and functions; document system software and
hardware as necessary.

Maintain a variety of records, accounts, logs

and files related to systems; prepare and
purge records as necessary.
 SYSTEM ANALYST SKILLS

INTERPERSONAL SKILLS ANALYTICAL SKILLS

MANAGEMENT SKILLS TECHNICAL SKILLS

 Interpersonal Skills
• Interface with users and programmer.
• Facilitate groups and lead smaller teams.
• Managing expectations.
• Good understanding, communication, selling and
teaching abilities.
• Motivator having the confidence to solve queries.
 Analytical Skills
• System study and organizational knowledge
• Problem identification, problem analysis, and problem
solving
• Sound commonsense
• Ability to access trade-off
• Curiosity to learn about new organization
 Management Skills
• Understand users jargon and practices.
• Resource & project management.
• Change & risk management.
• Understand the management functions
thoroughly.
 Technical Skills

• Knowledge of computers and software.

• Keep abreast of modern development.
• Know of system design tools.
• Breadth knowledge about new technologies.
 03
DESIGN
 SYSTEM DESIGN

In the design phase the SDLC process continues to move

from the what questions of the analysis phase to the how .
This phase focuses on the solution domain, i.e. “how to
implement?”
Based on the user requirements and the detailed analysis of a
new system, the new system must be designed.
System designing is the most crucial phase in the
development of a system.
 ُTYPES OF SYSTEM DESIGN

Logical Design Physical Design

● Physical design relates to the actual input and output
● Logical design pertains to an abstract
processes of the system.
representation of the data flow, inputs,
● It focuses on how data is entered into a system,
and outputs of the system.
verified, processed, and displayed as output.
● It describes the inputs (sources), outputs
● It produces the working system by defining the design
(destinations), databases (data stores),
specification that specifies exactly what the candidate
procedures (data flows) all in a format
system does.
that meets the user requirements.
● It is concerned with user interface design, process
design, and data design.
 SYSTEM DESIGN
In the design stage:
● the programming language and the hardware and software platform are
decided.
● Data structure, control process, equipment source
● workload and limitation of the system
● Interface, documentation
● Network design
● Database design
● Architecture design
● training, procedures of using the system
● taking backups and staffing requirement are decided at this stage.
 SYSTEM DESIGN

Using Tools:
There are several tools and techniques used for
describing the system design of the system. These
tools and techniques are:
● Data flow diagram (ERD),
● Data dictionary,
● Structured English,
● Decision table and Decision tree.
 Conceptual Data Modeling

Entity Relationship Model

ENTITY − It specifies distinct real world items in an application.

For example: vendor, item, student, course, teachers, etc.
RELATIONSHIP −they are the meaningful dependencies between
entities. For example, vendor supplies items, teacher teaches
courses, then supplies and course are relationship.
ATTRIBUTES − It specifies the properties of relationships. For
example, vendor code, student name. Symbols used in E-R model
and their respective meanings
 04
IMPLEMENTATION
 Implementation
After having the user acceptance of the new system
developed, the implementation phase begins.
Implementation is the stage of a project during
which theory is turned into practice.

.
 SYSTEM IMPLEMENTATION

CODING TESTING

ACQUISITION AND
INSTALLATION OF
HARDWARE AND Conversion
SOFTWARE

Training Documentation
 Coding
The system design needs to be implemented to
make it a workable system.
This is also called the programming phase in which
the programmer converts the program specifications
into computer instructions, which we refer to as
programs.
 TESTING
● Before actually implementing the new system into operations,
a test run of the system is done removing all the bugs, if any.
● It is an important phase of a successful system.
● After codifying the whole programs of the system, a test plan
should be developed and run on a given set of test data.
● The output of the test run should match the expected results.
 TESTING
Program test
Program test: When the programs have been coded and compiled and brought to working
conditions, they must be individually tested with the prepared test data.
All verification and validation be checked and any undesirable happening must be noted
and debugged (error corrected).
 TESTING
System test
After carrying out the program test and errors removed, then system test is done
on actual data. the results or output of the system is analyzed.
It may be found that the outputs are not matching the expected output of the
system. In such case, the errors in the particular programs are identified and are
fixed for the expected output.
 ACQUISITION AND INSTALLATION OF HARDWARE AND SOFTWARE
● The hardware and the relevant software
required for running the system must be
made fully operational before
implementation.
● During this phase, all the programs of the
system are loaded onto the user’s
computer.
 CONVERSION
● The conversion is also one of the most critical and expensive
activities in the system development life cycle.
● The data from the old system needs to be converted to operate in
the new format of the new system.
● The database needs to be setup with security and recovery
procedures fully defined.
 TRAINING
After loading the system, training of the user starts. Main topics of
such type of training are:

● How to execute the package?

● How to enter the data?
● How to process the data (processing details)?
● How to take out the reports?
 DOCUMENTATION

Documentation of everything happened in the implementation phase.

Such as system coding, interface design, database, testing, conversion, and
training.
 05
MAINTENANCE
 MAINTENANCE
In this phase, periodic maintenance for the system will be carried out
to make sure that the system will not become obsolete.
This will include
replacing the old hardware,
evaluating system’s performance.
providing latest updates components to make sure it meets the right
standards and the latest technologies to face current security threats.
 Thanks !
Do you have any questions?