Chapter One

System Analysis and Design

Chapter 1. System Development:
Target Group 2nd Year IS students
 OUTLINE
Introduction to Information System development.
System development methodologies, / Software life cycle
and process model and phase
Problem Identification, Selection and Planning Phase:
• Problem identification
• problem definition: symptoms vs problems
• prioritizing problems
• project initiation and planning
• planning tools and techniques
• Gantt& PERT
The human side of systems
 Introduction
Systems Analysis and Design is the process of examining a
business situation with the intent of improving it through better
procedures and methods. It must ensure that the proposed
information system meets user needs, can be delivered on time, and
can be updated inexpensively.

The process of system analysis commences with system study that is

conducted to learn the details of the current business situation,
and to suggest alternative design strategies along with the costs
and benefits analysis. It is conducted by the systems analyst.
 What is system?
A system is an organized collection of parts (or subsystems) that
are highly integrated to accomplish an overall goal.
The system has various inputs, which go through certain processes
to produce certain outputs, which together, accomplish the overall
desired goal for the system. So a system is usually made up of
many smaller systems, or subsystems.
For example, an organization is made up of many administrative
and management functions, products, services, groups and
individuals.
If one part of the system is changed, the nature of the overall
system is changed, as well.
 Con..
System Analysis is concerned on the understanding the details of
an existing system or a proposed one and then deciding whether
the proposed system is desirable or not and whether the existing
system needs improvements.
Thus, system analysis is the process of investigating a system,
identifying problems, and using the information to recommend
improvements to the system.
Analysis is the collection of notations, methodologies and tools
used to gather details and analyse a problem situation for
recommending improvements to information system
Analysis specifies what the system should do. Design states how to
accomplish the objective.
 Con..
System design is the process of planning a new business system or one to replace or
complement an existing system.

Design is the process of planning a new business system or one to replace or

complement an existing system.

The process of systems analysis and design tells us how to:

 Build information systems

 Analyse information system needs

 Design computer based information systems

 Solve systems problems in organizations

Systems Analyst

A Systems Analyst is the person responsible for researching, planning and

recommending software and systems choices to meet an organization's business
requirements.
 Information System development.

Information systems analysis and design is a complex,

challenging, and stimulating organizational process that
a team of business and systems professionals uses to
develop and maintain computer-based information
systems.

During the information systems analysis and design,

emphasis is placed on organization and the business
processes.
 ……… Information System development.

Organizations change with time. So, the IS’s are built

and rebuilt for organizational benefits. Therefore,
information systems analysis and design is an
organizational improvement process.

Information systems analysis and design is thus based on

the understanding of the organizations’ objectives,
structure, and processes, and the knowledge of
technology.
 ……… Information System development.

Information systems analysis and design is a complex,

challenging, and stimulating organizational process that
a team of business and systems professionals uses to
develop and maintain computer-based information
systems.

During the information systems analysis and design,

emphasis is placed on organization and the business
processes.
System development methodologies, / Software life cycle and process
model and phase
A system development life cycle or SDLC is essentially a project
management model. It defines different stages that are necessary to bring
a project from its initial idea or conception all the way to deployment and
later maintenance.
There are seven primary stages of the modern system development life
cycle.
1. Planning
2. Systems Analysis and Requirements
3. Systems Design
4. Development
5. Integration and Testing
6. Implementation
7. Operations and Maintenance
 1. Planning
This is the first phase in the systems development process. It
identifies whether or not there is the need for a new system to
achieve a business"s strategic objectives. This is a preliminary
plan (or a feasibility study) for a company"s business initiative to
acquire the resources to build on an infrastructure to modify or
improve a service.

The purpose of this step is to find out the scope of the problem
and determine solutions. Resources, costs, time, benefits and other
items should be considered at this stage.
 2. Systems Analysis and Requirements
The second phase is where businesses will work on the source of their
problem or the need for a change. In the event of a problem, possible solutions
are submitted and analysed to identify the best fit for the ultimate goal(s) of
the project.

It is also where system analysis takes place—or analysing the needs of the end
users to ensure the new system can meet their expectations.

Systems analysis is vital in determining what a business’s needs are, as well as

how they can be met, who will be responsible for individual pieces of the
project, and what sort of timeline should be expected.

There are several tools businesses can use that are specific to the second phase.
Requirements gathering

Structured analysis
 3. Systems Design
The third phase describes, in detail, the necessary specifications,
features and operations that will satisfy the functional
requirements of the proposed system which will be in place. This
is the step for end users to discuss and determine their specific
business information needs for the proposed system.

