Chapter 1 The Systems Development Environment.pdf

Chapter 1 Copyright © 2017 Pearson Education, Ltd. 1-1
Chapter 1
The Systems Development
Environment
Modern Systems Analysis
and Design
Eighth Edition, Global Edition
Joseph S. Valacich
Joey F. George

Learning Objectives
 Define information systems analysis and design.
 Describe the information systems development life cycle
(SDLC).
 Explain computer-aided software engineering (CASE)
tools.
 Describe Agile Methodologies and eXtreme
Programming.
 Explain object-oriented analysis and design and the
Rational Unified Process (RUP).

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

Introduction (Cont.)
 Application Software
Computer software designed to support
organizational functions or processes
 Systems Analyst
Organizational role most responsible for
analysis and design of information systems

Introduction (Cont.)
FIGURE 1-1 An organizational approach to systems analysis and
design is driven by methodologies, techniques, and tools.
Sources: Mitarart/Fotolia, PaulPaladin/Fotolia

A Modern Approach to Systems
Analysis and Design
 1950s: focus on efficient automation of
existing processes
 1960s: advent of procedural third
generation languages (3GL) faster and
more reliable computers
 1970s: system development becomes
more like an engineering discipline

A Modern Approach to Systems
Analysis and Design (Cont.)
 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 and smart
phones, component-based applications,
per-use cloud-based application services.

Developing Information Systems
 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 Development Life
Cycle (SDLC)
 Traditional methodology used to develop,
maintain, and replace information systems
 Phases in SDLC:
 Planning
 Analysis
 Design
 Implementation
 Maintenance

Standard and Evolutionary Views
of SDLC
FIGURE 1-3 Evolutionary model
FIGURE 1-2
Systems development life cycle

Systems Development Life Cycle
(SDLC) (Cont.)
 Planning – an organization’s total
information system needs are identified,
analyzed, prioritized, and arranged
 Analysis – system requirements are
studied and structured
 Design – a description of the
recommended solution is converted into
logical and then physical system
specifications

(SDLC) (Cont.)
 Logical design – all functional features of
the system chosen for development in
analysis are described independently of
any computer platform
 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

(SDLC) (Cont.)
 Implementation – the information system
is coded, tested, installed and supported in
the organization
 Maintenance – an information system is
systematically repaired and improved

A Specialized Systems
Development Life Cycle
Figure 1-7
Microsoft’s Security Development Lifecycle (SDL)
(Source: http://www.microsoft.com/security/sdl/default.aspx.
Used by permission.)
These are like traditional
SDLC’s analysis, design, and
implementation.
Training
focuses on
security.
Verification
focuses on
product
quality
assurance.
Release
makes
product
available
for general
use.
Response
deals with
security
problems
that come up
after product
release.

FIGURE 1-9
The heart of systems development
The Heart of the Systems Development Process
Current practice combines analysis, design, and implementation
into a single iterative and parallel process of activities.
FIGURE 1-8
Analysis–design–code–test loop

Traditional Waterfall SDLC
One phase begins
when another
completes, with
little backtracking
and looping.
FIGURE 1-10
Traditional waterfall SDLC

Problems with Waterfall Approach
 Feedback ignored, milestones lock in
design specs even when conditions
change
 Limited user involvement (only in
requirements phase)
 Too much focus on milestone deadlines of
SDLC phases to the detriment of sound
development practices

Different Approaches to Improving
Development
 CASE Tools
 Agile Methodologies
 eXtreme Programming

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

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.

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.

CASE Tools (Cont.)

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

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

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

eXtreme Programming
 Short, incremental development cycles
 Automated tests
 Two-person programming teams
 Coding, testing, listening, designing

eXtreme Programming (Cont.)
 Coding and testing operate together
 Advantages:
Communication between developers
High level of productivity
High-quality code

Object-Oriented Analysis and
Design (OOAD)
 Based on objects rather than data or
processes
 Object: a structure encapsulating
attributes and behaviors of a real-
world entity

Object-Oriented Analysis and
Design (OOAD) (Cont.)
 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

Rational Unified Process (RUP)
 An object-oriented systems development
methodology
 Establishes four phase of development:
inception, elaboration, construction, and
transition
Each phase is organized into a number of
separate iterations.

FIGURE 1-11
Phases of OOSAD-based development

Our Approach to Systems
Development
 Criticisms of SDLC
Forcing timed phases on intangible processes
(analysis and design) is doomed to fail
Too much formal process and documentation
slows things down
Cycles are not necessarily waterfalls
 And yet the concept of a cycle is in all
methodologies. So, SDLC is a valuable
model that has many variations.

Summary
 In this chapter you learned how to:
 Define information systems analysis and design.
 Describe the information systems development life
cycle (SDLC).
 Explain computer-aided software engineering (CASE)
tools.
 Describe Agile Methodologies and eXtreme
Programming.
 Explain object-oriented analysis and design and the
Rational Unified Process (RUP).

Chapter 1 The Systems Development Environment.pdf

More Related Content

What's hot (20)

Similar to Chapter 1 The Systems Development Environment.pdf (20)

More from SuryaBasnet3 (20)

Recently uploaded (20)

Chapter 1 The Systems Development Environment.pdf