True/False
Indicate whether the
statement is true or false.
|
|
|
1.
|
Systems analysis is a problem-solving technique
that decomposes a system into its component pieces for the purpose of studying how well those
component parts work and interact to accomplish their purpose.
|
|
|
2.
|
Systems design is a complementary problem solving
technique to systems analysis that reassembles a system's component pieces into a (hopefully
improved) complete system.
|
|
|
3.
|
A repository is a location (or set of locations)
where systems analysts, systems designers and system builders keep the documentation associated with
one or more systems or projects.
|
|
|
4.
|
Model driven analysis emphasizes the drawing of
pictorial system models to document and validate both existing and/or proposed systems. Ultimately
the system model becomes the blueprint for designing and constructing an improved
system.
|
|
|
5.
|
Data Flow Diagrams (DFDs) can only be used to
depict proposed new processes in a system, along with their inputs, outputs and files.
|
|
|
6.
|
Objected oriented analysis (OOA) is model-driven
technique that integrates Data and Process concerns into constructs called Objects. OOA models are
pictures that illustrate the system's objects from various perspectives such as structure and
behavior.
|
|
|
7.
|
A prototype is a small-scale, incomplete, but
working sample of a desired system.
|
|
|
8.
|
Discovery prototyping is used to identify the
user's business requirements by having them react to a quick and dirty implementation of those
requirements.
|
|
|
9.
|
Many analysts use parts of structured analysis and
information engineering in a complementary way to model an information system.
|
|
|
10.
|
Rapid architecture analysis attempts to derive
system models from existing systems or discovery prototypes.
|
|
|
11.
|
Requirements discovery is the process of
identifying system problems and solution requirements from the user community.
|
|
|
12.
|
The purpose of a context diagram is to analyze how
the system interacts with the world around it.
|
|
|
13.
|
The scope definition phase is the first phase of
the classic systems development process. It is also known as initial study phase, survey phase, or
planning phase.
|
|
|
14.
|
The scope definition phase looks at the question
"Is this project worth looking at?"
|
|
|
15.
|
The final deliverable for the scope definition
phases is the project charter..
|
|
|
16.
|
A problem statements matrix lists each problem,
opportunity, or directive related to the project.
|
|
|
17.
|
Scope defines the boundary of the
project.
|
|
|
18.
|
The final deliverable of the scope definition phase
is a working prototype to demonstrate system requirements.
|
|
|
19.
|
In the scope definition phase, urgency is used to
represent what time frame the problem needs to be solved or the opportunity or directive to be
realized.
|
|
|
20.
|
In the scope definition phase, benefits are
measured in terms of how a new system could increase annual revenues, or reduce annual
costs.
|
|
|
21.
|
In the scope definition phase, possible solutions
need to be expressed in as much detail as possible so that an accurate picture of the feasibility of
the project can be determined.
|
|
|
22.
|
Developing the baseline schedule and budget is the
responsibility of the system owner.
|
|
|
23.
|
Scope can change during the life cycle of a
project, however, the initial project plan needs to establish the preliminary scope to provide a
context for the budget and schedule.
|
|
|
24.
|
The facilitator for the joint requirements planning
process determines which projects will return the most value to the organization and thus should be
approved for continued system development.
|
|
|
25.
|
The problem analysis phase is best described by the
statement, "Don't try to fix it unless you understand it."
|
|
|
26.
|
The deliverables of the problem analysis phase
include an understanding of the problem domain and business vocabulary.
|
|
|
27.
|
Cause-and-effect analysis leads to the
understanding of problems and can lead to not-so-obvious, but more creative and valuable
solutions.
|
|
|
28.
|
Cause-and-effect analysis is an out-of-date
technique that is unnecessary today given the complete nature of the scope definition phase that
makes such problems and their solutions obvious.
|
|
|
29.
|
An objective is something that will limit your
flexibility in defining a solution to your constraints. Essentially, objectives cannot be
changed.
|
|
|
30.
|
The final deliverable for the problem analysis
phase is the completion of an updated project plan, including problem analyses, any system models,
the system improvement objectives, and any other documentation that was produced during this
phase.
|
|
|
31.
|
The requirements analysis phase answers the
question, "What do the users need and want from a new system?"
|
|
|
32.
|
The final deliverable and milestone of the
requirements analysis phase is the production of a business requirements statement that will fulfill
the system improvement objectives identified in the prior phase.
|
|
|
33.
|
Security is an example of a functional
requirement.
|
|
|
34.
|
A nonfunctional requirement is a description of
other features, characteristics and constraints that define a satisfactory system.
|
|
|
35.
|
Requirements analysis never really
ends.
|
|
|
36.
|
When using timeboxing the first version of the
system to be delivered returns little immediate value to the user.
|
|
|
37.
|
Timeboxing divides the total project into subsets
that can each be delivered within a one-week time frame.
|
|
|
38.
|
The final deliverable and milestone for the
decision analysis phase is to produce a system proposal that will fulfill the business requirements
identified in the previous phases.
|
|
|
39.
|
Each candidate solution must be analyzed for
feasibility.
|
|
|
40.
|
The feasibility analysis should be stopped as soon
as the analyst identifies an ideal solution. This will save valuable time that can be put to better
use during the implementation phase.
|
|
|
41.
|
Once the feasibility analysis has been done on each
candidate solution, a comparison can now be made among all of the candidate solutions to determine
which ones to recommend to the system owners and users.
|
Multiple Choice
Identify the
choice that best completes the statement or answers the question.
|
|
|
42.
|
A system proposal may be presented as
a:
a. | report | b. | verbal presentation | c. | walkthrough | d. | all of
these | e. | none of these |
|
|
|
43.
|
Which of the following is not a category of
constraints?
a. | schedule | b. | technology | c. | priority | d. | cost | e. | policy |
|
|
|
44.
|
A problem solving technique that decomposes a
system into its component parts while focusing on the business problem independent of technology
is:
a. | systems design | b. | systems analysis | c. | cause-and-effect
analysis | d. | joint application design
(JAD) | e. | none of these |
|
|
|
45.
|
Data flow diagrams are used in:
a. | model-driven analysis | b. | traditional approaches | c. | structured
analysis | d. | object oriented analysis | e. | a, b, and c |
|
|
|
46.
|
A small-scale, incomplete, but working sample of a
desired system is:
a. | an entity relationship
diagram | b. | a prototype | c. | a data-flow diagram | d. | a unified modeling
language diagram | e. | none of
these |
|
|
|
47.
|
A committee of executive business and system
managers that studies and prioritizes competing project proposals to determine which projects will
return the most for an organization, and should be approved is:
a. | joint application committee | b. | joint requirements committee | c. | steering body | d. | prototyping
body | e. | none of these |
|
|
|
48.
|
The problem analysis phase typically includes which
of the following tasks?
a. | negotiate baseline scope | b. | establish system improvement objectives | c. | prioritize system requirements | d. | analyze candidate solutions | e. | all of these |
|
|
|
49.
|
Which of the following is NOT shown in a context
diagram?
a. | the system | b. | actors or agents | c. | system
inputs | d. | system outputs | e. | all of these are shown |
|
|
|
50.
|
Technical feasibility asks the following
question(s):
a. | Is the solution technically practical? Does the staff
have the technical expertise to design and build the system? | b. | Will the solution fulfill the users' requirements? To what degree? How
will the solution change the users' work environment? | c. | Is the solution cost-effective? | d. | Can the solution be designed and implemented within an acceptable time
period? | e. | none of these |
|
|
|
51.
|
Operational feasibility asks the following
question(s):
a. | Is the solution technically practical? Does the staff
have the technical expertise to design and build the system? | b. | Will the solution fulfill the users' requirements? To what degree? How
will the solution change the users' work environment? | c. | Is the solution cost-effective? | d. | Can the solution be designed and implemented within an acceptable time
period? | e. | none of these |
|
|
|
52.
|
Economic feasibility asks the following
question(s):
a. | Is the solution technically practical? Does the staff
have the technical expertise to design and build the system? | b. | Will the solution fulfill the users' requirements? To what degree? How
will the solution change the users' work environment? | c. | Is the solution cost-effective? | d. | Can the solution be designed and implemented within an acceptable time
period? | e. | none of these |
|
|
|
53.
|
The project plan needs to be updated during what
phase of the systems development life cycle?
a. | problem analysis phase | b. | logical design phase | c. | requirements
analysis phase | d. | decision analysis
phase | e. | all of these |
|
Completion
Complete each
statement.
|
|
|
54.
|
____________________________ is a complementary
problem solving technique to systems analysis that reassembles a system's component pieces into
a (hopefully improved) complete system.
|
|
|
55.
|
A(n) __________________________ is a location (or
set of locations) where systems analysts, systems designers and system builders keep the
documentation associated with one or more systems or projects.
|
|
|
56.
|
The processes of an object are called
_____________.
|
|
|
57.
|
_______________________________________ is a
model-driven technique that integrates data and process concerns.
|
|
|
58.
|
________________________________ techniques use
facilitated workshops to bring together all the system owners, system users, systems analysts and
some systems designers and builders to jointly perform systems analysis.
|
|
|
59.
|
_______________________________________ is the
application of systems analysis methods to the goal of dramatically changing and improving the
fundamental business processes of an organization, independent of information
technology.
|
|
|
60.
|
The _________________________________________looks
at the question "Is this project work looking at?"
|
|
|
61.
|
In the scope definition phase,
_________________________ are measured in terms of how a new system could increase annual revenues,
or reduce annual costs.
|
|
|
62.
|
A _____________ is a business scenario or event for
which the system must provide a define response.
|
|
|
63.
|
__________________________ defines the boundary of
the project – those aspects of the business that will and will not be included. Scope can
change during the life cycle of a project, however, the initial project plan needs to establish the
preliminary scope to provide a context for the budget and schedule.
|
|
|
64.
|
The _____________________________phase is best
described by the statement, "Don't try to fix it unless you understand
it."
|
|
|
65.
|
_________________________________ fall into four
categories: schedule; cost; technology; and policy.
|
|
|
66.
|
The _____________________________________ phase
typically includes prioritizing system requirements.
|
|
|
67.
|
All systems documentation is kept in a
_________________________.
|