Course outline
Information Systems
Development
Foundations for systems development
The systems development environment
The origins of software
Managing the information systems project
Planning
Identifying and selecting systems development projects
Initiating and planning systems development projects
Analysis
Chapter 1
The Systems Development
Environment
Design
Dr. Annabella Habinka Ejiri
annabinka@must.ac.ug
annabinka@yahoo.co.uk
+256772571444
2005 by Prentice Hall
1-3
2005 by Prentice Hall
Introduction
Designing databases
Designing forms and reports
Designing interfaces and dialogues
Finalizing design specifications
Designing distributed and internet systems
Implementation and maintenance
System implementation
Maintaining information systems
1-2
2005 by Prentice Hall
Reading list
Systems Analysis and Design, Donald Yeates (2004)
Object Oriented Systems analysis and Design, Simon
Bennett (1999)
Systems analysis and design, Donald Yeates, Tony
Wakefield (2004)
Modern systems analysis and design, Jeffrey
A.Hoffer, Joey F.George, Joseph S.Valacich (2008)
Essentials of systems analysis and design , Jeffrey A
Hoffer, Joey F.George, Joseph S Valacich (2009)
Systems analysis and design methods, Jeffrey L
Whitten, Lonnie D Bentley (2007)
Determining systems requirements
Structuring systems process requirements
Structuring systems logical requirements
Structuring systems data requirements
Learning Objectives
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-4
2005 by Prentice Hall
Roles of the systems analyst
Information Systems Analysis and Design
Complex organizational process whereby computer-based
information systems are developed and maintained
In System Analysis more emphasis is given to 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.
Study problems and needs of an organization
Determine best approach to improving
organization through use of:
Application Software
Computer software designed to support organizational
functions or processes
Help system users and managers define their
requirements for new or enhanced systems
Systems Analyst
1-5
People
Methods
Information technology
Organizational role most responsible for analysis and design
of information systems
2005 by Prentice Hall
1-6
2005 by Prentice Hall
Skills of a Successful Systems
Analyst
Cont
Assess options for system
implementation
Analytical
In-house development
Outsourced development
Outsourced development and operation
Commercial application
Ability to see organizations and information
systems as systems
Technical
For in-house projects, work on a team
of analysts and developers
1-7
2005 by Prentice Hall
Understanding of organizations
Problem-solving skills
System thinking
1-8
Understanding of potential and limitations
of technology
2005 by Prentice Hall
Cont
Introduction (cont.)
Managerial
Ability to manage projects, resources, risk
and change
Interpersonal
1-9
Effective written and oral communication
skills
2005 by Prentice Hall
A Modern Approach to Systems
Analysis and Design
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 applications
1-11
2005 by Prentice Hall
1-10
2005 by Prentice Hall
Types of Information Systems
and Systems Development
Transaction Processing Systems (TPS)
Automate handling of data about business activities
(transactions)
Process orientation
Management Information Systems (MIS)
Converts raw data from transaction processing system into
meaningful form
Data orientation
Decision Support Systems (DSS)
1-12
Designed to help decision makers
Provides interactive environment for decision making
Involves data warehouses, executive information systems (EIS)
Database, model base, user dialogue
2005 by Prentice Hall
Developing Information
Systems and the SDLC
Types of Information Systems
and Systems Development (cont.)
System Development Methodology
Standard process followed in an
organization
Consists of:
Analysis
Design
Implementation
Maintenance
1-13
2005 by Prentice Hall
Systems Development Life
Cycle (SDLC)
1-14
2005 by Prentice Hall
Standard and Evolutionary Views
of SDLC
Traditional methodology for developing,
maintaining, and replacing information
systems
Phases in SDLC:
Planning
Analysis
Design
Implementation
Maintenance
1-15
2005 by Prentice Hall
1-16
SDLC Planning Phase
Identify, analyze,
prioritize, and
arrange IS needs
1-17
2005 by Prentice Hall
SDLC Analysis Phase
Study and
structure system
requirements
2005 by Prentice Hall
1-18
2005 by Prentice Hall
SDLC Design Phase
Logical design:
functional features
described
independently of
computer platform
Convert
recommended
solution to system
specifications
SDLC Implementation Phase
Code, test, install,
and support the
information system
Physical design:
logical
specifications
transformed to
technologyspecific details
1-19
2005 by Prentice Hall
1-20
2005 by Prentice Hall
1-22
2005 by Prentice Hall
SDLC Maintenance Phase
Systematically
repair and improve
the information
system
1-21
2005 by Prentice Hall
The Heart of the Systems
Development Process
Traditional Waterfall SDLC
One phase begins
when another
completes, little
backtracking and
looping
1-23
Current practice combines analysis, design, and implementation
into a single iterative and parallel process of activities
2005 by Prentice Hall
1-24
2005 by Prentice Hall
Problems with Waterfall
Approach
Alternatives to Traditional
Waterfall SDLC
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
1-25
2005 by Prentice Hall
Prototyping
CASE tools
Joint Application Design (JAD)
Rapid Application Development (RAD)
Agile Methodologies
eXtreme Programming
1-26
Prototyping
CASE Tools
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
Iterative development process:
Requirements quickly converted to a working system
System is continually revised
Close collaboration between users and analysts
1-27
2005 by Prentice Hall
Joint Application Design (JAD)
Structured process involving users,
analysts, and managers
Several-day intensive workgroup
sessions
Purpose: to specify or review system
requirements
1-29
2005 by Prentice Hall
2005 by Prentice Hall
1-28
2005 by Prentice Hall
Rapid Application Development
(RAD)
Methodology to decrease design and implementation time
Involves: prototyping, JAD, CASE tools, and code
generators
1-30
2005 by Prentice Hall
Agile Methodologies
eXtreme Programming
Short, incremental development cycles
Automated tests
Two-person programming teams
Coding and testing operate together
Advantages:
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
1-31
2005 by Prentice Hall
Object-Oriented Analysis and
Design
1-32
Communication between developers
High level of productivity
High-quality code
2005 by Prentice Hall
Rational Unified Process (RUP) involves an iterative,
incremental approach to systems development
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-33
2005 by Prentice Hall
1-34
2005 by Prentice Hall
Summary
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-35
2005 by Prentice Hall
