Fill This Form To Receive Instant Help
Homework answers / question archive / Utah State University ACCT 610 Chapter 14-Construct, Deliver, and Maintain Systems Projects TRUE/FALSE 1)The detailed design phase of the Systems Development Life Cycle is a linear process with each of five steps occurring once and in its proper sequence
Utah State University
ACCT 610
Chapter 14-Construct, Deliver, and Maintain Systems Projects
TRUE/FALSE
1)The detailed design phase of the Systems Development Life Cycle is a linear process with each of five steps occurring once and in its proper sequence.
a. |
prototypes do not include internal control features |
b. |
a prototype is an inexpensive, simplified model of a system |
c. |
a throwaway prototype is discarded after the requirements are established |
d. |
systems designers always discard prototypes and do not develop them into finished systems |
a. |
is commercially available software |
b. |
reduces the productivity but increases the quality of the work of systems professionals |
c. |
expedites the System Development Life Cycle |
d. |
consists of upper and lower tools |
a. |
the program code |
b. |
user prototype screens |
c. |
data flow diagrams |
d. |
all of the above |
a. |
conceptual level |
b. |
context level |
c. |
intermediate level |
d. |
elementary level |
a. |
context level |
b. |
elementary level |
c. |
intermediate level |
d. |
prototype level |
a. |
presents an overview model of the primary transactions processed |
b. |
graphically depicts the iceberg effect |
c. |
presents a model of the program code that constitutes the physical system |
d. |
is prepared by the systems analyst |
a. |
it facilitates the auditors review of the system |
b. |
it ensures that firm will use a specific CASE tool and vendor |
c. |
it forces all system changes to be made through the data flow diagrams |
d. |
it reduces the analysis required in designing the system |
a. |
the programmer must thoroughly review the program code |
b. |
changes should be made directly to the structure diagram |
c. |
significantly less time is required compared to maintenance activities for a system developed without using Computer Aided Software Engineering (CASE) tools |
d. |
the need for testing the modified application is eliminated |
a. |
the ability to easily revise the model during the development stage |
b. |
the requirement that all program code and documentation be regenerated for each module |
c. |
the cost of software engineering programs |
d. |
user involvement is restricted to final stages of development |
a. |
source code produced by CASE tools is less efficient than code written by a skilled programmer |
b. |
alternative designs cannot be reviewed prior to implementation |
c. |
system users are reluctant to become involved with the CASE approach |
d. |
maintenance costs are increased |
|
a. |
is a top-down approach |
b. |
is documented by data flow diagrams and structure diagrams |
c. |
assembles reusable modules rather than creating systems from scratch |
d. |
starts with an abstract description of the system and redefines it to produce a more detailed description of the system |
a. |
this approach does not require input from accountants and auditors |
b. |
development time is reduced |
c. |
a standard module once tested does not have to be retested until changes are made |
d. |
system maintenance activities are simplified |
a. |
an object |
b. |
an attribute |
c. |
an operation |
d. |
a class |
a. |
Ms. Andrews is an instance in the object class accounts receivable |
b. |
the amount Ms. Andrews owes the Edsell Company is an operation |
c. |
determining the amount past due is an attribute |
d. |
the object class accounts receivable inherits all the attributes of Ms. Andrews |
a. |
objects possess two characteristics–attributes and instances |
b. |
an instance is a logical grouping of individual objects |
c. |
inheritance means that each object instance inherits the attributes and operations of the class to which it belongs |
d. |
operations performed on objects always change attributes |
a. |
a single change to an attribute or operation in one object class is automatically changed for all the object instances and subclasses that inherit the attribute |
b. |
each module can inherit from other modules the attributes and operations it requires |
c. |
the entity relationship diagram is used to create a program which can be used in other systems |
d. |
the control module must be recreated for each program |
c. |
a user representative |
d. |
the system designer |
|
a. |
backbone system |
b. |
vendor-supported system |
c. |
benchmark system |
d. |
turnkey system |
a. |
can be installed faster than a custom system |
b. |
can be easily modified to the user’s exact specifications |
c. |
is significantly less expensive than a system developed in-house |
d. |
is less likely to have errors than an equivalent system developed in-house |
a. |
a detailed review of the source code |
b. |
contact with user groups |
c. |
preparation of a request for proposal |
d. |
comparison of the results of a benchmark problem |
a. |
fully documented system report |
b. |
systems selection report |
c. |
detailed system design report |
d. |
systems analysis report |
a. |
input screen formats |
b. |
alternative conceptual designs |
c. |
report layouts |
d. |
process logic |
a. |
completeness |
b. |
summarization |
c. |
conciseness |
d. |
relevance |
b. |
accuracy and timeliness |
c. |
relevance and summarization |
d. |
completeness and exceptions orientation |
|
a. |
summarization |
b. |
timeliness |
c. |
conciseness |
d. |
exception orientation |
a. |
a paper audit trail is maintained |
b. |
economies of scale in data collection are avoided |
c. |
input errors are reduced |
d. |
a point-of-sale terminal is required |
a. |
the form is a standard size |
b. |
the source document and the input screen are identical |
c. |
instructions use active voice |
d. |
sufficient copies of the form are prepared |
a. |
errors caused by transcription are reduced |
b. |
calculations are automatically performed on intelligent forms |
c. |
many data entry errors are detected and corrected immediately |
d. |
workers who use direct data input forms must be highly trained and skilled |
a. |
loosely coupled modules are independent of other modules |
b. |
cohesive modules perform a single, well-defined task |
c. |
maintenance of a module with weak cohesion is simple |
d. |
an error made in a tightly coupled module will affect other modules |
a. |
occurs in the implementation phase of the Systems Development Life Cycle |
b. |
expresses the detailed logic of the module in programming language |
c. |
discourages end users from becoming actively involved in designing the system |
d. |
permits individuals with few technical skills to understand the logic of the module |
b. |
occurs just after system implementation |
c. |
simulates the operation of the system in order to uncover errors and omissions |
d. |
reduces costs by reducing the amount of reprogramming |
a. |
systems designers and programmers |
b. |
end users |
c. |
accountants |
d. |
all of the above require systems documentation |
a. |
structure diagrams |
b. |
overview diagram |
c. |
system flowchart |
d. |
program flowchart |
a. |
run schedule |
b. |
logic flowchart |
c. |
file requirements |
d. |
explanation of error messages |
a. |
a list of users who receive output |
b. |
a program code listing |
c. |
a list of all master files used in the system |
d. |
a list of required hardware devices |
a. |
decomposing the system |
b. |
validating the database |
c. |
reconciliation of new and old databases |
d. |
backing up the original files |
a. |
cold turkey cutover |
b. |
phased cutover |
c. |
parallel operation cutover |
d. |
data coupling cutover |
a. |
Relationships are the degree of association between two entities. |
b. |
Attributes are data that describe the characteristics or properties of entities. |
c. |
Entities are resources, events, or agents involved in the business. |
d. |
Modeling is the task of formalizing the data requirements of the business process as a physical model. |
.
:
.
Already member? Sign In