Chapter 5

   
1:

Why are interviews important?

A1:

Interviews are important because they provide a valuable communication link between you (the developer) and the people for whom you're designing the database. They help ensure the success of your design efforts, and they provide critical information that can affect the design of the database structure.

2:

What problem can arise when you conduct an interview with a large number of people?

A2:

The problem that arises when you conduct an interview with a large number of people is that the intimidation level of some of the participants will rise in direct proportion to the number of participants taking part in the interview as a whole.

3:

What is the primary reason for conducting separate interviews with users and management?

A3:

The primary reason for conducting separate interviews with users and management is that each group has a different perspective on the organization as a whole and on how the organization uses its data on a daily basis.

4:

True or False: You'll commonly use closed questions in your interviews.

A4:

False. You'll commonly use open -ended questions in your interviews.

5:

What kind of responses should you try to evoke from the interview participants?

A5:

You should try to elicit complete, descriptive responses from the interview participants.

6:

What is the single most important guideline for every interview you conduct?

A6:

The single most important guideline for every interview you conduct is to always maintain control of the interview.

7:

What is a mission statement ?

A7:

A mission statement declares the specific purpose of the database in general terms.

8:

State two characteristics of a well-written mission statement.

A8:

A well-written mission statement is unambiguous, succinct and to the point, and free of phrases or sentences that explicitly describe specific tasks .

9:

True or False: You need not learn about the organization in order to compose a mission statement.

A9:

False. You must learn about the organization in order to compose a mission statement.

10:

When is your mission statement complete?

A10:

Your mission statement is complete when you have a sentence that describes the specific purpose of the database and that is understood and agreed upon by everyone concerned .

11:

What is a mission objective?

A11:

A mission objective is a statement that represents a single, general task supported by the data maintained in the database.

12:

State two characteristics of a well-written mission objective.

A12:

A well-written mission objective is a declarative sentence that clearly defines a general task and is free from unnecessary details. It is expressed in general terms, is succinct and to the point, and is unambiguous.

13:

True or False: You should interview users and management to help you define mission objectives.

A13:

True. You should interview users and management to help you define mission objectives.

14:

How does the staff's daily work relate to the mission objectives?

A14:

The staff's daily work relates to the mission objectives in that many of the tasks they perform will become mission objectives.

15:

True or False: A mission objective can describe more than one task.

A15:

False. A mission objective cannot describe more than one task.

16:

State two ways that a mission objective can be derived from a response.

A16:

A mission objective can be derived from a response either explicitly or implicitly.

17:

When is a mission objective complete?

A17:

A mission objective is complete when it is both properly defined and well defined, and when it makes sense to you and to those for whom you are designing the database


   
Top


Database Design for Mere Mortals[c] A Hands-On Guide to Relational Database Design
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design
ISBN: 0201694719
EAN: 2147483647
Year: 2002
Pages: 203

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net