Chapter 13: Building Info Systems Flashcards

1
Q

4 Kinds of Structure Organizational Change

A
  • automation
  • rationalization
  • business process redesign
  • paradigm shifts
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Automation

A

assisting employees with performing their tasks more efficiently and effectively
- productivity boost, decreases operational costs
- enhance data collection and analysis
- alters customer service interaction

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

Rationalization

A

streamlines standard operating procedures –> instructions and standardized tasks for consistency, quality, and efficiency
- eliminate unnecessary steps, decrease complexity
- focus on essential activities

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

Total Quality Management (TQM)

A

makes acheiving quality the responsibility of all within the organization

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

Six Sigma

A

measure of quality
goal for driving ongoing quality improvement progress

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

Business Process Redesign

A

business processes are analyzed, simplified, and redesigned
- organizes workflows to cut waste and eliminate repetitive tasks
- requires new “vision” how process is organized
- encourages cross-funcitonal collabs
makes sure process aligns with orgs goals

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

Paradigm Shift

A

more radical form of business change
- rethinking nature of business org
might encourage more adaptable and open environment, embracing experimentation
- necessitate collaboration against collab and teams

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

Business Process Redesign Steps

A

1) identify process for change
2) analyze existing process
3) design new process
4) implement new process
5) continuous measurement

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

Systems Development Process

A

new IS –> built as a solution to a problem or set of problems facing an org
systems development –> activities that go into producing an IS to an organizational prob or opportunity
structured problems solved with distinct activities
systems analysis –> systems design –> programming –> testing –> conversion –> production and maintenance

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

Systems Analysis

A

analysis of a problem that a firm tries to solve with an info system
1) define problem
2) identify causes
3) specifying solution
- Feasibility study
- info requirements
- systems proposal report

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

Feasibility Study

A

is the IS solution achievable

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

Info Requirements (sys analysis)

A
  • defines the objectives of the new or modified system and develops a detailed description of the functions the new system must perform
  • faulty requirements analysis is a leading cause of systems failure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Systems Design

A

how system will deliver functions identified during systems analysis
- should address all managerial, organizational, and tech components of a solution
ROLE OF END USERS
- user info requirements drive system building
- must have sufficient control over design process to ensure system reflects their business priorities and info needs
- insufficient user involvement in design effort is a major cause of failure

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

programming

A

system specification from design stage are translated into software program code
- might be purchased, licensed, or developed through 3rd party vendor

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

Testing

A

ensures system produces correct results through extensive and time consuming tests

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

Unit testing

A

testing each program separately in the system

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

System Testing

A

testing the funcitonality of system in its entirety

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

Acceptance Testing

A

final certification that the system is ready for production

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

Test plan

A

includes all preparations for tests
- work with end users to develop system testing
- includes conditions to be tested, and requirements and expected results

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

Conversion

A

changes from old system to new system
- required end users training and comprehensive documentation

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

Parallel Strategy

A

old system and new system run together for a time until everyone is assured the new one is correct
safest, most expensive

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

Direct Cutover Strategy

A

replaces old system in entirety with new system on appointed day
- risky, if issues costly

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

Pilot Study Strategy

A

new system introduced to pilot small population when working smoothly, installed

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

Phased Approach Strategy

A

new system introduced in phases

25
Q

Production

A

system reviewed by users and technical specialists to determine if revisions or modifications are needed
- post-implementation audit determines how well system meets og objectives

26
Q

Maintenance

A

changes in hardware, software, and documentation or procedures to a product system
- correct errors, meets new requirements or improve efficiency

27
Q

Structured Methodologies

A

technologies are step-by-step
- process-oriented modeling process that manipulates data
- separates data from process

28
Q

Data Flow Diagram

A

graphically illustrates a systems component process and flow of data between
- logical model of flow
- complex processes can be broken down and successive levels of detail

29
Q

Process specifications

A

describe the transformation occuring within lowest level of data
- flow diagrams

30
Q

Data dictionary

A

contains info about individual pieces of data and data groupings within system
- defines contents of data flows and stores so builders understand data contained

31
Q

Structure Chart

A

top-down chart, shows relationships between levels of design
-1st considers main function of program
- then breaks it into subfunction
- finally decompose each subfunction until lowest level of detail is reached

32
Q

Object-Oriented Development

A

addresses common issues with structured methodology
- Object: basic unit of systems analysis and design
- program send a message for an object to perform an operation
modeled as collection of objects and relationship among them

33
Q

Object-Oriented Modeling

A

objects belong to a certain class and have features of that class

34
Q

Traditional Systems Life Cycle

A

phased approach at building system
- divided into formal stages
- formal division of labor between end users and information system specialties

35
Q

Prototyping

A

building an experimental system rapidly and inexpensively
- iterative –> steps can be repeated over and over
- replaces unplanned rework, each version more and more accurately reflects users’ requirements

36
Q

Prototype

A

working version of product, premliminary model

37
Q

Prototyping Pros

A
  • useful if some uncertainty in design
  • often used for end-user interface design
  • more likely to fulfil end user requiremetns
38
Q

Prototyping Cons

A
  • may glass over essential steps
  • may not accommodate large quantities of data or large number of users
  • may not undergo full testing
39
Q

Application Software Package and Cloud Software service

A

alternative to buying systems –> licensing or purchasing an existing
- software packages and services save time, $, and offer customization features

40
Q

Evaluation Criteria for Systems

A
  • functions provided, flexibility, user friendliness, required resources, database requirements, installation, and maintenance
41
Q

Request for Proposal (RFP)

A

detailed list of questions submitted to software vendors –> used to evaluate alternative software packages and cloud service software

42
Q

Outsourcing

A

Cloud and SAAS Providers
- subscribing companies use software and hardware provided by vendors
External Vendors
- hired to design, create software

43
Q

Domestic Outsources

A

driven by firm’s need for additional skills, resources assets

44
Q

Offshore Outsourcing

A

driven by cost savings
(other workers makes less than have US makes)

45
Q

Outsourcing pro

A

allows org flexibility in IT needs

46
Q

Cons outsourcing

A
  • hidden costs (identifying vendor, transitioning)
  • opening proprietary business to 3rd party
47
Q

Rapid Allocation Development (RAD)

A

creating workable systems in a short period of time -
- flexibility to adapted as the project evolves
- includes use of visual programming and other tools

48
Q

Joint Application Design (JAD)

A

accelerate generation of information requirements by having end users and IS work together in intensive design sessions
- session must be properly prepared and designed
- can significantly speed up design phase

49
Q

Agile

A

type of project management
- rapid delivery of working software eby breaking large projects into subprojects that can be compiled in short period of time (sprints)

50
Q

Automates Software Testing

A

tools to perform examinations of software, report outcomes, compare results with earlier test runs

51
Q

Dev Ops

A

builds an agile development principles as an org strategy

52
Q

Low-Code Development

A

enables creation of workable software with minimal hand-coding
- uses visual modeling in a graphic interface to assemble apps
reduce hardcoding so business apps can be created by a wide range of people more rapidly

53
Q

No-Code Development

A

includes built in tools that enable user to create apps without coding
Cons: limited functionality, can create apps without proper management oversight

54
Q

Mobile Website

A

version that is scaled down in content and navigation for easy access and search on a small mobile screen

55
Q

Mobile Web App

A

internet-enabled app with specific functionality for mobile devices through web browser

56
Q

Native App

A

standalone app designed to run on platform and device
installed directly on device

57
Q

Responsive Web Design

A

websites programmed so that layouts change automatically according to user’s computing device

58
Q
A