Explain the iterative nature of the database requirements phase. ...

[j.rubin]

Explain the iterative nature of the database requirements phase.
 
  What will be an ideal response?

Question 2

Give an example of the type of decision that would be made by an Operational Manager?
 
  What will be an ideal response?

[ciecieme]

Answer to Question 1

The guidelines and methods for the database requirements phase call for an iterative process. A smaller beginning set of requirements can be collected, defined, and visualized, and then discussed by the database developers and intended end users. These discussions can then lead into another iteration of collecting, defining, and visualizing requirements that gradually increases the first set of requirements. Even when a set of requirements is agreed upon within the database requirements collection, definition, and visualization steps, it can still be subject to change initiated by the other steps in the database development process. Instead of mandating the collection, definition, and visualization of all database requirements in one isolated process, followed by all other steps in the development of the database systems, the common recommendation is to allow refining and adding to the requirements after each step of the database development process. For example, a common practice in database projects is to collect, define, and visualize an initial partial set of requirements and, based on these requirements, create and implement a preliminary partial database model. This is followed by a series of similar iterations where the additional requirements are added (collected, defined, and visualized) and then used to expand the database model. The requirements can also be altered iteratively when other steps, such as the creation of front-end applications or actual database use, reveal the need for modifying, augmenting, or reducing the initial set of requirements.

Answer to Question 2

Students should provide an example that is consistent with the idea that Operational Managers use predetermined rules that usually have predictable outcomes, e.g., dismissing an employee for reporting to work late three times in a week.