Data Doctrine® and related trademarks are the property of  Data Blueprint. All Rights Reserved.

Provided by:

* Excerpt from:  Data Strategy and the Enterprise Data Executive:  Ensuring that Business and IT are in Synch in the Post-Big Data Era by Peter Aiken & Todd Harbour

Data structures & software development must be separated and sequenced!

An example of the impact of data structure changes comes from the manner that the organizational software performs scheduling.  If job sharing is not permitted then each EMPLOYEE has one POSITION and each POSITION is filled by exactly one EMPLOYEE.  Scheduling is accomplished when an EMPLOYEE is scheduled full time (the only option) for a position.  This can be done with much less information that under conditions permitting job sharing when scheduling must be accomplished with the additional coordination complexity involving an EMPLOYEE, a POSITION, and a SCHEDULE and perhaps on a daily basis depending on the granularity of the job sharing permitted.*