CP 212:

Systems Analysis and Design

Lecture One
 Course info.

• Course code: CP 212

• Course name: Systems Analysis and Design

Instructors
 Ms. Christina Muro-Lecturer, CSE department
Ms. Gloriana Monko-Ass Lecturer. CSE department

Systems Analysis and Design. Introduction to SAD 2

 Aim of the course

• To provide learners with the knowledge and

skills needed to undertake a system analysis
investigation by following a recognized
methodology.

Systems Analysis and Design. Introduction to SAD 3

 Grading system of the Course

1st and 2nd Tests 20%

Quizzes, Assignments, Discussion, Investigations, Designs

and Presentations  20%

Final Exam  60%

Systems Analysis and Design. Introduction to SAD

4
 Text book of the course

System Analysis and

Design,
Ninth Edition

Authors: Gary B. Shelly,

Thomas J.
Cashman and Harry J.
Rosenblatt ,

Publisher: SHELLY
CASHMAN SEWIES.

Systems Analysis and Design. Introduction to SAD 5

 Further reading book

Modern Systems Analysis

and Design 8th Edition
Authors: Jeffrey A. Hoffer ,
Joey F. George, Joseph S.
Valacich

Systems Analysis and Design. Introduction to SAD 6

 Learning OUTCOMES
 Explain what systems are and how they are developed
 Describe the phases of the systems development life cycle.
 Develop and evaluate system requirements.
 Work effectively in a team environment.
 Describe the role and responsibilities of the systems analyst
in the development and management of systems.
 Explain the need for and value of a formalized step-by-step
approach to the analysis, design, and implementation of
computer information systems.

Systems Analysis and Design. Introduction to SAD 7

 Learning OUTCOMES
Use tools and techniques for process and data modeling.
Describe the role and responsibilities of the participants in
information systems development.
Develop a feasibility analysis of a proposed system.
Develop and deliver a Requirements Definition Proposal for a
new system in a well-structured business proposal.
Explain the common ways projects fail and how to avoid these
failures.
Implement various project management tools.
Systems Analysis and Design. Introduction to SAD 8
 Introduction to
Systems analysis
and design
System development methodologies
 Introduction

• Information Systems Analysis and Design

• Complex organizational process
• Used to develop and maintain computer-based
information systems
• Used by a team of business and systems professionals

Systems Analysis and Design. Introduction to SAD

10
 Introduction

An organizational approach to systems analysis and

design is driven by methodologies, techniques, and tools
Systems Analysis and Design. Introduction to SAD

11
 Introduction

• Application Software
• Computer software designed to support organizational
functions or processes
•Sources of Software
•Information technology services firm
• Packaged software producers
• Open source software
• In-house developers
Systems Analysis and Design. Introduction to SAD

12
 Introduction

• Systems Analyst
• Organizational role most responsible for analysis and
design of information systems

Systems Analysis and Design. Introduction to SAD 13

 Introduction

• System Development Methodology is a standard

process followed in an organization to conduct all
the steps necessary to analyze, design, implement,
and maintain information systems.

Systems Analysis and Design. Introduction to SAD

14
 Systems Development Life
Cycle (SDLC)
• Traditional methodology used to develop, maintain,
and replace information systems.
• Phases in SDLC:
• Planning
• Analysis
• Design
• Implementation
• Maintenance
Systems Analysis and Design. Introduction to SAD

15
The systems development life cycle
(SDLC)
• Is the process of understanding how an information system (IS) can
support business needs by designing a system, building it, and
delivering it to users
• The SDLC has a set of four fundamental phases:
• planning,
• analysis,
• design, and
• Implementation
Each phase is itself composed of a series of steps, which rely upon techniques
that produce deliverables (specific documents and files that provide understanding
about the project).
Systems Analysis and Design. Introduction to SAD 16
 Planning
• The planning phase is the fundamental process of understanding why
an information system should be built and determining how the project
team will go about building it. It has two steps:
1. Project initiation
• the system’s business value to the organization is identified: how will it lower
costs or increase revenues?
• to conduct a feasibility analysis. The feasibility analysis examines key aspects of
the proposed project:
• The idea’s technical feasibility (Can we build it?)
• The economic feasibility (Will it provide business value?)
• The organizational feasibility (If we build it, will it be used?)
• Decide weather or not the project should be undertaken

Systems Analysis and Design. Introduction to SAD 17

 Planning

2. Project management
• creates a work plan
• The deliverable for project
management is a project plan, which
describes how the project team will
go about developing the system
Systems Analysis and Design. Introduction to SAD 18
 Analysis
• The analysis phase answers the questions of who will use the system, what the
system will do, and where and when it will be used
• During this phase, the project team investigates any current system(s), identifies
improvement opportunities, and develops a concept for the new system
• This phase has three steps
1. An analysis strategy is developed to guide the project team’s efforts. Such a strategy usually includes an
analysis of the current system (called the as-is system) and its problems, and then ways to design a new
system (called the to-be system)
2. The next step is requirements gathering
• The system concept is then used as a basis to develop a set of business analysis models, which describe how the
business will operate if the new system is developed
• The set of models typically includes models that represent the data and processes necessary to support the
underlying business process.

3. The analyses, system concept, and models are combined into a document called the system
proposal(Software specification document)
Systems Analysis and Design. Introduction to SAD 19
 Design
• The design phase decides how the system will operate, in terms of the
hardware, software, and network infrastructure; the user interface, forms and
reports; and the specific programs, data- bases, and files that will be needed.
• The design phase has four steps:
1. The design strategy
• It clarifies whether the system will be developed by the company’s own programmers,
whether the system will be outsourced to another firm (usually a consulting firm), or whether
the company will buy an existing software package.
2. architecture design
• In most cases, the system will add or change the infrastructure that already exists in the
organization. The interface design specifies how the users will move through the system
(e.g., navigation methods such as menus and on-screen buttons) and the forms and reports
that the system will use.

