Multiple Choice Answers

1. Management skills:
help you work with end users, as well as other analysts and programmers.
help you understand the potential and the limitations of information technology.
help you manage projects, resources, risk, and change.
enable you to understand the organization and its functions, to identify opportunities and problems, and to analyze and solve problems.
none of the above.

2. The process of developing and maintaining an information system best describes:
joint application design.
prototyping.
information systems analysis and design.
information technology infrastructure development.
systems implementation.

3. (TCO 3) Which of the following is not an approach to systems development? (Points : 5)
Prototyping.
Agile Methodologies.
Joint application design.
Re-engineering analysis.
Rapid application development.

4. Which of the following is not a true statement?
An object’s behavior depends on its state and the operation being performed.
An object’s state is determined by its attribute values and links to other objects.
An operation is simply an action that one object performs upon another in order to get a response.
An object’s state and behavior are packaged separately.
An object has a state and exhibits behavior through operations that can examine or affect its state.

5. An individual with a diverse set of skills–management, leadership, technical, conflict management, and customer relationship–who is responsible for initiating, planning, executing, and closing down a project best defines:

chief information officer.
consultant.
project scheduler.
project manager.
end user.

6. Which of the following is not a project management phase?
Closing down the project
Planning the project
Executing the project
Initiating a project
Implementing the project

7. The concept of comparing present cash outlays to future expected returns best defines:
cost/benefit analysis.
internal rate of return.
time value of money.
investment return analysis.
monetary futures analysis.

8. A supplier of auto parts to your company would be represented on a data-flow diagram as a:

process.
source.
data flow.
data store.
relationship.

9. The analysis of documents can help you identify:
problems with existing systems.
special information processing circumstances that occur irregularly and may not be identified by any other requirements determination technique.
the reason why current systems are designed the way they are.
the organizational direction that can influence information system requirements.
all of the above.

10. The term that refers to systems development projects bogged down in an abundance of analysis work is: information overload.
analysis paralysis.
analysis overload.
information abundance.
disruptive analysis.

11. During physical design, you consider:
the definitions of each attribute.
the descriptions of where and when data are entered, retrieved, deleted, and updated.
the expectations for response time and data integrity.
the descriptions of the file and database technologies to be used.
all of the above.

12. The most common style for a logical database model is the:
relational database model.
hierarchical database model.
network database model.
object-oriented database model.
hybrid database model.

13. The conservation of inputs and outputs to a data-flow diagram process when that process is decomposed to a lower level defines:

decomposition.
balancing.
flow conservation.
data flow structuring.
gap proofing.

14. The most common format used for data modeling is:
state-transition diagramming.
entity-relationship diagramming.
process modeling.
logic modeling.
a flowchart.

15. The document sent to vendors asking them to propose hardware and software that will meet the requirements of your new system is called a:
requirements statement.
request for proposal (RFP).
baseline project plan.
business case.
systems service request.

16. Shaping alternative system design strategies involves:
enumerating different potential implementation environments.
proposing different ways to source or acquire the various sets of capabilities for the different implementation environments.
dividing requirements into different sets of capabilities.
all of the above.
none of the above.

17. On a use-case diagram, an actor can represent:
a hardware device.
another system.
a human.
an organization.
all of the above.

18. Which of the following describes agile methodologies?
Simple design and continuous refactoring are excellent for highly dynamic environments but are a source of potentially expensive rework for highly stable environments.
Methods evolved to handle highly critical products.
Methods evolved to handle large products and teams.
Needs a critical mass of scarce experts during project definition but can work with fewer later in the project, unless the environment is highly dynamic.
Thrives in a culture where people feel comfortable and empowered by having their roles defined by clear practices and procedures.

19. The primary deliverable from the conceptual data-modeling step within the analysis phase is:
a state-transition diagram.
an entity-relationship diagram.
a context data flow diagram.
a decision table.
structured English.

20. Which of the following is an example of a form?
Invoice.
Pie chart.
Mailing labels.
An electronic spreadsheet.
Weekly sales summaries by region and salesperson.

21. Changes made to a system to repair flaws in its design, coding, or implementation describes:
corrective maintenance.
adaptive maintenance.
preventive maintenance.
perfective maintenance.
programmatic maintenance.

21. Activities occurring within maintenance include:
transforming requests into changes.
obtaining maintenance requests.
implementing changes.
designing changes.
all of the above.