The Systems Analysis

and Design

 Chapter 1
 The Systems Development
Environment

Chapter 1 1
 Introduction
 System analysis and design deal with planning the
development of information systems.
 What a system should do and how the components
of the system should be implemented and work
together. System analysts solve business problems
through Analysing the requirements of information
systems.
 This course deals with the concepts, skills,
methodologies, techniques, tools, and perspectives
essential for systems analysts.
Chapter 1 2
 Chapter outline
 The key to success in business is the ability to
gather, organize, and interpret information.
 Systems analysis and design is a proven
methodology that helps both large and small
businesses obtain the rewards of utilizing
information to its full capacity.
 A systems analyst is a person in the organization
who most involved with systems analysis and
design.
Chapter 1 3
 Objectives of the chapter
After studying this chapter, you should be able to:
Define information systems analysis and design.

Discuss the modern approach to systems analysis and

design.
Describe the role of the systems analyst in information

systems development.
Describe the information systems development life

cycle (SDLC). List alternatives to the systems

development life cycle.
Chapter 1 4
 What Is Information Systems
Analysis and Design?
 The process of developing/creating and maintaining
an information system.
 Information systems analysis and design is a
method used by companies to create and maintain
information systems that perform basic business
functions.
 For example, keeping track of customer names and
addresses, processing orders, and paying
employees.

Chapter 1 5
 Cont.………….
 The main goal of systems analysis and
design is to improve organizational systems,
typically through applying software that can
help employees accomplish key business
tasks more easily and efficiently.
 As a systems analyst, you will be at the
center of developing this software.

Chapter 1 6
 Systems Analysis and
Design: Core Concepts
 Information systems are interrelated
components working together to collect, process,
store, and distribute information to support
decision making, coordination, control, analysis,
and visualization in an organization.
 A software that helps organize and analyze data.
So the purpose of an Information system is to turn
raw data into useful information that can be used
for decision making in an organization.
Chapter 1 7
 Conti…………
 System is a group of interrelated
procedures/components used for a business
function, with an identifiable boundary, working
together for some purpose.
 Application software is a software designed to
process data and support users in an organization.
 The goal of application software is to turn data
into information.

Chapter 1 8
 Types of IS
 Transaction processing systems
 Management information systems
 Decision support systems

Chapter 1 9
 Components of Information
systems
 The hardware and systems software on which the
application software runs.
 Documentation and training materials.
 The specific job roles associated with the overall system,
such as the people who run the computers and keep the
software operating.
 Controls, which are parts of the software written to help
prevent fraud and theft.
 The people who use the software in order to do their jobs.

Chapter 1 10
Chapter 1 11
 Software engineering process
 The software engineering process leads
to the creation of information systems.
 As shown in Figure below, proven
methodologies, techniques, and tools are
central to software engineering
processes.

Chapter 1 12
 Software Engineering
process

Chapter 1 13
 Methodologies
 Are a sequence of step-by-step approaches
that help develop your final product: the
information system.
 Methodologies is a standard process
followed in an organization to conduct all
the steps necessary to analyze, design,
implement, and maintain information
systems.
Chapter 1 14
 Techniques
 Techniques are processes that you, as an analyst, will
follow to help ensure that your work is well thought-out,
complete, and comprehensible to others on your project
team.
 Techniques provide support for a wide range of tasks,
including conducting interviews, planning and managing
the activities in a systems development project,
diagramming how the system will function, and designing
the reports, such as invoices, your system will generate
for its users to perform their jobs.

Chapter 1 15
 Tools
 Tools are computer programs, such as
computer-aided software engineering (CASE)
tools, that make it easy to use specific
techniques.
 These three elements— methodologies,
techniques, and tools—work together to form
an organizational approach to systems
analysis and design.
Chapter 1 16
Systems and Its parts
1) Components
2) Interrelated components
3) Boundary
4) Purpose
5) Environment
6) Interface
7) Input
8) Output
9) Constrain

17 Chapter 1
Chapter 1 18
 Important System Concepts
 Decomposition; is breaking the description of a
system into small parts
 Modularity; dividing a system into portions or
modules of equal size
 Coupling; the extent which subsystems depend on
each other
 Cohesion; the extent which subsystem performs a
single function.

Chapter 1 19
 A Modern Approach to
Systems Analysis and Design
 Today, systems development focuses on systems
integration. Systems integration allows hardware and
software from different vendors to work together in an
application.
 In a client/server environment, some of the software
runs on the server, a powerful computer designed to
allow many people access to software and data stored
on it, and some of the software runs on client machines.
Alternatively, organizations may purchase an enterprise-wide
system from companies.

Chapter 1 20
 Your Role in Systems
Development
 Although many people in organizations are involved
in systems analysis and design, the systems analyst
has the primary responsibility.
 The primary role of a systems analyst is to study the
problems and needs of an organization
 A systems analyst helps system users and other
business managers define their requirements for new
or enhanced information services. Systems analysts
are key to the systems development process.
Chapter 1 21
 Types of skills required
 Analytical: Analytical skills enable you to
understand the organization and its functions, to
identify opportunities and problems, and to
analyze and solve problems.
 Technical: Technical skills help you understand
