Pertemuan 2 PDF

Modern Systems Analysis
and Design Learning Objectives

Seventh Edition
 Define information systems analysis and design.
 Describe the information systems development life cycle
Jeffrey A. Hoffer (SDLC).
Joey F. George  Explain Rapid Application Development (RAD) and
computer-aided software engineering (CASE) tools.
Joseph S. Valacich  Describe Agile Methodologies and eXtreme
Programming.
Chapter 1  Explain object-oriented analysis and design and the
Rational Unified Process (RUP).
The Systems Development
Environment
Chapter 1 Copyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 2
Introduction Introduction (Cont.)

 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
FIGURE 1-1 An organizational approach to systems analysis and

design is driven by methodologies, techniques, and tools
Chapter 1 Copyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 3 Chapter 1 Copyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 4
1
A Modern Approach to Systems
Introduction (Cont.)
Analysis and Design
 Application Software  1950s: focus on efficient automation of
existing processes
 Computer software designed to support
 1960s: advent of procedural third
organizational functions or processes
generation languages (3GL) faster and
 Systems Analyst more reliable computers
 Organizational role most responsible for  1970s: system development becomes
analysis and design of information systems more like an engineering discipline
A Modern Approach to Systems

Developing Information Systems
Analysis and Design (Cont.)
 1980s: major breakthrough with 4GL,  System Development Methodology is a
CASE tools, object-oriented methods standard process followed in an
 1990s: focus on system integration, GUI
applications, client/server platforms, organization to conduct all the steps
Internet necessary to analyze, design, implement,
 The new century: Web application and maintain information systems.
development, wireless PDAs and smart
phones, component-based applications,
application service providers (ASP)
2
Systems Development Life Standard and Evolutionary Views
Cycle (SDLC) of SDLC
 Traditional methodology used to develop,
maintain, and replace information systems
 Phases in SDLC:
 Planning
 Analysis
 Design
 Implementation
FIGURE 1-3 Evolutionary model
 Maintenance FIGURE 1-2
Systems development life cycle
Systems Development Life Cycle Systems Development Life Cycle

(SDLC) (Cont.) (SDLC) (Cont.)
 Planning – an organization’s total  Logical design – all functional features of
information system needs are identified, the system chosen for development in
analyzed, prioritized, and arranged analysis are described independently of
any computer platform
 Analysis – system requirements are
 Physical design – the logical
studied and structured specifications of the system from logical
 Design – a description of the design are transformed into the
recommended solution is converted into technology-specific details from which all
logical and then physical system programming and system construction can
specifications be accomplished
3
Systems Development Life Cycle
(SDLC) (Cont.)
 Implementation – the information system
is coded, tested, installed and supported in
the organization
 Maintenance – an information system is
systematically repaired and improved
The Heart of the Systems Development Process

FIGURE 1-8
Traditional Waterfall SDLC
FIGURE 1-9
Analysis–design–code–test loop The heart of systems development
One phase begins

when another
completes, with
little backtracking
and looping.
FIGURE 1-10
Traditional waterfall SDLC
Current practice combines analysis, design, and implementation

into a single iterative and parallel process of activities.
Chapter 1 Copyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall Chapter 1 Copyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 16
4
Different Approaches to Improving
Problems with Waterfall Approach
Development
 Feedback ignored, milestones lock in  CASE Tools
design specs even when conditions
 Rapid Application Development
change
(RAD)
 Limited user involvement (only in
requirements phase)  Agile Methodologies
 Too much focus on milestone deadlines of  eXtreme Programming

SDLC phases to the detriment of sound
development practices
Computer-Aided Software Computer-Aided Software

Engineering (CASE) Tools Engineering (CASE) Tools (Cont.)
 Diagramming tools enable graphical  Analysis tools automatically check for
representation. consistency in diagrams, forms, and
reports.
 Computer displays and report generators
 A central repository provides integrated
help prototype how systems “look and storage of diagrams, reports, and project
feel”. management specifications.
 IBM’s Rational products are the best
known CASE tools.
5
Computer-Aided Software CASE Tools (Cont.)
Engineering (CASE) Tools (Cont.)
 Documentation generators standardize
technical and user documentation.
 Code generators enable automatic FIGURE 1-11
Screen shot of
generation of programs and database ArgoUML, an open
code directly from design documents, source CASE tool
diagrams, forms, and reports. (Source:

http://argouml.tigris.org/)
Rapid Application Development

CASE Tools (Cont.)
(RAD)
 Decreases design and implementation
time
 Involves: extensive user involvement,
prototyping, integrated CASE tools, code
generators
 More focus on user interface and system
function, less on detailed business
analysis and system performance
6
Rapid Application Development
Agile Methodologies
(RAD) (Cont.)
 Motivated by recognition of software
FIGURE 1-12
RAD life cycle development as fluid, unpredictable, and
dynamic
 Three key principles
 Adaptive rather than predictive
 Emphasize people rather than roles
 Self-adaptive processes
When to use Agile Methodologies

 If your project involves:
 Unpredictable or dynamic requirements
The Agile
Methodologies group  Responsible and motivated developers
argues that software
development  Customers who understand the process and
methodologies
adapted from
will get involved
engineering generally
do not fit with real-
world software
development.
7
eXtreme Programming
 Short, incremental development cycles
 Automated tests
 Two-person programming teams
 Coding, testing, listening, designing
Object-Oriented Analysis and

eXtreme Programming (Cont.)
Design (OOAD)
 Coding and testing operate together  Based on objects rather than data or
 Advantages: processes
 Communication between developers  Object: a structure encapsulating
 High level of productivity attributes and behaviors of a real-
 High-quality code world entity
8
Object-Oriented Analysis and
Rational Unified Process (RUP)
Design (OOAD) (Cont.)
 Object class: a logical grouping of  An object-oriented systems development
objects sharing the same attributes methodology
and behaviors  Establishes four phase of development:
 Inheritance: hierarchical inception, elaboration, construction, and
arrangement of classes enable transition
subclasses to inherit properties of  Each phase is organized into a number of
superclasses separate iterations.
FIGURE 1-13
Our Approach to Systems
Phases of OOSAD-based development Development
 The SDLC is an organizing and guiding
principle in this book.
 We may construct artificial boundaries or
artificially separate activities and
processes for learning purposes.
 Our intent is to help you understand all the
pieces and how to assemble them.
9
Summary
This image cannot currently be display ed.
 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 Service-Oriented Architecture (SOA).
 Describe agile methodologies and eXtreme
programming.
Copyright © 2014 Pearson Education, Inc.
 Explain Object-Oriented Analysis and Design Publishing as Prentice Hall
(OOAD) and the Rational Unified Process (RUP).
Chapter 1 Copyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 37
10

Pertemuan 2 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Pertemuan 2 PDF

Transféré par

Droits d'auteur :

Formats disponibles

Modern Systems Analysis

and Design Learning Objectives

Introduction Introduction (Cont.)

FIGURE 1-1 An organizational approach to systems analysis and

A Modern Approach to Systems

Systems Development Life Cycle Systems Development Life Cycle

The Heart of the Systems Development Process

One phase begins

Current practice combines analysis, design, and implementation

 Too much focus on milestone deadlines of  eXtreme Programming

Computer-Aided Software Computer-Aided Software

diagrams, forms, and reports. (Source:

Rapid Application Development

When to use Agile Methodologies

Object-Oriented Analysis and

 In this chapter you learned how to:

Chapter 1 Copyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 37

Vous aimerez peut-être aussi