<
logo for information-management-architect.com
leftimage for information-management-architect.com

Data Requirements

Improve requirements gathering process with David Bowman’s information management guidelines for data requirements

This site is designed for Information Technology professionals who need  to improve efficiency and require guidance and direction to help teams consistently produce error free results.

It provides a checklist of information management guidelines for data  requirements.

What is a Requirements Specification?

A data warehouse requirements specification states the project objectives and goals and related data storage, data integration, information delivery, security, quality, usage, functional and non-functional requirements that must be delivered in order to achieve the project objectives.

The requirements specification provides a means of specifying all requirements and the criteria that will be used to accept that the requirements have been met.

It helps ensure that the technical team does not design and build something that is not specified.

Conceptual Data Model
  • Should provide an appreciation for the overall scope of data storage requirements;
  • Should include definitions of each conceptual entity;
  • Should confirm understanding of the project data storage scope;
  • Should be a sub-set of the enterprise conceptual data model;
  • Should involve data modeling sessions with selected stakeholders;
  • Should involve feed-back sessions to introduce the conceptual data model; and
  • Should be approved before commencing logical data modeling.
Logical Data Model
  • Should finalize structure and design requirements;
  • Should involve data modeling sessions with selected stakeholders;
  • Should document entity definitions;
  • Should document entity attributes;
  • Should document storage volumetric requirements;
  • Should list any known issues with the logical data model;
  • Should be the subject of an internal team review; and
  • Should be approved before finalizing requirements specification.
Backup and Recovery
  • Should define backup and recovery requirements to achieve service level agreements in the event of operational, non-catastrophic, failure;
  • Should involve facilitating working sessions with selected stakeholders to discuss backup/recovery requirements;
  • Should be the subject of an internal team review; and
  • Should be approved before finalizing requirements specification.
Disaster Recovery
  • Should define backup and recovery requirements to achieve service level agreements in the event of operational, non-catastrophic, failure;
  • Should involve facilitating working sessions with selected stakeholders to discuss backup/recovery requirements;
  • Should be the subject of an internal team review; and
  • Should be approved before finalizing requirements specification.
Summary…

A data warehouse requirements specification states the project objectives and goals and related data storage, data integration, information delivery, security, quality, usage, functional and non-functional requirements that must be delivered in order to achieve the project objectives.

The requirements specification provides a means of specifying all requirements and the criteria that will be used to accept that the requirements have been met.

It helps ensure that the technical team does not design and build something that is not specified.

This site provided a checklist of information management guidelines for data requirements