Data Integration Buyer's Guide

9 Key Data Integration Questions to Ask: A Hidden How-To Guide

9 Key Questions to Ask When Tackling Data Integration

9 Key Questions to Ask When Tackling Data IntegrationDeep within the US Department of Transportation Federal Highway Adminstration Transportation Performance Management Resources Website (the USDoTFHWATPMRW) there is a remarkable and comprehensive primer of Data Integration. This How-to-Integrate-Data Guide discusses a wide range of topics including everything from Requirements Analysis to Data and Process Flow Modeling as well as Data Models and Data Standards.

It also contains a list of 9 Key Questions to ask when analyzing existing data and database systems within an organization might include:

  1. Where do the data come from and who collects it?
  2. How often, and how, are the data collected?
  3. What reference system or systems are used?
  4. What is the structure, format, and size of the data?
  5. How are the data currently transmitted, processed and stored?
  6. What is the general quality of the data? Is it accurate? Complete? Recent? Unique or redundant?
  7. How are the data used-in what business processes?
  8. What applications draw data from the databases (e.g., bridge management system, pavement management system)?
  9. What types of reports are produced currently? What types are needed?

Download Link to Data Integration Buyer's Guide

It concludes with the following summary: “This Primer describes requirements analysis, data and process flow modeling, alternatives evaluation, detailed database design, software development, and implementation. Application of each of these methodologies help ensure the most successful possible outcome for a data integration initiative. Within various stages of this complex process, a few general guidelines serve an agency well:”

  • Use a data environment that best supports making changes in database functions or adding new data sets.
  • Adopt an incremental development approach to assure the maximum flexibility for inevitable change and evolution, and to provide sufficient time to test and upgrade integrated databases.
  • Involve database users in every stage of design and development to benefit from their input and to assure their cooperation and buy-in.
  • Select hardware and software that meet the goals of data users, the agency, and the database management system.

Widget not in any sidebars

Share This

Related Posts