Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Information Systems 414 > Chapter 16 > Flashcards

Chapter 16 Flashcards

1
Q

Six Sigma

A
  • A culture built on quality
  • Uses a top-down approach
  • Project leader is called a Black Belt
  • Project members are called Green Belts
  • Master Black Belts have worked on many projects and are available as a resource to project teams
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Philosophy of Six Sigma (7 steps)

A
  1. Define the Problem
  2. Observe the Problem
  3. Analyse the Causes
  4. Act on the Causes
  5. Study the Results
  6. Standardize the Changes
  7. Draw Conclusions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Responsibility for Total Quality Management

A
  • Full organizational support of management must exist

* Early commitment to quality from the analyst and business users

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

Structured Walkthroughs

A
  • One of the strongest quality management actions is to do structured walkthroughs routinely
  • Use peer reviewers to monitor the system’s programming and overall development
  • Point out problems
  • Allow the programmer or analyst to make suitable changes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Who is Involved in Structured Walkthroughs?

A
  • The person responsible for the part of the system being reviewed
  • A walkthrough coordinator
  • A programmer or analyst peer
  • A peer who takes notes about suggestions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

The Top-Down Approach

A
  • Top-down design allows the systems analyst to ascertain overall organizational objectives and how they are best met in an overall system
  • The system is divided into subsystems and their requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Advantages of the Top-Down Approach

A
  • Avoiding the chaos of attempting to design a system all at once
  • Enables separate systems analysis teams to work in parallel on different but necessary subsystems
  • Prevents losing sight of what the system is supposed to do
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Modular Development

A 
• Breaking the programming into logical, manageable portions or modules
• Works well with top-down design
• Each individual module should be functionally
cohesive, accomplishing only one function
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Advantages of Modular Development

A
  • Modules are easier to write and debug
  • Modules are easier to maintain
  • Modules are easier to grasp because they are self- contained subsystems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Guidelines for Modular Programming

A
  • Keep each module to a manageable size
  • Pay particular attention to the critical interfaces
  • Minimize the number of modules the user must modify when making changes
  • Maintain the hierarchical relationships set up in the top- down phases
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Testing, Maintenance, and Auditing

A
  • The testing process
  • Maintenance practices
  • Auditing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

The Testing Process

A
  • Program testing with test data
  • Link testing with test data
  • Full system testing with test data
  • Full system testing with live data
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Program Testing with Test Data

A
  • Desk check programs
  • Test with both valid and invalid data
  • Check output for errors and make any needed corrections
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Link Testing with Test Data

A 
• Also referred to as string testing
• Checks to see if programs that are interdependent
actually work together as planned
• Test for normal transactions
• Test with invalid data
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Full System Testing with Test Data

A
  • Adequate documentation in procedure manuals
  • Are procedure manuals clear enough?
  • Do work flows actually “flow”?
  • Is output correct and do users understand this output?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Full System Testing with Live Data

A
  • Comparison of the new system’s output with what you know to be correctly processed output
  • Only small amounts of live data are used
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Maintenance Practices

A
  • Reduce maintenance costs
  • Improve the existing software
  • Update software in response to the changing organization
  • Ensure channels for feedback
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Auditing

A

• Having an expert who is not involved in setting up or using the system examine information in order to ascertain its reliability
• There are internal and external auditors
• Internal auditors study the controls used in the
information system to make sure that they are adequate
• External auditors are used when the information system processes data that influences a company’s financial statements

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

Client-Server Technology

A
  • The client-server model refers to a design model that can be thought of as applications running on a network
  • The client is a networked computer that uses small programs to do front-end processing, including communicating with the user
20
Q

Advantage of Client-Server Model

A

• Advantage—greater computer power and greater opportunity to customize applications

21
Q

Disadvantage of Client-Server Model

A

more expensive and applications must be written as two separate software components each running on separate machines

22
Q

Cloud Computing

A

• Organizations and individual users can use: – Web services
– Database services
– Application services over the Internet
• Done without having to invest in corporate or personal hardware, software, or software tools
• A large collection of corporate users jointly bear the
lowered cost
• Realize increases in peak-load capacity
• Companies also hope to improve their ability to perform disaster recovery

23
Q

Cloud Computing Trade-Offs

A

