. . . Database development featuring Microsoft Access

Call 512-202-7121

For Free Consultation


What Are Database Requirements?

Well Stated Project Requirements Help Develop Your Database

Defining Requirements And How They Work

Database requirements

A requirement is a specification that informs the developer what should be included or implemented in a database application.

Here are some example Access database requirements:

  • A user driven feature: "The user must be able to include a total of each salesperson's sales."
  • A system property: "There should be a login form and limits as for user rights."
  • A application constraint: "All code must include error trapping."

We help you create your Requirements Specificiations with our Database Planning Phase for your project; find out more at . . .

+ How the Database Planning Phase works for you.

Here are some examples of statements that are NOT application requirements:

  • This description is too ambiguous: "Build an Inventory Program."
  • Database program constraint: "The parts table must have a many-to-one relationship to the vendor table."

In the examples above, an "Inventory Program" does not have enough detail to meet the definition of a requirement. Baically, there is no way to adequately define the inventory program. Abstract statements do not have enough detail to allow for testing whether the requirement is completed. In this instance reform the statement into a series of smaller requirements. For example, a requirement for the inventory system could be: "The application should store vendor and parts data for all incoming shipments."

The second example is not accurate because a requirement is designed with the user in mind, and should address a problem, issue or need. A requriement is not designed around the programming language.

Requirements Are Designed For The Program User

Because requirements are "user specific" means that developers should not be given the responsibility of creating the program requirements. An application developer typically does not know the user's business environment or industry. Requirements are best developed from input from users and developers should continously ask "What do you want the final application to do for you?"

As a business owner, project leader, or database user, be prepared to articulate as precisely as possible what your database program should include. A truly robust database application is the result of a good interaction and continous communication between developer and users.

Do you need instant help? Call us at 512-202-7121 for rapid service.