It315 Midterm
It315 Midterm
2. The four phases of the Systems Development Life Cycle are _____.
a. analysis, gathering, modeling, and diagramming
b. construction, installation, testing, and converting
c. initiating, planning, controlling, and implementing
d. planning, analysis, design, and implementation
e. system request, feasibility, staffing, and construction
9. If end users feel fearful or threatened by a proposed new system, this factor
should be included as a part of the _____.
a. economic feasibility assessment
b. organizational feasibility assessment
c. system proposal
d. system request
e. technical feasibility assessment
11. Adding people to a project team in order to speed up total development time
_____.
a. is a standard task in timeboxing
b. is a useful way to meet a tight deadline
c. may actually increase total development time
d. simplifies communication within the team
e. none of the above
12. Unlike traditional Work Breakdown Structures (WBS), evolutionary WBSs are
a. organized in a standard manner across all projects
b. created in an iterative and incremental manner
c. designed so one can compare the current project to past projects
d. all of the above
e. none of the above
14. The most comprehensive and complete deliverable of the analysis phase is _____.
a. project work plan
b. system proposal
c. behavioral models for the to-be system
d. functional models for the to-be system
e. structural models for the to-be system
15. The information gathering technique that enables the analyst to collect facts and
opinions from a wide range of geographically dispersed people quickly and with
the least expense is the _____.
a. document analysis
b. interview
c. JAD session
d. observation
e. questionnaire
16. Which of the following diagramming symbols represents an actor in a use case
diagram?
a
.
b
.
c.
d
.
e.
17. Which of the following diagramming symbols represents a use case in a use case
diagram?
a.
b
.
c.
d
.
e.
18. The importance level of a use case increases for all of the following
characteristics of the use case EXCEPT _____.
a. the use case represents an important business process
b. the use case supports revenue generation
c. the technology is proven
d. the functionality is complex
e. the functionality is time-critical
19. The correct sequence of the major steps in creating use case diagrams is _____.
a. identify the major use cases, expand the major use cases, confirm the
major use cases, create the use-case diagram
b. identify the major use cases, expand the major use cases, create the use-case
diagram, confirm the major use cases
c. create the use-case diagram, identify the major use cases, expand the major
use cases, confirm the major use cases
d. create the use-case diagram, identify the major use cases, confirm the major
use cases, expand the major use cases
e. identify the major use cases, confirm the major use cases, expand the major
use cases, create the use-case diagram
20. An analyst depicts the static view of an information system with _____.
a. use-case models
b. structural models
c. behavioral models
d. interaction diagrams
e. statechart diagrams
21. Which of the following objects would be most likely to be destroyed at some
point in time in a sequence diagram?
a. customer
b. order
c. order item
d. invoice
e. shopping cart
23. Which of the following will be converted to methods in later phases of the SDLC?
a. attributes
b. operations
c. classes
d. objects
e. abstract classes
25. One way to identify objects for the class diagram is to scan the use case
descriptions for ____.
a. relationships
b. object lists
c. patterns
d. nouns
e. verbs
TRUE OR FALSE
1. Familiarity with the application and technology are major factors considered
under economic feasibility.
2. Cost benefit analysis identifies the financial costs and benefits associated with a
systems project.
3. To identify the costs and benefits related to the computer technology for a
project the systems analyst should rely on the business users.
7. Natalie has been asked by her project manager to list the possible intangible
benefits for a new system. Her list will include reduced expenses for the
company.
9. Calculating the break-even point helps in understanding how long it will take
before the system creates real value for the organization.
10. When planning a systems project, overly optimistic timetables are the cause of
project completion delays.
12. Timeboxing is a popular technique which sets a fixed deadline for a project and
delivers the system by that deadline no matter what, even if functionality needs to
be reduced.
16. Observation is a powerful tool for gathering information about the As-Is system
and may be necessary because managers often do not remember how they work
and how they allocate their time.
17. Because it is important not to disrupt the normal business function, joint
application design (JAD) sessions should be held at a location easily
accessible to the participants’ office staffs, and attendees should be those
most easily released from regular duties and least likely to be missed.
18. Jessica has asked the users to generate a list of problems with the current system
and to prioritize the problems in order of importance. Jessica then generated all
the possible causes for the problems, starting with the most important. Jessica is
identifying improvement opportunities through root cause analysis.
19. A use case that describes functionality that is complex and risky would be given a
high importance level.
20. The primary actor is the person or thing that starts the execution of a use case.
22. A formal way of representing how a business system interacts with its
environment is termed a use case.
25. A message with the information [aStudent exists] will be sent only when this
condition is true.
28. The symbol for a class in a class diagram contains the name of the class, a list of
the attributes, and a list of operations.
29. Age is an example of a derived attribute in a class since it can be computed from
the date-of-birth attribute and the current date.
SHORT ANSWER
13. List and briefly describe the four major steps in writing
effective use-case descriptions and use-case diagrams.
Guidelines for writing effective use case descriptions are:
Write each set in the form of subject verb direct object (and sometimes preposition
indirect object)
Make sure it is clear how the initiator of the step is.
Write the steps from the perspective of the independent observer.
Write each step at about the same level of abstraction.
Ensure the use case has sensible set of steps
Apply the KISS principle liberally
Write repeating instructions after the set of steps to be repeated.