1 intro stu

Upload: adriatic-sea

Post on 26-Feb-2018

220 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/25/2019 1 Intro Stu

    1/14

    1

    Chapter 1

    The Systems Development in

    an Organization Context

    2

    Text Books

    J.A.Hoffer, J.F.George & J.S.Valacich.

    Modern Systems Analysis and Design,

    6th edition, Prentice-Hall, 2011

    J.L.Whitten, L.D.Bentley, & K.C.Dittman, \

    Systems Analysis and Design Method,7thedition, McGraw-Hill, 2007

    K.E.Kendall and J.E.Kendall.

    Systems Analysis and Design,

    8th Edition, Prentice-Hall, 2010

    A.Dennis, B.H.Wixom, and R.M.Roth,

    System Analysis & Design,

    5th Edition, John Wiley, 2012

    G.B.Shelly, T.J.Cashman, and H.J.Rosenblatt,

    Systems Analysis and Design,

    7th Edition, CourseTech, 2007

    J.W.Satzinger, R.B.Jackson, and S.D.Burd,Systems Analysis and Design in a Changing World,

    4th edition, Course Technology, 2006

    3

    Your Objectives of SA&D Study

    IS development methodology

    Principle, idea, technique, tip, knowledge of SA

    Data collection (user handling)

    Case study, real case, prototype

    Problem solving

    Project management (configuration, risk, team, negotiation)

    SA skill, systematic thinking, reengineering

    Drawing diagram, tools, lead to programming

    Outside classroom knowledge, application integration Pros & cons of organization

    Documentation, pattern design, multidisciplinary4

    Your Objects of M.Sc. Study

    Better position, salary

    Chance of work progress

    Organization development

    Get new vision

    Certificate

    Work connection

  • 7/25/2019 1 Intro Stu

    2/14

    5

    Course Content

    Fundamental of System Development

    System Development Life CycleSystem Planning

    System Analysis

    System Design

    System Implementation and Maintenance

    Standard Sustainable System

    Development

    Management /People

    Business Driven

    Methodology ICT: InternetH/W, S/W

    IS

    6

    IS: Enterprise Applications

    Kaizen (for SME)

    ++ Overall+Quality Control

    7

    ERP: need (customer driven) innovation

    using advance technologies

    HR

    Corporate social

    responsibility

    Financial

    Financial performance

    Operations

    Outstanding commitment

    to environment

    Full services

    Smart convergence

    services (solution)

    Marketing & sales

    Excellent customer service

    Outstanding customer service

    Advance & extensive network

    deployment

    Filed market leadership

    Network depth & reliability

    8

    Content

    Information systems analysis and design (SA&D)

    Different types of information systems

    Information Systems Development Life Cycle (SDLC)

    Rapid Application Development (RAD), Prototyping,

    Joint Application Development (JAD), and Computer

    Aided Software Engineering (CASE)

    Agile methodologies and eXtreme programming

    Object Oriented Analysis and Design and RationalUnified Process (RUP)

  • 7/25/2019 1 Intro Stu

    3/14

    9

    1. Introduction

    Information Systems Analysis and Design

    Complex organizational process

    Used to develop and maintain computer-basedinformation systems

    Used by a team of business and systemsprofessionals

    10

    Introduction (Cont.)

    An organizational approach to systems analysis and design is driven by

    methodologies, techniques, and tools

    11

    Modern Approach to SA&D

    1950s: efficient automation of existing processes

    1960s: 3GL, faster and reliable computers

    1970s: system development, using engineeringdiscipline

    1980s: 4GL, CASE tools, object oriented methods

    1990s: system integration, GUI applications,

    client/server platforms, Internet

    The new century : Web application development,

    wireless PDAs, component-based applications,

    ubiquitous technology

    (Charles Babbage)

    12

    Modern Approach to SA&D (Cont.)

    Application Software

    Computer software designed

    to support organizationalfunctions or processes

    Systems Analyst

    Organizational role most

    responsible for analysis and

    design of information

    systems

  • 7/25/2019 1 Intro Stu

    4/14

    13

    Systems Analyst as a Facilitator

    Whitten 14

    Knowledge and Skills of Systems Analyst

    Knowledge

    Information technology

    Computer programming experience and expertise

    General business knowledge

    Skills

    Problem-solving

    Interpersonal communication

    Interpersonal relations

    Flexibility and adaptability

    Character and ethics

    Systems analysis and designWhitten

    15

    2. Types of Information Systems and

    Systems Development

    Transaction Processing Systems (TPS)

    Automate handling of data about businessactivities (transactions)

    Process orientation

    Management Information Systems (MIS)

    Converts raw data from transaction processing

    system into meaningful form

    Data orientation

    16

    Types of Information Systems

    and Systems Development (Cont.)

    Decision Support Systems (DSS)

    Designed to help decision makersProvides interactive environment for decision

    making

    Involves data warehouses, executive information

    systems (EIS)

    Database, model base, user dialogue

    Expert Systems

  • 7/25/2019 1 Intro Stu

    5/14

    17

    Types of Information Systems

    18

    Summary of Information Systems Types

    19

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

    20

    Systems Development Life Cycle (SDLC)

    Traditional methodology used to develop,

    maintain, and replace information systems

    Phases in SDLC:

    Planning

    Analysis

    Design

    ImplementationMaintenance

  • 7/25/2019 1 Intro Stu

    6/14

    21

    Standard and Evolutionary Views of SDLC

    FIGURE 1-3 Evolutionary modelFIGURE 1-2

    The systems development life cycle

    22

    Systems Development Life Cycle (Cont.)

    Planning an organizations total information

    system needs are identified, analyzed,prioritized, and arranged

    Analysis system requirements are studied and

    structured logical system specification (model)

    Design a description of the recommended

    solution is converted intophysical systemspecifications

    23

    Systems Development Life Cycle (Cont.)

    Logical design all functional features of the

    system chosen for development in analysis are

    described independently of any computerplatform

    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

    24

    Logical Design

    vs.

    Physical Design

  • 7/25/2019 1 Intro Stu

    7/14

    25

    Systems Development Life Cycle (Cont.)

    Implementation the information system is

    coded, tested, installed and supported in theorganization

    Maintenance an information system is

    systematically repaired and improved

    26

    27

    SDLC-based Guide to Hoffers Book

    28

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

    The heart of systems development

    FIGURE 1-7

    The analysisdesigncodetest loop

  • 7/25/2019 1 Intro Stu

    8/14

    29

    Traditional Waterfall SDLC

    One phase begins when

    another completes, littlebacktracking and looping

    30

    Problems with Waterfall Approach *

    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

    31 32

    4.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/25/2019 1 Intro Stu

    9/14

    33

    a) Prototyping *

    Iterative development process

    Requirements quickly converted to a workingsystem

    System is continually revised

    Close collaboration between users and analysts

    34

    Prototyping (Cont.)

    12

    3 4

    5

    35

    b) Computer-Aided Software Engineering

    (CASE) Tools

    Diagramming tools enablegraphical representation

    Computer displays and report generators helpprototype how systems look and feel

    Analysis tools automatically check forconsistency in diagrams, forms, and reports

    36

    CASE Tools (Cont.)

    Central repository for integrated storage of

    diagrams, reports, and project management

    specificationsDocumentation generators standardize

    technical and user documentation

    Code generators enable automatic generation

    of programs and database code directly from

    design documents, diagrams, forms, and

    reports

  • 7/25/2019 1 Intro Stu

    10/14

    37

    CASE Tools (Cont.)

    Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall 38

    c) Joint Application Design (JAD)

    Structured process involving users,

    analysts, and managers Several-day intensive workgroup sessions

    Purposeto specify or review system

    requirements

    RAD: was developed by Chuck Morris of IBM Raleigh and

    Tony Crawford of IBM Toronto in the late 1970's

    39

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

    FIGURE 1-11

    RAD life cycle

    40

    Service-Oriented Architecture (SOA)

    An approach to systems development

    based on building complete systems

    through assembling software components,each of which model generic business

    functions

  • 7/25/2019 1 Intro Stu

    11/14

    41

    Service-Oriented Architecture (SOA)

    (Cont.)

    FIGURE 1-12

    Illustration of a service, a credit check,

    used by applications and other services

    42

    e) Agile Methodology

    Motivated by recognition of software

    development as fluid, unpredictable, anddynamic

    Three key principles

    Adaptive rather than predictive

    Emphasizepeople rather than roles

    Self-adaptive processes

    43

    The Agile

    Methodologies group

    argues that software

    development

    methodologies

    adapted from

    engineering generally

    do not fit with real-

    world softwaredevelopment.

    44

    When to use Agile Methodologies

    If your project involves:

    Unpredictable or dynamic requirementsResponsible and motivated developers

    Customers who understand the process and will get

    involved

  • 7/25/2019 1 Intro Stu

    12/14

    45 46

    f) eXtreme Programming

    Short, incremental development cycles

    Automated tests Two-person programming teams

    Coding and testing operate together

    Advantages:

    Communication between developers

    High level of productivity

    High-quality code

    by Kent Beck in the late 90s

    47

    5. Object-Oriented Analysis and Design

    (OOAD)

    Based on objects rather than data or processes

    Object: a structure encapsulating attributes andbehaviors 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 super-class

    48

    Rational Unified Process (RUP)

    An object-oriented systems development

    methodology

    RUP establishes 4 phases of development:inception, elaboration, construction, and

    transition

    Each phase is organized into a number of

    separate iterations

  • 7/25/2019 1 Intro Stu

    13/14

    49Additional source: http://www-306.ibm.com/software/awdtools/rup/

    FIGURE 1-13

    Phases of OOSAD-based development

    50

    Summary

    Information systems analysis and design (SAD)

    Different types of information systems

    Information Systems Development Life Cycle(SDLC)

    Rapid Application Development (RAD),

    Prototyping, Joint Application Development (JAD),

    and Computer Aided Software Engineering (CASE)

    Agile methodologies and eXtreme programming

    Object Oriented Analysis and Design and theRational Unified Process (RUP)

    51

    Questions and Answers

    52

    Further Read

    J.L.Whitten, L.D.Bentley, & K.C.Dittman, Systems Analysis

    and Design Method, 7th edition, McGraw-Hill, 2007

    K.E.Kendall and J.E.Kendall. Systems Analysis and Design,

    6th

    edition, Prentice-Hall, 2005 W.S.DavisBusiness Systems Analysis and Design,

    Wadsworth, 1994

    A. Dennis & et.al. System Analysis and Design, John Wiley,

    2006

    M.L. Gibson and C.T. Hughes. Systems Analysis and Design:

    A Comprehensive Methodology with CASE, Boyd & Fraser,

    1994

  • 7/25/2019 1 Intro Stu

    14/14

    53

    Teamwork Assignment

    Topic

    Form a team of 10 students:

    No, ID, name, email addresses (sort by ID)Mark * for a leader & ** for an auditor after ID

    Email to: [email protected]

    cc: all team members (to build a mailing list)

    Subject: SA-N# (xxx) or SA-W# (xxx)

    where # is a team no. & xxx is week-No(1..15) Submit

    Date: (next week) one day before a class / Time: 1.00 p.m.

    54

    Quiz 1

    1.The __________________________ is thetraditional methodology used to develop,maintain, and replace information systems.

    2.The first phase in the systems development lifecycle (SDLC) is _______.

    3. ______________________________ is astructured process in which users, managers, andanalysts work together for several days in a seriesof intensive meetings to specify or review system

    requirements.4. The output from the analysis phase is the

    _____________________.

    55

    Exercise

    1 List & explain some of the problems with the

    traditional waterfall SDLC.

    2 Explain how prototype might be used as part ofSDLC.

    56

    Enemy

    Inadequate & unstable requirements

    Inadequate customer communication

    Poor team communication Unnecessary complexity

    Ineffective team behavior

    (OO project management using UML)