tracing data requirements

Post on 03-Sep-2014

1.294 Views

Category:

Technology

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

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.

TRANSCRIPT

Tracing Data Requirements

By Declan Chellar

© Declan Chellar 2011

Assumptions

© Declan Chellar 2011

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

© Declan Chellar 2011

• 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

© Declan Chellar 2011

• 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

© Declan Chellar 2011

• 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

© Declan Chellar 2011

• 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

© Declan Chellar 2011

Proposal

© Declan Chellar 2011

• 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

© Declan Chellar 2011

• 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

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Tracing Data Requirements

© Declan Chellar 2011

Scenario 1

© Declan Chellar 2011

Scenario 2

© Declan Chellar 2011

Scenario 3

© Declan Chellar 2011

Scenario 4

© Declan Chellar 2011

Scenario 5

© Declan Chellar 2011

Scenario 6

© Declan Chellar 2011

Scenario 7

© Declan Chellar 2011

Scenario 8

© Declan Chellar 2011

Scenario 9

© Declan Chellar 2011

Scenario 10

© Declan Chellar 2011

Scenario 11

© Declan Chellar 2011

Scenario 12

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

www.chellar.com/blog

top related