Hoffer5e_CH01

Embed Size (px)

Citation preview

  • 7/30/2019 Hoffer5e_CH01

    1/35

    Chapter 1

    The Systems DevelopmentEnvironment

    Modern Systems Analysisand Design

    Fifth Edition

    Jeffrey A. HofferJoey F. George

    Joseph S. Valacich

  • 7/30/2019 Hoffer5e_CH01

    2/35

    2008 by Prentice Hall 3Chapter 1

    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 systemsprofessionals.

  • 7/30/2019 Hoffer5e_CH01

    3/35

    Introduction (Cont.)

    2008 by Prentice Hall 4Chapter 1

    Figure 1-1 An organizational approach to systems analysis and

    design is driven by methodologies, techniques, and tools

  • 7/30/2019 Hoffer5e_CH01

    4/35

    2008 by Prentice Hall 5Chapter 1

    A Modern Approach to Systems

    Analysis and Design (Cont.)Application Software

    Computer software designed to support

    organizational functions or processes.

    Systems Analyst role

    Study the problems and needs of an

    organization to bring improvements to theorganization

  • 7/30/2019 Hoffer5e_CH01

    5/35

    2008 by Prentice Hall 6Chapter 1

    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 transactionprocessing system into meaningful form

    Data orientation

  • 7/30/2019 Hoffer5e_CH01

    6/35

    2008 by Prentice Hall 7Chapter 1

    Types of Information Systems

    and Systems Development (Cont.) Decision Support Systems (DSS)

    Designed to help decision makers

    Provides interactive environment for decisionmaking

    Involves data warehouses, executive

    information systems (EIS)Database, model base, user dialogue

  • 7/30/2019 Hoffer5e_CH01

    7/35

    2008 by Prentice Hall 8Chapter 1

    Summary of Information

    Systems Types

  • 7/30/2019 Hoffer5e_CH01

    8/35

    2008 by Prentice Hall 9Chapter 1

    Developing Information Systems

    System Development Methodology is astandard process followed in an

    organization to conduct all the stepsnecessary to analyze, design, implement,

    and maintain information systems.

  • 7/30/2019 Hoffer5e_CH01

    9/35

    2008 by Prentice Hall 10Chapter 1

    Systems Development Life

    Cycle (SDLC) Traditional methodology used to develop,

    maintain, and replace information systems.

    Phases in SDLC: Planning

    Analysis

    Design

    Implementation

    Maintenance

  • 7/30/2019 Hoffer5e_CH01

    10/35

    2008 by Prentice Hall 11Chapter 1

    Systems Development Life Cycle

    (SDLC) (Cont.) Planningan organizations total

    information system needs are identified,

    analyzed, prioritized, and arranged. Analysis system requirements are

    studied and structured.

  • 7/30/2019 Hoffer5e_CH01

    11/35

    2008 by Prentice Hall 12Chapter 1

    Systems Development Life Cycle

    (SDLC) (Cont.) Design a description of the

    recommended solution is converted into

    logical and then physical systemspecifications.

    Logical design all functional features ofthe system chosen for development inanalysis are described independently ofany computer platform.

  • 7/30/2019 Hoffer5e_CH01

    12/35

    2008 by Prentice Hall 13Chapter 1

    Systems Development Life Cycle

    (SDLC) (Cont.) Physical design the logical

    specifications of the system from logical

    design are transformed into thetechnology-specific details from which all

    programming and system construction can

    be accomplished.

  • 7/30/2019 Hoffer5e_CH01

    13/35

    2008 by Prentice Hall 14Chapter 1

    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.

  • 7/30/2019 Hoffer5e_CH01

    14/35

    2008 by Prentice Hall 15Chapter 1

  • 7/30/2019 Hoffer5e_CH01

    15/35

    2008 by Prentice Hall 16Chapter 1

    Traditional Waterfall SDLC

    One phase begins

    when anothercompletes, little

    backtracking and

    looping

  • 7/30/2019 Hoffer5e_CH01

    16/35

    2008 by Prentice Hall 17Chapter 1

    Problems with Waterfall Approach

    System requirements locked in after

    being determined (can't change).

    Limited user involvement (only inrequirements phase).

    Too much focus on milestone deadlines of

    SDLC phases to the detriment of sounddevelopment practices.

  • 7/30/2019 Hoffer5e_CH01

    17/35

    2008 by Prentice Hall 18Chapter 1

    Different Approaches to Improving

    Development Prototyping

    Computer-Aided Software Engineering (CASE)

    Tools Joint Application Design (JAD)

    Rapid Application Development (RAD)

    Agile Methodologies eXtreme Programming

  • 7/30/2019 Hoffer5e_CH01

    18/35

    2008 by Prentice Hall 19Chapter 1

    Prototyping

    Iterative development process:

    Requirements quickly converted to a

    working system.

    System is continually revised.

    Close collaboration between users and

    analysts.

  • 7/30/2019 Hoffer5e_CH01

    19/35

    2008 by Prentice Hall 20Chapter 1

    Prototyping (Cont.)

  • 7/30/2019 Hoffer5e_CH01

    20/35

    2008 by Prentice Hall 21Chapter 1

    Computer-Aided Software Engineering

    (CASE) Tools

    Software tools that provide automated support for someportion of the systems development process.

  • 7/30/2019 Hoffer5e_CH01

    21/35

    2008 by Prentice Hall 22Chapter 1

    Computer-Aided Software Engineering

    (CASE) Tools (general types)

    Diagramming tools enable graphical representation.

    Computer displays and report generators helpprototype how systems look and feel.

    Analysis tools automatically check for consistencyin diagrams, forms, and reports.

  • 7/30/2019 Hoffer5e_CH01

    22/35

    2008 by Prentice Hall 23Chapter 1

    Computer-Aided Software Engineering

    (CASE) Tools (general types) Central repository for integrated storage of

    diagrams, reports, and project managementspecifications.

    Documentation generators standardize technicaland user documentation.

    Code generators enable automatic generation ofprograms and database code directly from designdocuments, diagrams, forms, and reports.

  • 7/30/2019 Hoffer5e_CH01

    23/35

    CASE Tools (Cont.)

    2008 by Prentice Hall 24Chapter 1

  • 7/30/2019 Hoffer5e_CH01

    24/35

    2008 by Prentice Hall 25Chapter 1

    Joint Application Design (JAD)

    Structured process involving users,

    analysts, and managers.

    Several-day intensive workgroup sessions.

    Purpose: to specify or review system

    requirements.

  • 7/30/2019 Hoffer5e_CH01

    25/35

    2008 by Prentice Hall 26Chapter 1

    Rapid Application Development

    (RAD)Methodology to radically decrease

    design and implementation time.

    Involves: extensive user involvement,

    prototyping, JAD sessions, integrated

    CASE tools, and code generators.

  • 7/30/2019 Hoffer5e_CH01

    26/35

    2008 by Prentice Hall 27Chapter 1

    Rapid Application Development

    (RAD) (Cont.)

  • 7/30/2019 Hoffer5e_CH01

    27/35

    2008 by Prentice Hall 28Chapter 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.

  • 7/30/2019 Hoffer5e_CH01

    28/35

    2008 by Prentice Hall 29Chapter 1

    eXtreme Programming

    Short, incremental development cycles.

    Automated tests.

    Two-person programming teams.

  • 7/30/2019 Hoffer5e_CH01

    29/35

    2008 by Prentice Hall 30Chapter 1

    eXtreme Programming (Cont.)

    Coding and testing operate together.

    Advantages:

    Communication between developers.

    High level of productivity.

    High-quality code.

  • 7/30/2019 Hoffer5e_CH01

    30/35

    2008 by Prentice Hall 31Chapter 1

    Object-Oriented Analysis and

    Design (OOAD) Based on objects rather than data or

    processes.

    Combines data and processes (methods)into single entities called objects

    Object: a structure encapsulatingattributes and behaviors of a real-worldentity.

  • 7/30/2019 Hoffer5e_CH01

    31/35

    2008 by Prentice Hall 32Chapter 1

    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 enablesubclasses to inherit properties ofsuperclasses.

  • 7/30/2019 Hoffer5e_CH01

    32/35

    2008 by Prentice Hall 33Chapter 1

    Rational Unified Process (RUP)

    An object-oriented systems development

    methodology.

    RUP establishes four phase ofdevelopment: inception, elaboration,

    construction, and transition.

    Each phase is organized into a number ofseparate iterations.

  • 7/30/2019 Hoffer5e_CH01

    33/35

    2008 by Prentice Hall 34Chapter 1

    Phases of OOSAD-based

    Development

    Figure 1-14 Phases of OOSAD-based development

  • 7/30/2019 Hoffer5e_CH01

    34/35

    2008 by Prentice Hall 35Chapter 1

    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).

  • 7/30/2019 Hoffer5e_CH01

    35/35

    2008 by Prentice Hall 36Chapter 1

    Summary (Cont.)

    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).