Page 174 - Automated Fingerprint Identification Systems (AFIS)
P. 174

BUYING AN AFIS SYSTEM: THE BASIC DOCUMENTS NEEDED           159



          • How well is the vendor’s product conforming to the requirements spec?
            • Are the interfaces all understood and documented?
            • Has each requirement been allocated to a COTS or developmental item?


          In the development and deployment phase, the documents are prepared by the
          successful offerer. The SOW defined the documents for the vendor to deliver
          and the scope of those documents. During this phase, the government team
          needs to review the documents for completeness, accuracy, conformance to the
          requirements spec, the SOW, and the requirements spec, etc. The typical devel-
          opment phase documents include the following:


          • System design
            • Components and networks, including speed, memory, protocols, capaci-
              ties, etc.
            • Detailed design, including all of your requirements and all second-level
              design information such as model of latent workstation and its compliance
              with the Appendix F Quality Specification and with all requirements allo-
              cated to components
            • Workflows, including administrative workflows even if they are to be staffed
              by the vendor
            • Interfaces with livescans, card scanners, Records Management Systems,
              Computerized Criminal History Systems, other AFIS, the FBI’s CJIS WAN,
              if applicable, etc.
            • Reports that can be generated, including those that are automatically pre-
              pared and printed at the end of each month and quarter
            • Backup and continuity of operations plans, scenarios, and limitations
            • Requirements traceability and verification matrix that maps the require-
              ments to the design and to the verification methods
          • Test plans with test cases, requirements, and design details allocated to test
            cases, test methods, etc.
          • Card conversion plan, including location and approach for data entry, card
            scanning, quality checks, and loading into the operational environment
          • Integration and transition plan
            • Factory integration
            • Site integration
            • Installation
            • Transition
            • Training
          • Project management plan and master schedule
            • Configuration control plan
            • Design review(s)
   169   170   171   172   173   174   175   176   177   178   179