Systems Analysis and Design. Introduction to SAD 20

 Design

3. The database and file specifications are developed

• These define exactly what data will be stored and where they will be
stored.
4. program design,
• which defines the programs that need to be written and exactly what each
program will do
• This collection of deliverables (architecture design, interface
design, database and file specifications, and program design) is the
system specification that is handed to the programming team for
implementation.
Systems Analysis and Design. Introduction to SAD 21
 Implementation

• This phase has three steps:

1. System construction
2. The system is installed.
• is the process by which the old system is
turned off and the new one is turned on
3. The analyst team establishes a support plan for
the system
Systems Analysis and Design. Introduction to SAD 22
 Processes and outcomes

Process Product
Planning Project Plan

Analysis System Proposal

Design System
Specification

Implementation New System and

Systems Analysis and Design. Introduction to SAD Maintenance Plan 23
 System Development
Methodology
• A methodology is a formalized approach to implementing
the SDLC (i.e., it is a list of steps and deliverables)
• There are many ways to categorize methodologies. One
way is by looking at whether they focus on business
processes or the data that support the business
• Process-centered methodology emphasizes process models as
the core of the system concept.
• Object oriented methodologies attempt to balance the focus
between process and data by incorporating both into one model.

Systems Analysis and Design. Introduction to SAD 24

 Category of systems
development methodologies
1. Waterfall Development
• One phase begins when another
completes, with little backtracking
and looping
• System requirements “locked in”
after being determined (can't change)
• Limited user involvement (only in
requirements phase)
• Too much focus on milestone
deadlines of SDLC phases to the
detriment of sound development
practices

Systems Analysis and Design. Introduction to SAD 25

 category of systems
development methodologies
2. Parallel Development
• attempts to address the
problem of long delays
between the analysis phase and
the delivery of the system
• it performs a general design
for the whole system and then
divides the project into a series
of distinct subprojects that can
be designed and implemented
in parallel
Systems Analysis and Design. Introduction to SAD 26
 category of systems
development methodologies
3. Rapid Application Development (RAD)
• attempt to address both weaknesses of structured
design methodologies by adjusting the SDLC
phases to get some part of the system developed
quickly and into the hands of the users
• Critical elements
• CASE tools
• JAD sessions
• Disadvantages:
• Difficulties in managing user expectations. Due
to the use of the tools and techniques that can
improve the speed and quality of systems
development, user expectations of what is
possible may dramatically change

Systems Analysis and Design. Introduction to SAD 27

 category of systems
development methodologies
4. Phased Development
• A phased
development–based
methodology breaks an
overall system into a
series of versions,
which are developed
sequentially.

Systems Analysis and Design. Introduction to SAD 28

 category of systems
development methodologies
5. Prototyping
• A prototyping-based methodology performs
the analysis, design, and implementation
phases concurrently, and all three phases are
performed repeatedly in a cycle until the
system is completed
• a ―quick-and-dirty‖ program that provides a
minimal amount of features.
• Advantage: Provides a system for the users to
interact with, even if it is not initially ready
for use.
• Disadvantage: Often the prototype undergoes
such significant changes that many initial
design decisions prove to be poor ones
Systems Analysis and Design. Introduction to SAD 29
 category of systems
development methodologies
6. Throwaway prototyping:
• Refers to the creation of a model
that will eventually be discarded
rather than becoming part of the
final delivered software. After
preliminary requirements gathering
is accomplished, a simple working
model of the system is constructed
to visually show the users what
their requirements may look like
when they are implemented into a
finished system. It is also a form of
rapid prototyping.
Systems Analysis and Design. Introduction to SAD 30
 category of systems
development methodologies
7. Agile Development
• These programming-centric methodologies have few
rules and practices, all of which are fairly easy to
follow. They focus on streamlining the SDLC by
eliminating much of the modeling and documentation
overhead and the time spent on those tasks. Instead,
projects emphasize simple, iterative application
development
• Extreme programming (XP) is founded on
four core values: communication, simplicity,
feedback, and courage. he methodology takes
its name from the idea that the beneficial
elements of traditional software engineering
practices are taken to "extreme" levels. As an
example, code reviews are considered a
beneficial practice; taken to the extreme, code
can be reviewed continuously

Systems Analysis and Design. Introduction to SAD 31

 Choosing Appropriate
Development Methodology
• With unclear requirements
• With unfamiliar technology
• Complex system
• A reliable system
• Requires short time schedule
• With schedule visibility

Systems Analysis and Design. Introduction to SAD 32

 Project team Skills and Roles:
Projects should consist of a variety of skilled individuals in order
for a system to be successful. Six major skill sets an analyst
should have include:
• Technical
• Business
• Analytical
• Interpersonal
• Management
• Ethical
Systems Analysis and Design. Introduction to SAD 33
 Categories of Analysts:

• Business Analyst
• Systems Analyst
• Infrastructure Analyst
• Change Management Analyst
• Project Manager

Systems Analysis and Design. Introduction to SAD 34

 The Main Roles of System
Analyst
• Business knowledge.
• Business problem solver.
• Help translate business requirements
into IT projects.

Systems Analysis and Design. Introduction to SAD 35

 Systems Development Tools and Techniques

• Computer-Aided Systems Engineering (CASE)

Tools

• Also called computer-aided software engineering, is

a technique that uses powerful software, called
CASE tools, to help systems analysts develop and
maintain information systems.
• Framework for systems development and support a
wide variety of design methodologies

Systems Analysis and Design. Introduction to SAD 36