Slides adapted from

Jeffrey A. Hoffer, University of Dayton

Joey F. George, Florida State University
Joseph S. Valacich, Washington State University

Modern Systems Analysis and Design, 4/E, Pearson Prentice Hall, 2004
 ü Information Systems Analysis and Design
n Complex organizational process whereby
computer-based information systems are
developed and maintained
ü Application Software
n Computer software designed to support
organizational functions or processes
ü Systems Analyst
n Organizational role most responsible for analysis
and design of information systems

1-2 © R Gustas
1-3 © R Gustas
 ü 1950s: focus on efficient automation of existing
processes
ü 1960s: advent of 3GL, faster and more reliable
computers
ü 1970s: system development becomes more like an
engineering discipline
ü 1980s: major breakthrough with 4GL, CASE tools,
object oriented methods
ü 1990s: focus on system integration, GUI applications,
client/server platforms, Internet
ü The new century: Web application development,
wireless PDAs, component-based systems

1-4 © R Gustas
 ü Transaction Processing Systems (TPS)
n Automate handling of data about business activities
(transactions)
n Process orientation
ü Management Information Systems (MIS)
n Converts raw data from transaction processing system into
meaningful form
n Data orientation (e.g.: summaries of data)
ü Decision Support Systems (DSS)
n Designed to help decision makers
n Provides interactive environment for decision making
n Involves data warehouses, executive information systems (EIS)
n Database, model base, user dialogue

1-5 © R Gustas
 üSystem Development Methodology
n Standard process followed in an
organization
n Consists of:
w Analysis
w Design
w Implementation
w Maintenance

1-6 © R Gustas
 ü Traditional methodology for developing,
maintaining, and replacing information
systems
ü Phases in SDLC:
n Planning
n Analysis
n Design
n Implementation
n Maintenance

1-7 © R Gustas
1-8 © R Gustas
 Identify, analyze,
prioritize, and
arrange IS needs

1-9 © R Gustas
 Study and
structure system
requirements

1-10 © R Gustas
 Logical design:
Convert functional features
recommended described
solution to system independently of
computer platform
specifications

Physical design:
logical
specifications
transformed to
technology-
specific details

1-11 © R Gustas
 Code, test, install,
and support the
information system

1-12 © R Gustas
 Systematically
repair and improve
the information
system

1-13 © R Gustas
 Current practice combines analysis, design, and implementation
into a single iterative and parallel process of activities
1-14 © R Gustas
 One phase begins
when another
completes, little
backtracking and
looping

1-15 © R Gustas
 ü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 (harm)
of sound development practices

1-16 © R Gustas
 üPrototyping
üCASE tools
üJoint Application Design (JAD)
üRapid Application Development (RAD)
üAgile Methodologies
üeXtreme Programming

1-17 © R Gustas
Iterative development process:
wRequirements quickly converted to a working system
wSystem is continually revised
wClose collaboration between users and analysts

1-18 © R Gustas
 üComputer-Aided Software Engineering
üSoftware tools providing automated
support for systems development
üProject dictionary/workbook: system
description and specifications
üDiagramming tools
üExample products: Oracle Designer,
Rational Rose

1-19 © R Gustas
 üStructured process involving users,
analysts, and managers
üSeveral-day intensive workgroup
sessions
üPurpose: to specify or review system
requirements

1-20 © R Gustas
ü Methodology to decrease design and implementation time
ü Involves: prototyping, JAD, CASE tools, and code
generators

1-21 © R Gustas
 üMotivated by recognition of software
development as fluid, unpredictable,
and dynamic
üThree key principles
n Adaptive rather than predictive
n Emphasize people rather than roles
n Self-adaptive processes

1-22 © R Gustas
 üShort, incremental development cycles
üAutomated tests
üTwo-person programming teams
üCoding and testing operate together
üAdvantages:
n Communication between developers
n High level of productivity
n High-quality code

1-23 © R Gustas
 ü Based on objects rather than data or
processes
ü Object: a structure encapsulating attributes
and behaviors of a real-world entity
ü Object class: a logical grouping of objects
sharing the same attributes and behaviors
ü Inheritance: hierarchical arrangement of
classes enable subclasses to inherit
properties of superclasses

1-24 © R Gustas
 Rational Unified Process (RUP) involves an iterative,
incremental approach to systems development

1-25 © R Gustas
 ü In this chapter you learned how to:
ü Define information systems analysis and design.
ü Describe the different types of information
systems.
ü Describe the information Systems Development
Life Cycle (SDLC).
ü Explain Rapid Application Development (RAD),
prototyping, Joint Application Development (JAD),
and Computer Aided Software Engineering
(CASE).
ü Describe agile methodologies and eXtreme
programming.
ü Explain Object Oriented Analysis and Design and
the Rational Unified Process (RUP).
1-26 © R Gustas