During this phase they will consider the essential components

(hardware and/or software) structure (networking capabilities),
processing and procedures for the system to accomplish its
objectives.
 4. Development

The fourth phase is when the real work begins—in particular,

when a programmer, network engineer and/or database developer
are brought on to do the major work on the project.

This work includes using a flow chart to ensure that the process
of the system is properly organized. The development phase
marks the end of the initial section of the process.

Additionally, this phase signifies the start of production. The

development stage is also characterized by instillation and
change. Focusing on training can be a huge benefit during this
phase.
 5. Integration and Testing
The fifth phase involves systems integration and system testing
(of programs and procedures)—normally carried out by a Quality
Assurance (QA) professional—to determine if the proposed design
meets the initial set of business goals.

Testing may be repeated, specifically to check for errors, bugs

and interoperability. This testing will be performed until the end
user finds it acceptable.

Another part of this phase is verification and validation, both of

which will help ensure the program"s successful completion.
 6. Implementation
The sixth phase is when the majority of the code for the program is
written. Additionally, this phase involves the actual installation of
the newly-developed system.

This step puts the project into production by moving the data and
components from the old system and placing them in the new system
via a direct cutover.

While this can be a risky (and complicated) move, the cutover

typically happens during off-peak hours, thus minimizing the risk.

Both system analysts and end-users should now see the realization
of the project that has implemented changes.
 7. Operations and Maintenance
The seventh and final phase involves maintenance and regular required
updates. This step is when end users can fine-tune the system, if they
wish, to boost performance, add new capabilities or meet additional user
requirements.
Benefits of SDLC
SDLC provides a number of advantages to development teams that
implement it correctly.
 ‍Clear Goal Descriptions
 Proper Testing Before Installation
 Clear Stage Progression
 Member Flexibility
 Perfection Is Achievable
 No One Member Makes or Breaks the Project
Systems analysts will often be expected to:
Gather facts and information

Make command decisions about which bugs to prioritize or what features to

cut

Suggest alternative solutions

Draw specifications that can be easily understood by both users and

programmers

Implement logical systems while keeping modularity for later integration

Be able to evaluate and modify the resulting system as is required by project

goals

Help to plan out the requirements and goals of the project by defining and
understanding user requirements
 Basic SDLC Methodologies
Six more specific methodologies can be leveraged to achieve
specific results or provide the greater SDLC with different
attributes.
1. Waterfall Model
The waterfall model is the oldest of all SDLC methodologies. It’s
linear and straightforward and requires development teams to finish
one phase of the project completely before moving on to the next.
Each stage has a separate project plan and takes information from
the previous stage to avoid similar issues (if encountered).
Cont..
 Cont..
2. Iterative Model
The iterative model focuses on repetition and
repeat testing.
New versions of a software project are produced
at the end of each phase to catch potential errors
and allow developers to constantly improve the
end product by the time it is ready for market.
One of the upsides to this model is that developers
can create a working version of the project
relatively early in their development life cycle, so
implement the changes are often less expensive.‍
Cont..
 Cont..
3. Spiral Model
Spiral models are flexible compared to other
methodologies. Projects pass through four
main phases again and again in a
metaphorically spiral motion.
It’s advantageous for large projects since
development teams can create very customized
products and incorporate any received
feedback relatively early in the life cycle.
Cont..
 Cont..
4. V-Model
The V-model (which is short for verification and validation) is
quite similar to the waterfall model. A testing phase is incorporated
into each development stage to catch potential bugs and defects.
It’s incredibly disciplined and requires a rigorous timeline.
5. Big Bang Model
Cont..
The Big Bang model is incredibly flexible and doesn’t follow a
rigorous process or procedure. It even leaves detailed planning
behind.
It’s mostly used to develop broad ideas when the customer or
client isn’t sure what they want. Developers simply start the
project with money and resources.
 Cont..
6. Agile Model
The agile model is relatively well-known, particularly in the
software development industry.
The agile methodology prioritizes fast and ongoing release cycles,
utilizing small but incremental changes between releases. This
results in more iterations and many more tests compared to other
models.
Theoretically, this model helps teams to address small issues as they
arise rather than missing them until later, more complex stages of a
project.
…cont
 Cont…
Gantt& PERT
 A Gantt chart is a bar chart with the x-axis and y-axis
representing tasks in a timeline.
 A PERT chart is a flow chart or network diagram that
displays project tasks in boxes and links them with
arrows that outline dependencies