Requirements-driven Data Engineering

Abstract

In the early 1990s, the effectiveness and efficiency of the information systems (IS) supporting the US Department of Defense's non-combat operations was questioned.  As had many organizations, the support had evolved into multiple, redundant, unintegrated, undocumented, stove-piped IS.  These systems require unnecessarily large non-combat IT expenses, supporting war fighting efforts.  Lack of integration hindered the Department from effectively providing mission support information.  DOD's efforts to re-engineer the non-combat IS is one of the first attempts to apply requirements-driven data engineering to a large systems environment.  Its application to DOD's non-combat IS data environment has provided tangible results: (1) from the top down, an enterprise model (EM) now specifies Department-wide requirements capable of guiding future integration and development efforts; (2) from the bottom-up, non-cobat IS are being significantly reduced, simplifying the overall problem; and (3) data quality engineering methods, guided by the EM, are being developed and applied to the remaining IS.  This success has achieved a prerequisite necessary to increase the effectiveness and efficiency of the systems.

Reference

Aiken, P.H., Yoon, Y., and Leong-Hong, B., Requirements-driven Data Engineering.  Information & Management February 1999 35(3):155-168.

Access

Before viewing the entire article, please provide just a bit of information about yourself and your organization:

First Name: 
Last Name:
Title:
Company:
E-mail:

 

Check this box to opt-out of our mailing list for Data-Ed Online, our monthly data management webinars.  You will always have the option to out-out of our announcements.

Disclaimer:

This information is obtained only for its intended use.  Data Blueprint will not share your information with 3rd parties.  Click here to view our privacy policy.