• One major decision is whether to use an external cloud
provider (public cloud) or an internal one (private cloud)
• Sometimes the decision to use a public cloud has to do with how critical it is for the company to strategically control data
• A hybrid approach, in which more critical data linked to strategic aims and corporate intellectual property are held in a private cloud, and less critical data for the same organization makes use of a public cloud, may be a solution

24
Q

Factors in Choosing a Cloud Provider

A

• If a client of the cloud services provider is hacked, how will it adversely affect other businesses the cloud provider is hosting?
• How can your client be sure data are completely deleted from cloud systems when these systems are eventually decommissioned?
• Are the data architectures being used by the cloud provider standard and transparent so if the client wants to switch providers it would be realistic to do so?
proprietary programming structures in use, making transferring data out of the question?
• How can your client be certain that no one at the cloud provider or their staff working for other clients has access to your organization’s data?

25
Q

ERP and Cloud Computing

A

• Many of the issues and challenges associated with implementing ERP systems can be mitigated by ERP offerings that take advantage of cloud computing

26
Q

Training

A
  • Who to train
  • People who train users
  • Training objectives
  • Training methods
  • Training sites
  • Training materials
27
Q

Who to Train

A
  • All people who will have primary or secondary use of the system
  • Ensure that users of different skill levels and job interests are separated
28
Q

People Who Train Users

A
  • Vendors
  • Systems analysts
  • External paid trainers • In-house trainers
  • Other system users
29
Q

Conversion Strategies

A
  • Direct changeover
  • Parallel conversion
  • Gradual or phased conversion
  • Modular prototype conversion
  • Distributed conversion
30
Q

Direct Changeover

A
  • Old system stops, new one starts
  • Needs extensive testing
  • Risky approach to conversion
  • Users may resent being forced into using an unfamiliar system without recourse
  • No adequate way to compare new results to old
31
Q

Parallel Conversion

A

• Run the old and new systems at the same time
• The advantage is that you can check new data against
old data
• The disadvantage is doubling employees’ workloads

32
Q

Gradual Conversion

A
  • Combines best features of parallel and direct conversion
  • Volume of transactions is gradually increased
  • Advantage is that users get involved with the system gradually
  • Agile methodologies use this conversion approach
33
Q

Modular Prototype Conversion

A 
• Each module is tested and put into use
• The advantage is that each module is thoroughly tested
before being used
• Users are familiar with each module as it becomes operational
• Object-oriented methodologies often use this approach
34
Q

Distributed Conversion

A

• When there are many installations of the same system, such as at branch offices
• Install software at one office
• Advantage is that problems can be detected and
contained
• Disadvantage is that even when one conversion is successful, each site will have its own peculiarities to work through

35
Q

Three types of Security Concerns

A
  • Physical security
  • Logical security
  • Behavioral security
36
Q

Physical security

A

securing the computer facility, its

equipment, and software through physical means

37
Q

Logical security

A

refers to logical controls in the software itself

38
Q

Behavioral security

A

building and enforcing procedures to prevent the misuse of computer hardware and software

39
Q

Special Security Considerations for Ecommerce

A

• Virus protection software
• Email filtering products
• URL filtering products
• Firewalls, gateways, and virtual private networks
• Intrusion detection products
• Vulnerability management products
• Security technologies such as secure socket layering (SSL)
for authentication
• Encryption technologies
• Public key infrastructure (PKI) use and obtaining a digital certificate

40
Q

Information System Utility Approach

A
  • Possession
  • Form
  • Place
  • Time
  • Actualization
  • Goal
41
Q

Possession utility

A

answers the question of who should

receive output

42
Q

Goal utility

A

answers the why of information systems by asking whether the output has value in helping the organization achieve its objectives

43
Q

Place utility

A

answers the question of where information is distributed

44
Q

Form utility

A

answers the question of what kind of

output is distributed to the decision maker

45
Q

Time utility

A

answers the question of when information

is delivered

46
Q

Actualization utility

A

involves how the information is

introduced and used by the decision-maker

47
Q

Website Evaluation

A

• Know how often the Web site is visited
• Learn details about specific pages on the site
• Find out more about the Web site’s visitors
• Discover if visitors can properly fill out the forms you
designed
• Find out who is referring Web site visitors to the client’s site
• Determine what browsers visitors are using
• Find out if the client’s Web site visitors are interested in advertising

Information Systems 414 (12 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions