My Paper Writer » Essay Blog » English Homework Help » English Mid-term Exam

English Mid-term Exam

Instructions:

The exam is to be completed by yourself without assistance, but you may use your book and notes.  Be sure to type your name at the top.  Clearly highlight your selected answer in green for the True/False and Multiple Choice questions.  Please type your response to each short answer immediately following the short answer question.

Each of the diagrams will be constructed in LucidChart using the modeling conventions used in the lectures.  For each diagram, download your diagram as a PDF using the menu option of File->Download As…  Submit your exam document and the PDF model documents via the D2L dropbox.  Be sure to reopen your files from D2L after submission to ensure that they work and that your models are completely visible.

 

Mid-term Exam

 

True/False (10 points – 1 point each)

 

Highlight the correct response.

 

T          F          A stakeholder is any person who has an interest in an information system.

 

T          F          A systems analyst is a specialist that only concentrates on constructing

information systems based on design specifications.

 

T          F          The Capability Maturity Model (CMM) is a framework for determining the

maturity of an organization’s information systems development and management processes.

 

T          F          Creeping commitment refers to an approach to systems development where the

feasibility of the project is review at multiple checkpoints during development.

 

T          F          A Gantt chart is less effective at communicating a schedule than a PERT chart.

 

T          F          Joint project planning only involves the technical specialists that will construct

the information system.

 

T          F          An expectations management matrix is a tool to understand tradeoffs between

knowledge, processes, and costs.

 

T          F          Scope defines what a project may or may not include.

 

T          F          In terms of system improvement objectives, constraints are measures of success

which are expected to be achieved if given sufficient resources.

 

T          F          When conducting an interview, the interviewer should avoid assuming anything

about the topic or the interviewee.

 

Multiple Choice (40 points – 2 points each)

 

Highlight one correct response:

 

A system owner is described as:

  1. A technical specialist that user requirements into technical solutions
  2. An experienced professional who plans, monitors, and controls projects.
  3. A person that interacts with the system on a regular basis
  4. A sponsor and advocate of the information system

 

The simplified system development process presented in the book consists of the following phases EXCEPT:

  1. Implementation
  2. Design
  3. Analysis
  4. Business Process Reengineering

 

Which phase of the simplified system development process is described by the specification of a technical, computer-based solution for identified business requirements?

  1. Implementation
  2. Design
  3. Analysis
  4. Business Process Reengineering

The building blocks of information systems include all of the following EXCEPT for:

  1. Communication
  2. Partnership
  3. Knowledge
  4. Processes

 

Interface specifications belong to which building block?

  1. Communication
  2. Partnership
  3. Knowledge
  4. Processes

 

Work flows are

  1. A group of related business processes that support the business
  2. Technical designs that document how system users interact with a system
  3. The flow of transactions through processes to ensure appropriate checks and approvals
  4. Representations of users’ data in terms of entities and attributes

 

 

 

 

The text asserts that the term “Problem” consists of the following, EXCEPT for:

  1. Problems
  2. Directives
  3. Suggestions
  4. Opportunities

 

A statement of work is:

  1. A categorization of problems and constraints
  2. A contract or agreement to develop an information system
  3. The physical design of an information system
  4. A logical model of an information system

 

A common phenomenon where requirements and expectations increase without regard to the impact on budget and schedule is:

  1. Work flow creep
  2. Scope creep
  3. Creeping commitment
  4. Creeping analysis

 

A project is considered a success if:

  1. The system is delivered within budget
  2. The development process had minimal impact on ongoing business operations
  3. The system is delivered on time
  4. All of the above

 

In estimating task durations, expected duration is:

  1. The estimated amount of time to complete a task
  2. The estimated amount of time required to complete a based on a weighted average of other durations
  3. The estimated maximum amount of time to complete a task
  4. The estimated minimum amount of time to complete a task

 

The application of system analysis methods with the goal dramatically changing and improving the fundamental business processes of an organization is:

  1. The agile method
  2. Rapid architected analysis
  3. Fact-finding
  4. Business process redesign

 

The purpose of the decision analysis phase is to:

  1. Identify, evaluate and select a candidate solution
  2. Decide which system development methodology to use
  3. Identify and express system requirements
  4. Negotiate baseline scope

 

When conducting an interview, you should:

  1. Use jargon to illustrate your knowledge
  2. Maintain control of the interview
  3. Record the person for later review
  4. Reveal your personal biases

 

 

A free-format questionnaire is

  1. Designed to offer respondents greater latitude in responding
  2. Contains questions that require selecting an answer from predefined responses
  3. Used in structured interviews
  4. Used in unstructured interviews

 

