Unlock document.
This document is partially blurred.
Unlock all pages and 1 million more documents.
Get Access
Essentials of Systems Analysis and Design, 6e (Valacich)
Chapter 5 Determining System Requirements
1) The two parts to systems analysis are determining requirements and structuring requirements.
projects
Classification: Concept
2) During requirements determination, information can be gathered from users of the current
system, forms, reports, and procedures.
projects
Classification: Concept
3) Information refinement means taking the system requirements you find during requirements
determination and ordering them into tables, diagrams, and other formats that make them easier
to translate into technical system specifications.
Classification: Concept
4) Assuming anything is possible and eliminating the infeasible describes the reframing
characteristic that a systems analyst should exhibit during the requirements determination phase.
projects
Classification: Concept
1
5) Finding the best solution to a business problem or opportunity describes the attention to
details characteristic that a systems analyst should exhibit during the requirements determination
phase.
projects
Classification: Application
6) Challenging yourself to look at the organization in new ways describes the impertinence
characteristic that a systems analyst should exhibit during the requirements determination phase.
projects
Classification: Concept
7) Meeting notes, procedure manuals, and consultant reports are specific deliverables that might
be obtained during the requirements determination process.
projects
Classification: Concept
8) Requirements creep is a term used to describe a project that has become bogged down in an
abundance of analysis work.
projects
Classification: Concept
2
9) Joint application design and prototyping can help keep the analysis effort at a minimum yet
still effective.
projects
Classification: Concept
10) Collection of information is at the core of systems analysis.
projects
Classification: Concept
11) Contrary to popular belief, interviewing is not one of the primary ways analysts gather
information about an information systems project.
projects
Classification: Concept
12) In order to promote more truthful responses, the general nature of the interview should not be
explained to the interviewee in advance.
projects
Classification: Concept
13) Neutrality is a guideline for effective interviewing.
projects
Classification: Concept
3
14) As a general guideline, you should prepare an agenda with approximate time limits for
different sections of the interview.
projects
Classification: Concept
15) Open-ended questions are usually used to probe for information when you cannot anticipate
all possible responses or when you do not know the precise question to ask.
projects
Classification: Concept
16) Open-ended questions can put interviewees at ease because they can respond in their own
words using their own structure.
projects
Classification: Concept
17) Open-ended questions put the interviewee at ease, are easily summarized, and save time.
projects
Classification: Concept
18) Closed-ended questions work well when the major answers to the questions are known.
projects
Classification: Concept
4
19) A major disadvantage of closed-ended questions is that useful information that does not quite
fit the defined answers may be overlooked as the respondent tries to make a choice instead of
providing his or her best answer.
projects
Classification: Concept
20) Multiple choice, rating, and ranking are types of closed-ended questions.
projects
Classification: Concept
21) You should use the interview process to set expectations about the new or replacement
system.
projects
Classification: Concept
22) Since observations are unbiased, they are preferable to other requirements determination
techniques.
projects
Classification: Concept
23) While being observed, employees may follow exact procedures more carefully than they
typically do.
projects
Classification: Concept
5
24) In documents you can find information about the values of the organization or individuals
who can help determine priorities for different capabilities desired by different users.
projects
Classification: Concept
25) In documents you can find information about special information processing circumstances
that occur irregularly.
projects
Classification: Concept
26) When performing observations, it is best to select typical people and sites as opposed to
atypical people and sites.
projects
Classification: Concept
27) As a systems analyst, it is part of your job to create a document for a missing work
procedure.
projects
Classification: Concept
28) If you encounter contradictory information about procedures from interviews, questionnaires,
or observations, you should reconcile the contradictions before proceeding to other analysis
tasks.
projects
Classification: Concept
6
29) Informal systems develop because of inadequacies of formal procedures, individual work
habits and preferences, and resistance to control.
projects
Classification: Concept
30) The most useful forms do not contain data.
projects
Classification: Concept
31) When gathering system requirements, document analysis and observation are used the least.
projects
Classification: Concept
32) When comparing observations and document analysis, the expense of observations is rated
moderate.
projects
Classification: Application
33) When comparing observations and document analysis, the chances for follow-up and probing
with document analysis are rated high to excellent.
projects
Classification: Application
7
34) When comparing observations and document analysis, the time required for document
analysis is rated as low to moderate.
projects
Classification: Application
35) The primary purpose of using JAD in the analysis phase is to collect systems requirements
simultaneously from the key people involved with the system.
projects
Classification: Concept
36) A JAD is an inexpensive, popular requirements determination technique.
projects
Classification: Concept
37) Referencing a JAD session, the sponsor is the individual responsible for organizing and
running a JAD session.
projects
Classification: Concept
38) In general, JADs benefit greatly from computer support.
projects
Classification: Concept
8
39) The goal with using prototyping to support requirements determination is to build the
ultimate system from prototyping.
projects
Classification: Concept
40) The prototyping process usually includes formal documentation of system requirements.
projects
Classification: Concept
41) Rapid process redesign is the search for, and implementation of, radical change in business
processes to achieve breakthrough improvements in products and services.
Classification: Concept
42) The idea behind BPR is to reorganize the complete flow of data in major sections of an
organization to eliminate unnecessary steps, achieve synergies among previously separate steps,
and become more responsive to future changes.
Classification: Concept
43) A first step in any BPR effort is to understand what processes need to change.
Classification: Concept
9
44) BPR efforts often result in the development of information system maintenance requests or
requests for system replacement.
Classification: Concept
45) Key business processes are the structured, measured set of activities designed to produce a
specific output for a particular customer or market.
Classification: Concept
46) Key business processes are customer focused.
Classification: Concept
47) In terms of BPR, activities deemed important, changeable, and dysfunctional are primary
candidates for alteration.
Classification: Concept
48) Disruptive technologies enable the breaking of long-held business rules that inhibit
organizations from making radical business changes.
Classification: Concept
10
