Requirement Analysis

• Requirement Analysis


  is the stage in the design cycle when you find out everything you can about the data the client needs to store in the database and the conditions under which that data needs to be accessed
• is to gather every bit of information needed to design a database that meets the informational needs of an organization


  Purpose of Requirement Analysis
• ·Examine the existing database(s)

  ·Conduct user interviews

  ·Create a data flow diagram (if needed)

  ·Determine user views

  ·Document all findings


  Related tasks in requirement analysis purpose
• - To determine the data requirements of the database in terms of primitive objects

  - To classify and describe the information about these objects

  - To identify and classify the relationships among the objects

  - To determine the types of transactions that will be executed on the database and the interactions between the data and the transactions

  - To identify rules governing the integrity of the data


  Goals of the requirements analysis
• - Review of existing documents:

  - Interviews with end users:

  - Review of existing automated systems:


  Information needed for the requirement analysis can be gathered in several ways:
• Business objects


  - are things (both tangible and intangible) in a business environment that are related, and about which data is (or needs to be) stored.
• Business Rules


  - describe the business policies that apply to the data stored on a company's databases. In other words, business rules reflect how a business perceives its use of data.

  - are especially important to the database designer because they can be incorporated into the logical schema of the database.
• Field constraints within tables

  Relationship constraints between tables


  2 Categories of Business Rules