System Analysis & Design Chapter 2 Study Guide

Kill Me Now.

The practice of turning over responsibility of some or all of an organization's information systems applications and operations to an outside firm is referred to as:

outsourcing

When developing information systems, an organization could use which of the following:
A) an information technology services firm.
B) open-source software.
C) cloud computing.
D) in-house development.
E) all of the above.

all of the above

Packaged software producers create software such as:

excel

A system that integrates individual traditional business functions into a series of modules so that a single transaction occurs seamlessly within a single information system rather than several separate systems best describes:

enterprise resource planning (erp)

All of the following are benefits of enterprise solutions, EXCEPT:

shifting toward enterprise solutions means changing business processes

The provision of computing resources over the Internet so that customers do not need to invest in infrastructure is called:

cloud computing

All of the following are reasons to go with cloud computing EXCEPT:

reduced development time

The primary concern about cloud computing is:

reliability

Open-source software is developed by:

communities of interested people

An organization should acquire software from in-house developers when:

the resources and staff are available and the system must be built from scratch

Which of the following describes the internal staffing requirements when software components are acquired from packaged software producers?

some information systems and user staff to define requirements and evaluate packages are needed

Which of the following describes the internal staffing requirements when software components are acquired from enterprise-wide solutions providers?

some internal staff are necessary, but mostly consultants are needed

Which of the following options are common criteria to consider when selecting off-the-shelf software?
A) Flexibility
B) Vendor viability
C) Functionality
D) Cost
E) All of the above

all of the above

Two criteria that are always among the most important when choosing software are:

vendor support & vendor viability

In terms of criteria to consider when choosing off-the-shelf software, ease of customization is also referred to as:

(D) flexibility

In terms of criteria to consider when choosing off-the-shelf software, documentation refers to all of the following EXCEPT:
A) user's manuals.
B) technical documentation.
C) the cost for multiple copies.
D) the baseline project plan.
E) how understandable the documentation is.

D) the baseline project plan.

Which of the following are ways of validating purchased software information?
A) Reviewing software documentation and technical marketing literature
B) Sending prospective vendors a questionnaire asking specific questions about their packages
C) Using the software yourself and running it through a series of tests based on the criteria for selecting software D) Obtaining feedback from other users of the software
E) All of the above

E) All of the above

The document sent to vendors asking them to propose hardware and software that will meet the requirements of your new system is called a:
A) requirements statement.
B) request for proposal (RFP).
C) Baseline Project Plan.
D) business case.
E) systems service request.

B) request for proposal (RFP).

The use of previously written software resources is also referred to as:
A) reuse.
B) reengineering.
C) reprocessing.
D) re-analysis.
E) restructuring.

A) reuse.

Reuse typically refers to using previously written:
A) objects.
B) components.
C) documentation.
D) business cases.
E) Both A and B are correct.

E) Both A and B are correct.

Reusing software can:
A) increase the cost of software development.
B) decrease development time.
C) increase development time.
D) increase schedule overruns.
E) decrease programmer productivity.

B) decrease development time.

Which of the following is NOT a result of reuse?
A) Higher-quality software
B) Lower defect rates
C) Decreased maintenance costs
D) Higher defect rates

D) Higher defect rates

Technical issues related to reuse include all of the following EXCEPT:
A) the over-reliance on class libraries.
B) lack of a methodology for creating reusable components.
C) lack of a methodology for clearly defining reusable components.
D) the small number of reusable resources available.
E) the small number of reliable resources available.

A) the over-reliance on class libraries.

The four approaches to reuse include all of the following EXCEPT:
A) ad hoc.
B) facilitated.
C) managed.
D) designed.
E) ex ante.

E) ex ante.

The typical reuse level of facilitated reuse:
A) varies.
B) is low.
C) is high.
D) is very high.
E) is moderate.

B) is low.

The typical reuse level of designed reuse:
A) varies.
B) is low.
C) is moderate.
D) is high.
E) is none to low.

D) is high.

The relative cost of ad hoc reuse is:
A) low.
B) none.
C) moderate.
D) high.
E) extremely high.

A) low.

When an organization invests in carefully designing assets for reuse, choosing assets for domain or product line, they are said to be engaged in:
A) ad hoc reuse.
B) facilitated reuse.
C) designed reuse.
D) managed reuse.
E) ex ante reuse.

C) designed reuse.

When an organization encourages and supports use with limited resources, infrastructure, and policies to make reuse easier, they are said to be engaged in:
A) ad hoc reuse.
B) managed reuse.
C) ex ante reuse.
D) facilitated reuse.
E) designed reuse.

D) facilitated reuse.

With managed reuse, the development, sharing, and adoption of reusable assets is:
A) encouraged.
B) mandated.
C) discouraged.
D) minimal.
E) All of the above are correct

B) mandated.

For complete systems that cross functional boundaries:

Enterprise solutions vendors

When resources and staff are available and system must be built from scratch:

In-house developers

When task requires custom support and system can't be built internally or system needs to be sourced:

IT services firms

For instant access to an application:

Cloud computing

When supported task is generic:

Cloud computing & Open-source software

When supported task is generic but cost is an issue:

Open-source software

Refers to whether and how much a vendor can assist in installing the software, how much training and support is provided, and how much help can be provided to solve problems after installation:

Vendor Support

Refers to how long it takes the software package to respond to the user's request in an interactive:

Response time

Refers to the vendor's ability to remain in business:

Viability of vendor

A document provided to vendors to ask them to propose hardware and system software that will meet the requirements of your new system:

Request for proposal

Refers to how easy it is for you, or the vendor, to customize the software:

Flexibility

Refers to the tasks the software can perform and the mandatory, essential, and desired system features:

Functionality

Refers to the availability and cost of user manuals and other technical paper work associated with the software:

Documentation

Individuals find assets on their own, sharing with colleagues as they choose:

Ad Hoc Reuse

Organization enforces reuse practice through policies, resources, tools, and people:

Managed Reuse

Organization invests in carefully designing assets for reuse, choosing assets for domain or product line. Assets are designed or reengineered to fit together:

Designed Reuse

Organization encourages and supports reuse with limited resources, infrastructure, and policies to make reuse easier:

Facilitated Reuse