the potential and the limitations of information
technology.

Chapter 1 22
 Cont’d……
 Managerial: Management skills help you manage
projects, resources, risk, and change.
 Interpersonal: Interpersonal skills help you work
with end users as well as with other analysts and
programmers.

Chapter 1 23
 Systems Development Life
Cycle (SDLC)
 Traditional methodology used to develop,
maintain, and replace information systems.
 Phases in SDLC:
 Planning
 Analysis
 Design
 Implementation
 Maintenance

24 Chapter 1
 Standard and Evolutionary
Views of SDLC

SDLC

FIGURE 1-3 Evolutionary model

FIGURE 1-2
The systems development life cycle

25 Chapter 1
 Systems Development Life
Cycle (SDLC) (Cont.)
 Planning – an organization’s total information
system needs are identified, analyzed, prioritized,
and arranged and in which a potential
information systems project is identified and an
argument for continuing or not continuing with
the project is presented.
 Analysis – system requirements are studied and
structured and alternative replacement systems
are proposed.

26 Chapter 1
 Systems Development Life
Cycle (SDLC) (Cont.)
 Design – a description of the recommended
solution is converted into logical and then
physical system specifications.
 Logical design – all functional features of the
system chosen for development in analysis
are described independently of any
computer platform.

27 Chapter 1
 Systems Development Life
Cycle (SDLC) (Cont.)
 Physical design – the logical specifications
of the system from logical design are
transformed into the technology-specific
details from which all programming and
system construction can be accomplished.

28 Chapter 1
 Systems Development Life
Cycle (SDLC) (Cont.)
 Implementation – the information system is
coded, tested, installed and supported in the
organization. Systems implementation activities
also include initial user support such as the
finalization of documentation, training programs,
and ongoing user assistance.
 Maintenance – an information system is
systematically repaired and improved.

29 Chapter 1
 Example of SDLC
 For example, a commercial product, such
as a Kaspersky antivirus or a Honda car,
follows a life cycle: It is created, tested,
and introduced to the market. Its sales
increase, peak, and decline. Finally, the
product is removed from the market and is
replaced by something else.

Chapter 1 30
 Alternative Approaches to
Development
 Prototyping, computer-aided software
engineering (CASE) tools, joint application
design (JAD), rapid application development
(RAD), and the use of Agile Methodologies
represent different approaches that
streamline and improve the systems analysis
and design process from different
perspectives.
Chapter 1 31
 Prototyping
 Designing and building a scaled-down but
working version of a desired system is known
as prototyping.
 A prototype can be developed with a CASE
tool, a software product that automates steps
in the systems development life cycle.

Chapter 1 32
Cont.…………

Chapter 1 33
 Computer-Aided Software
Engineering (CASE) Tools
 Diagramming tools enable graphical
representation.
 Computer displays and report
generators help prototype how
systems “look and feel”.

34 Chapter 1
 Computer-Aided Software
Engineering (CASE) Tools (Cont.)
 Analysis tools automatically check for
consistency in diagrams, forms, and
reports.
 A central repository provides
integrated storage of diagrams,
reports, and project management
specifications.

35 Chapter 1
 Computer-Aided Software
Engineering (CASE) Tools (Cont.)

 Documentation generators
standardize technical and user
documentation.
 Code generators enable automatic
generation of programs and
database code directly from design
documents, diagrams, forms, and
reports.

36 Chapter 1
CASE Tools (Cont.)

FIGURE 1-10
A class diagram from
IBM’s Rational Rose

(Source: IBM)

37 Chapter 1
 Joint Application Design

 A structured process in which users,

managers, and analysts work together for
several days in a series of intensive meetings
to specify or review system requirements.

Chapter 1 38
 Rapid Application Development
(RAD)
 Approach to completely decrease design and
implementation time
 Involves: extensive user involvement, prototyping,
JAD sessions, integrated CASE tools, and code
generators.
 RAD involves gaining user acceptance of the interface
and developing key system capabilities as quickly as
possible. RAD is widely used by consulting firms. It is
also used as an in-house methodology by firms such
as the Boeing Company.
39 Chapter 1
 Rapid Application
Development (RAD) (Cont.)

FIGURE 1-11
RAD life cycle

40 Chapter 1
 Agile Methodologies
 Motivated by recognition of software
development as fluid, unpredictable,
and dynamic
 Three key principles
 Adaptive rather than predictive
 Emphasize people rather than roles
 Self-adaptive processes

41 Chapter 1
The Agile Methodologies
group argues that software
development methodologies
adapted from engineering
generally do not fit with
real-world software
development.

42 Chapter 1
 When to use Agile
Methodologies
 If your project involves:
 Unpredictable or dynamic requirements
 Responsible and motivated developers
 Customers who understand the process
and will get involved

43 Chapter 1
 Summary
In this chapter you learned how to:
Define information systems analysis and design.

Describe the information Systems Development Life

Cycle (SDLC).
Explain Rapid Application Development (RAD),

prototyping, Computer Aided Software Engineering

(CASE), and JAD.
Describe agile methodologies

State role of systems analysis

44 Chapter 1
 End

Chapter 1 45