Consider requirements definition and system design Issues for Archived Data Management Systems.
Experience from six Archived Data Management Systems case studies.
Seattle,Washington,United States; Maricopa County ,Arizona,United States; Minnesota,United States; Detroit,Michigan,United States; California,United States
During the planning and design phases of archived data management systems (ADMS), there are a number of issues that transportation agencies need to consider to ensure the success of their project. Based on the experience of the six sites profiled in this study, the following set of lessons learned highlight key issues regarding the requirements definition and system design phases of ADMS projects.
- Define the audience that will be the main system users so as to understand their data and application needs. The Minnesota TMC’s database format is structured to facilitate query response to support a broad range of users and applications. Data formats used by the system therefore include commercially available relational database applications. Moreover, system developers focused on ensuring that all data are centralized and distributed via the Internet (though individual applications could be distributed or localized).
- Teach engineers and planners that are helping to define ADMS applications to think "outside the box" to derive maximum benefit from the system. However, be prepared to provide boundaries as users may ask for capabilities they will rarely, if ever, use.
- Consider that some database formats may be easy to manage and inexpensive initially, but may require a high level of programming support which is expensive.
- Address firewall and security issues as early as possible.
- Use commercially available or open source software over proprietary or custom designed systems. Early ADMSs such as Washington State TRAC and Minnesota TMC have a history of sharing software code with other public sector ADMS developers. Sharing of code may result in development of a set of standard practices to assure that minimum quality standards are addressed. The Maricopa County RADS will rely largely on open source software to address data collection. Open source software is well suited for the wide variety of data types that the Maricopa County RADS is expected to store and process. The system will collect data via the Internet, CD-ROMs, or dedicated landlines, depending upon the agency providing the data.
- Develop a configuration plan for system software and hardware.
- Ensure proper documentation of software (especially if university students are used for software development)
- Include mapping tools in requirements developed for applications.
- Bring maintenance staff into the process early and develop coordination procedures to ensure the loop functionality will be preserved
Published By: U.S. DOT Federal Highway Administration
Source Date: December 2005
EDL Number: 14128
Other Reference Number: FHWA-JPO-05-044URL: http://ntl.bts.gov/lib//jpodocs/repts_te//14128.htm
RITA/Volpe National Transportation Systems Center
Average User Rating