A primary business actor is

  1. The stakeholder that receive the primary benefits of a use case
  2. The stakeholder that directly interfaces with the system to initiate the use case
  3. The stakeholder that responds to a request from the use case
  4. The stakeholder that is not the primary actor, but still receives some benefit from a use case.

 

In use cases, an association (aka communication) relationship is:

  1. A relationship between actors created to simplify the drawing using an abstract actor to show that multiple real actors involved in a use case
  2. A relationship between use cases indicating that one use case cannot be performed until another use case has been performed
  3. A relationship between an actor and a use case in which an interaction occurs between them
  4. A relationship used to show that one use case performs a common set of steps among two or more use case that has been isolated in an abstract use case to reduce redundancy

 

In use cases, an inheritance relationship is

  1. A relationship between actors created to simplify the drawing using an abstract actor to show that multiple real actors involved in a use case
  2. A relationship between use cases indicating that one use case cannot be performed until another use case has been performed
  3. A relationship between an actor and a use case in which an interaction occurs between them
  4. A relationship used to show that one use case performs a common set of steps among two or more use case that has been isolated in an abstract use case to reduce redundancy

 

In use cases, an uses (aka includes) relationship is

  1. A relationship between actors created to simplify the drawing using an abstract actor to show that multiple real actors involved in a use case
  2. A relationship between use cases indicating that one use case cannot be performed until another use case has been performed
  3. A relationship between an actor and a use case in which an interaction occurs between them
  4. A relationship used to show that one use case performs a common set of steps among two or more use case that has been isolated in an abstract use case to reduce redundancy

 

A use case narrative is

  1. A line
  2. The act of breaking down a system into subcomponents
  3. An oval
  4. A textual description of the business event and the user will interact with the system

 

Short Answer (25 points)

 

Sentences or bulleted responses as appropriate

 

Identify each of the general problem-solving steps as defined in Chapter 1 (7 points).

 

 

 

 

 

 

 

 

 

Define the items that comprise the PIECES framework classifying problems (7 points).

 

 

 

 

 

 

 

 

 

Identify and define the two types of system requirements.  (4 points).

 

 

 

 

 

 

 

 

Identify two of the seven types of fact-finding techniques for requirements gathering defined in the text.  Then compare and contrast 3 different aspects of the techniques in terms of advantages and disadvantages.  (7 points)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PERT Chart (10 points)

 

Draw a PERT Chart for the following project activities and answer the questions that follow.   Use the symbols from the legend in your PERT Chart.

 

Legend:

 

 

 

Project Activities:

 

Activity                       Precedence                  Duration (Days)

A                                 –                                   4

B                                 –                                   3

C                                 –                                   7

D                                 A                                 9

E                                  B                                 6

F                                  C                                 8

G                                 D,E                              2

H                                 F                                  4

 

 

Questions:

  1. Identify each path and its total duration.

 

 

 

 

 

 

 

 

 

 

 

  1. Identify the critical path and explain its implications for this project.

 

 

 Use Case Diagram (15 points)

Draw a use case diagram for the system description below:

Our chain of pharmacies is considering implementing a self-service checkout system, called SelfCheck in order to reduce the staff required to man the cash registers.  With the resources freed up by the automated checkouts, our goal is to add more pharmacy technicians to improve satisfaction with the prescription-filling process.  All the ways that the SelfCheck system can be used are described below.

 

SelfCheck allows a customer to scan an item.  The customer initiates this action by running the barcode of the item over the barcode reader.  The system records what item was purchased, for what amount, etc.

 

Our pharmacies have a customer loyalty program that uses the little keychain cards like many grocery stores.  SelfCheck is built to handle this and a customer may scan their membership card to tell the system to invoke membership benefits and discounts.  They will receive the same membership benefits as checking out as they would at a regular register.

 

Of course, the customers will need to pay for the items they have purchased.  They tell the system when they are done scanning and need to pay.  They indicate the payment method and provide cash, check, or credit card as appropriate.

 

We pride ourselves on responsive service.  One of the things we like about SelfCheck is that it allows the customer to request help at any time during the checkout process.  The customer presses a help button and the clerk will receive a notification that the customer needs help.

 

One of the features that our management requires is the system produces a statistical report.  SelfCheck automatically generates the statistical report on a weekly schedule and sends the report to the pharmacy manager by e-mail.  These reports will help our management determine the adoption rate of SelfCheck and determine if the project will be considered successful.

 

Last Updated on March 13, 2019

Don`t copy text!