Click for next page ( 37

The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 36
36 Guide for Implementing a Geospatially Enabled Enterprise-wide Information Management System Detailed Design Before starting the software coding, you will establish the detailed design. Designers will review and confirm requirements with the agency project manager and work group and encapsulate them through the following: Conventions for graphical user interfaces Input screens Output screens and standard reports Navigation procedures Database design Geospatial functionality Interfaces to other systems The basis for the last three items are included in the 8-55A logical model but actual requirements associated with the systems that exist in your agency need to be specified and incorporated in the design. Test Plan You will need a test plan to evaluate the system as it is operationalized. In addition to the standard alpha and beta testing of the phase being implemented, you can also include testing at milestones that were identified when you defined the system. The following types of tests can be included: Unit testing for testing components that are being built Integration testing for testing how components work together System testing to ensure that the system meets business needs Acceptance testing to evaluate user satisfaction Scenario testing to ensure that the system meets user needs Most development environment software includes the ability to build these tests into the development process. It may be worth the time and resources to include time for staff to work with developers during the later testing, but prior to the alpha testing of the system as a whole. In the test plan, you will want to establish a method to document successful and unsuccessful tests and to capture comments during the process. Project creep can rapidly absorb allocated resources if you do not carefully control the evaluation of what was included in the design versus what "would be nice to have." For contracted development, the contractor is responsible, at its expense, to ensure the system meets design specifications. Anything that is outside the design specifications is usually performed at additional cost. Procedures for Configuration Management--Versioning If you are developing the system in-house, you will need to have procedures for tracking versions and updates to the software. Most development environment software includes versioning and the ability to "check out" and "check in" code. When multiple developers are working on the project, you should make sure you have the enterprise version of the development software so that changes can be synchronized. If the system is being developed by a contractor, you will want to establish a method for tracking the versions that are released to you for evaluation or after fixes are made.