Part A:

Question 1. When developing information systems, an organization could use:

• an information technology services firm.
• open-source software.
• cloud computing.
• in-house development.
• all of the above.

Question 2. The practice of turning over responsibility of some or all of an organization's information systems applications and operations to an outside firm is referred to as:

• realignment.
• downsizing.
• outsourcing.
• time sharing.
• system reassignment and deployment.

Question 3. Identifying, assessing, and managing the risks and day-to-day changes that occur during a project best defines which of the following project manager activities?

• Conflict management
• Risk and change management
• Team management
• Customer relations
• Technical problem solving

Question 4. 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

Question 5. Which of the following would be classified as an intangible cost?

• Hardware costs
• Labor costs
• Employee morale
• Operational costs
• Internet service setup fee

Question 6. The primary deliverable from the project identification and selection phase is:

• a context data flow diagram.
• at least three substantively different system design strategies for building the replacement information system.
• the development of a new version of the software and new versions of all design documents.
• an entity relationship diagram.
• a schedule of specific IS development projects.

Question 7. 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.

Question 8. Good interview guidelines consist of:

• phrasing the question to illicit the correct response.
• typing your notes within two weeks of the interview.
• establishing expectation levels about the new system.
• seeking a variety of perspectives from the interviews.
• using as much time as you need.

Question 9. The search for, and implementation of, radical change in business processes to achieve breakthrough improvements in products and services best defines:

• joint application design.
• rapid application development.
• structured programming.
• business process reengineering.
• disruptive design.

Question 10. The purpose of requirements structuring is to:

• enable the analysts to gather information on what the system should do from as many sources as possible.
• enable the analysts to develop a baseline project plan quickly.
• enable the large amount of information gathered during requirements determination to be organized.
• enable the analysts to identify several feasible alternatives.

Question 11. The diagram that shows the scope of the system, indicating what elements are inside and outside the system, is called a:

• context diagram.
• level-2 diagram.
• referencing diagram.
• representative diagram.
• decomposition diagram.

Question 12. The number of instances of entity B that can (or must) be associated with each instance of entity A refers to:

• cardinality.
• domain.
• ternary occurrence.
• participation level.
• join level.

Question 13. 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.

Question 14. Which of the following are general guidelines for displaying tables and lists?

• All columns and rows should have meaningful labels.
• Place a blank line between every five rows in long columns.
• Use the same family of typefaces within and across displays and reports.
• Allow white space on printed reports for the user to write notes.
• All of the above are guidelines for displaying tables and lists.

Question 15. Which of the following is a guideline for displaying text?

• Use double spacing if space permits.
• Do not hyphenate words between lines.
• Left-justify text and leave a ragged right margin.
• Display text in mixed upper and lowercase and use conventional punctuation.
• All of the above are guidelines for displaying text.

Question 16. Reversing the sequence of one or more characters in a field is called:

• transposing.
• transcripting.
• appending.
• truncating.
• hashing.

Question 17. A notation that allows the modeler to specify, visualize, and construct the artifacts of software systems, as well as business models, best defines:

• Unified Modeling Language.
• Structured English.
• pseudocode.
• logic modeling.
• structured design.

Question 18. Benefits of the object-oriented modeling approach include:

• the ability to tackle more challenging problem domains.
• improved communication among users, analysts, designers, and programmers.
• reusability of analysis, design, and programming results.
• increased consistency among the models developed during object-oriented analysis, design, and programming.
• all of the above.

Question 19. System documentation that is part of the program source code or is generated at compile time best defines:

• system documentation.
• user documentation.
• internal documentation.
• external documentation.
• embedded documentation.

Question 20. User testing of a completed information system using simulated data refers to:

• acceptance testing.
• alpha testing.
• beta testing.
• system testing.
• stub testing.

Part B:

Question 1. Describe the role of a systems analyst.

Question 2. Discuss the six major categories of feasibility.

Question 3. Identify and describe the traditional methods for determining requirements.

Question 4. What is gap analysis? Why is gap analysis useful?

Question 5. Contrast data modeling to process modeling and logic modeling.

Question 6. Suppose that an analysis team did not generate alternative design strategies for consideration by a project steering committee or client. What might the consequences be of having only one design strategy? What might happen during the oral presentation of project progress if only one design strategy is offered?

Question 7. Describe the three-step process for designing dialogues.

Question 8. What is meant by Agile Methodologies? Identify the three key principles that the Agile Methodologies share.

Question 9. Describe four types of installation.

Question 10. Describe four types of maintenance.