![]() |
![]() |
||||
JOINT AUTOMATED BOOKING SYSTEM (JABS)SituationThe U.S. Department of Justice's (DOJ) law enforcement agencies need to book criminal offenders. A single arrest may involve as many as three agencies, during which the arresting agency, then the detaining agency, then the incarcerating agency may, for the same offender, photograph, fingerprint, and record biographical data. Prior to JABS, booking data were captured on paper and in systems accessible by only one agency, making it difficult to share information among federal law enforcement components. In USDOJ Components without a data system for recording bookings, storing, managing, and retrieving such information was inefficient. For example, information sent to the Federal Bureau of Investigation (FBI) for identification purposes was sent by mail on hard-copy forms, and the response from the FBI could take several weeks. A client-server version of JABS was implemented and initially deployed in 1999. The success of JABS resulted in over 800 deployed sites across the country by 2004. However, the technical architecture of a client-server implementation came with inherent drawbacks. The JABS PMO quickly realized that the effort and cost associated with deploying and maintaining so many sites was prohibitive. SPS - Problem Solved.
SPS implemented a 3-tier software architecture that divided the application into three tiers: Presentation or User Interface Tier, Business Logic Tier, and Database Manipulation Tier using a Model-View-Controller (MVC) design pattern. A JABS ABS workstation was designed and developed using the Aware Accuscan, NISTPack Sequence Check, and Accuprint developer toolkits in combination with internally developed web pages and client software to interface to and integrate with COTS components. SPS developed a data administration sub-system to manage user access and audits, and a query sub-system to provide extensive search capability functions to all participating agencies. Methodology Development methodology followed the DOJ System Development Life Cycle processes and standards, appropriately modified in consultation with the JABS program management office. The SDLC emphasizes artifact preparation and quality control as embedded activities, greatly facilitating clear linkage between requirements and implementations, and effective client review and guidance. SPS designed and developed the system using a component-based design and J2EE session beans to set the foundation for a service-oriented architecture. The advantage of this approach is that a component can interface with other J2EE components using the J2EE protocols and not incur the overhead of SOAP and XML processing, and at the same time be loosely integrated with external systems using XML. This also reduces redundant code without comprising performance. Lessons Learned A comprehensive integrated development environment, including system configurations closely matching systems to be deployed, substantially reduced changes late in the development cycle. Deployed systems were essentially error free. Cooperative and productive interactions with other JABS contractors requires a substantial degree of formalism and "bipartisan" commitment to mutual success. Results
Client Benefits The client now has a system that demonstrates a highly secure, flexible, and scalable Java information technology solution with interfaces to peripherals and hardware, capable of capturing biometric information requirements. About SPS Contact Information |
CASE FACTSSector: |
||||
| © 2005–2007 Software
Performance Systems, Inc. | Privacy Policy
7905 Malcolm Road · Suite 200 · Clinton, MD 20735 · 1.866.734.6777 · sps@goSPS.com |
|||||