Tracing Data Requirements

By Declan Chellar

Assumptions

• The data requirements of any software development should be based on two key artefacts: The Data Dictionary The Logical Data Model

• Recording data requirements without reference to those artefacts leads to data redundancy

• Data redundancy leads to poor physical data modelling and ultimately to poor DB performance

Assumptions

Proposal

• Just as functional requirements are traced from business need to implementation, data requirements should be traced to eliminate redundancy and ensure coverage.

• The following procedure facilitates the tracing of data requirements to their source.

Proposal

• Just as functional requirements are traced from business need to implementation, data requirements should be traced to eliminate redundancy and ensure coverage.

• The following procedure facilitates the tracing of data requirements to their source.

Proposal

Scenario 1

Scenario 2

Scenario 3

Scenario 4

Scenario 5

Scenario 6

Scenario 7

Scenario 8

Scenario 9

Scenario 10

Scenario 11

Scenario 12

For a free JPG of this flow chart, please contact me via my blog.

www.chellar.com/blog

Tracing Data Requirements

Technology

Transcript of Tracing Data Requirements