+ All Categories
Home > Documents > L545 Systems Analysis Design Week 2: September 9, 2008.

L545 Systems Analysis Design Week 2: September 9, 2008.

Date post: 18-Jan-2018
Category:
Upload: darrell-chambers
View: 212 times
Download: 0 times
Share this document with a friend
Description:
Problem w/ Traditional Systems Analysis Approach Dataflow diagram
25
L545 Systems Analysis & Design Week 2: September 9, 2008
Transcript
Page 1: L545 Systems Analysis  Design Week 2: September 9, 2008.

L545 Systems Analysis & Design

Week 2: September 9, 2008

Page 2: L545 Systems Analysis  Design Week 2: September 9, 2008.

Problems with Information Systems

Information Systems-centric

Page 3: L545 Systems Analysis  Design Week 2: September 9, 2008.

Problem w/ Traditional Systems Analysis Approach

Dataflow diagram

Page 4: L545 Systems Analysis  Design Week 2: September 9, 2008.

Problem w/ Traditional Systems Analysis Approach

Dataflow diagram

Page 5: L545 Systems Analysis  Design Week 2: September 9, 2008.

Consider the Work System

People and work practices are essential ingredients in IT success stories, and that supposed “computer glitches” often involve sloppy work practices and human error (Alter, 2006, p. 4)

Page 6: L545 Systems Analysis  Design Week 2: September 9, 2008.

Consider the Work System

Infrastructure

Envir

onm

ent Strategies

Customers

Products & Services

Work Practices

participants Information Technologies

Global Ginat’s CRM system

Page 7: L545 Systems Analysis  Design Week 2: September 9, 2008.

Contextual Design

Discover the everyday work practice of people

Page 8: L545 Systems Analysis  Design Week 2: September 9, 2008.

Contextual Design

Discover the everyday work practice of people

Page 9: L545 Systems Analysis  Design Week 2: September 9, 2008.

How Do We Know ….

To automate self-check out grocery system?

Page 10: L545 Systems Analysis  Design Week 2: September 9, 2008.

How Do We Know ….?

To automate self-check out grocery system?

Page 11: L545 Systems Analysis  Design Week 2: September 9, 2008.

Work Redesign

Page 12: L545 Systems Analysis  Design Week 2: September 9, 2008.

Work Redesign

Page 13: L545 Systems Analysis  Design Week 2: September 9, 2008.

Any Questions

Page 14: L545 Systems Analysis  Design Week 2: September 9, 2008.

Definition of A System A set of components that function

together in a meaningful way

Other examples of a system?

Page 15: L545 Systems Analysis  Design Week 2: September 9, 2008.

Definition of An Information System

Page 16: L545 Systems Analysis  Design Week 2: September 9, 2008.

Definition of An Information System

Any examples of an information system?

Page 17: L545 Systems Analysis  Design Week 2: September 9, 2008.

System Development Life Cycle (SDLC, or the waterfall method)

Problem definition Analysis Design/Development Testing Implementation Maintenance

Page 18: L545 Systems Analysis  Design Week 2: September 9, 2008.

What is a Problem?

A problem is a difference between things as desired and things as perceived (Gause & Weinberg)

Page 19: L545 Systems Analysis  Design Week 2: September 9, 2008.

What is a Problem?

A problem is a difference between things as desired and things as perceived (Gause & Weinberg)

Zero inventory

Page 20: L545 Systems Analysis  Design Week 2: September 9, 2008.

Defining Problems

Problem

Organizational goals

Page 21: L545 Systems Analysis  Design Week 2: September 9, 2008.

Defining Problems

Problem

Organizational goals

Long-term Scope Feasibility

Page 22: L545 Systems Analysis  Design Week 2: September 9, 2008.

You Cannot Solve a Problem Unless You know the Cause

Scientist

Observephenomenon

Formulatehypothesis

Performexperiment

Physician

Observesymptoms

Identifypossiblecauses

Conductdiagnostictests

Systems analyst (You)

Recognizeproblem

List possible causes

Study presentsystem

Page 23: L545 Systems Analysis  Design Week 2: September 9, 2008.

Communicate the hypothesis with the clients

A good problem statement includes: The problem: a list of symptoms

E.g., inventory value is $100,000 too high The objectives: the likely cause(s)

E.g., reduce inventory cost by $100,000 by eliminating obsolete inventory

Resources implications or scope: estimated resources needed to solve the problem (cost estimate)

E.g., the cost of this inventory system will not exceed $100,000

Specify what must be done, not how to do it

Page 24: L545 Systems Analysis  Design Week 2: September 9, 2008.

Problem Definition

The problem definition = the analyst’s preliminary sense of the problem (it could be wrong, thus keep an open mind)

See the assignment page for details: https://ella.slis.indiana.edu/~nhara/teaching/fall08/s556/assign.html

Page 25: L545 Systems Analysis  Design Week 2: September 9, 2008.

WSLC Overview Activity

1. Form groups of 5 people 2. Two teams will work on the UpNow

case, and the other two will work on the Websters4 case

3. Discuss the cases by asking the question on the worksheet

4. Report back to the class


Recommended