Chapter 10: Building Successful Information Systems Flashcards

1
Q

Why do Business Information Systems often fail (5)

A
  • incomplete requirements
  • failure to include all members
  • lack of clarity
  • lack of communication
  • unrelated goals and expectations etc
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

System Development Life Cycle SDLC Phases (5)

A
  1. Planning
  2. Requirements gathering and analysis
  3. Decision
  4. Implementation
  5. Maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

System Development Life Cycle 1. Planning

A

define internal/external problems of organization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

analyst or team assess current and future needs of organization: Planning 4 W’s

A

why is it designed
who will be using it
when will it be operational
what are its capabilities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Planning - Task Force Formation Team (who is on it)

A

representatives from different departments, systems analyst, stakeholders, and top management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Internal users
external users

A

employee use system regularly
customers, contractors, suppliers, partners

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Boundary Spanning Roles (2)

A
  1. Link internal resources and external info sources
  2. speak languages of technology and business
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Feasibility studies

A

measure of beneficial/practical of new IS 4 Org

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Feasibility studies 5 dimensions ETOSL

A

Economic
Technical
operational
scheduling
legal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Tangible Costs

A

quantifiable costs relating to identifiable source

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Intangible Costs

A

unquantifiable costs related to identity source

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Tangible Benefit example
Intangible Benefit example

A

Benefits quantified in terms of money
difficult to identify and quantify in terms of dollar amounts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Feasibility studies - technical

A

technology used in the system, is it available and feasible

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Feasibility studies - operational

A

how well new IST solution will work,resistance? support?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Feasibility studies - scheduling

A

system schedule for implementation and progression, deadlines, potential set backs or losses

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Feasibility studies - legal

A

legal issues, restrictions, political consequences , conflicts with government

17
Q

Requirements Gathering Analysis

A

Gathering requirements via interviews, surveys, observations, brainstroming

18
Q

Output of analysis

A

requirements doc, data flow, flowchart, conceptual models

19
Q

Phase 3: Decision

A

Analyst choose solution most realistic and yields highest payoff

20
Q

Output of Phase 3:

A

document with exact specifications for implementation

21
Q

Phase 4: Implementation

A

Solution from paper to action

22
Q

Implementation Tasks for IS (4-6)

A

employment, schedule, plan and design, code/test, security measure and safeguard

23
Q

Request for Proposal / Information

A

document with specifications on equipment, supplies, services, vendors

24
Q

Critical Path

A

longest path to complete the project

25
Q

Gantt Chart for implementation

A

Implementation by month timeline and category

26
Q

Phase 5: Maintenance

A

Information Systems is in operation, review, enhance, modify and test.

collect performance data and if meet expectations

27
Q

Service Oriented Architecture

A

software and system development methodology focuses on development and reuse of small self contained codes to meet software needs

28
Q

High Modularity Required

A

Reusable Blocks of Codes

29
Q

Agile Methodologies

A

communication and feedback

30
Q

Rapid Application Development

A

continuous interaction between user involvement and design

31
Q

Rapid Application Development Process cycle rddt

A

repeat, design, development, and test

32
Q

Extreme Programming

A

project in smaller functions and developed in step by step functions

33
Q

blocked steps

A

next phase or step cannot occur till previous step completed

34
Q

pair programming

A

find error before entire program written

35
Q

Agile and task divison

A

able to move quickly and easily
short phases of work and frequent reassessment and adaptation

36
Q

Agile methods drawbacks

A

bugs accumulate, team members change, requirements change