• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/12

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

12 Cards in this Set

  • Front
  • Back
Directly from the chapter. If seven blind persons examined an elephant .
they would arrive at different conclusions about what an elephant is like; in project management a team must communicate well and share their collective knowledge to avoid arriving at the wrong conclusions about their project.
Something the system must do or a characteristic it must have is a requirement.

True

BPA (Business Process Automation) approaches analysis of the IS by either problem analysis or root cause analysis. Which statement is correct about both of these approaches?
problem analysis asks the users and managers to identify problems with the as-is system and how to solve them in the to-be system; root cause analysis focuses on the problems, not the solutions (and does not treat the symptoms).

The most important purpose of the requirements definition is to define the scope of the system.

True

In Business Process Improvement, Activity-Based Costing can be described as

a process that focuses on the material and labor cost of the project. Each input is assessed for labor and material cost and the most "expensive" ones are the focus of improvement.

The current system is often referred to as the _(A)_ system; the new system is often referred to as the __(B)__ system. The identifier for this class is __(C)__ and requirements gathering is considered the most important step in the __(D)__ process.

1. as-is


2. to-be


3. CIS 305


4. SDLC

Requirements developed by the developer, and called system requirements, can be functional or nonfunctional in nature. The difference between functional and nonfunctional requirements can be described as

functional requirements relate directly to a process the system has to perform or information it needs to contain while nonfunctional requirements refer to behavioral properties that the system must have, such as performance and usability.

Requirements in design are written from the perspective of the developer and are called

System requirements

The requirements definition report, usually called the requirements definition, is a straightforward text report that simply lists the functional and nonfunctional requirements in an outline format.

True

"How many orders can a customers place?" Is an example of a(n) _____________________ question and is used to gather information about a current business process.

closed-ended

"What are some of the problems you face on a weekly basis?" Is an example of a(n) __________________ question and is a basic tool for the systems analyst.

open-ended

"Can you give me an example?" Is a _______________ question used to find out more information about a system during requirements gathering.

probing