NYC Departments of Correction and Probation
Portal Implementation
Business Requirements
Tata Consultancy Services Limited
Draft
March 10, 2005
NYC Departments of Correction and Probation Portal Implementation
Revisions
Version
Primary
Author(s)
Description of Version
Date
Completed
Page i
NYC Departments of Correction and Probation Portal Implementation
Contents
REVISIONS ................................................................................................................................................ I
CONTENTS ............................................................................................................................................... II
1
INTRODUCTION .............................................................................................................................. 1
1.1
1.2
1.3
1.4
1.5
1.6
2
PURPOSE .......................................................................................................................................... 1
SCOPE ............................................................................................................................................. 1
SUPPORTING MATERIAL ...................................................................................................................... 1
DEFINITIONS AND ACRONYMS ............................................................................................................ 2
BUSINESS INTERACTION MODEL ........................................................................................................... 3
OVERVIEW ....................................................................................................................................... 3
OVERALL DESCRIPTION.................................................................................................................. 4
2.1
PRODUCT PERSPECTIVE ...................................................................................................................... 4
2.2
PRODUCT FEATURES ........................................................................................................................... 4
2.3
ACTORS, ROLLS AND BUSINESS FUNCTION ............................................................................................ 4
2.3.1
Personas ....................................................................................................................... 4
2.4
OPERATING ENVIRONMENT ................................................................................................................ 4
2.5
DESIGN AND IMPLEMENTATION RESTRAINTS ........................................................................................... 4
2.6
ASSUMPTIONS AND DEPENDENCIES ..................................................................................................... 4
3
FUNCTIONAL REQUIREMENTS ........................................................................................................ 5
3.1 FUNCTIONALITY BY USE CASE ..................................................................................................................... 5
3.1.1
Overview ...................................................................................................................... 5
3.1.2
Use Case Reference ................................................................................................... 5
3.1.3
Business Functionality .................................................................................................. 5
3.1.4
Process Workflow ......................................................................................................... 6
4
EXTERNAL INTERFACE REQUIREMENTS .......................................................................................... 8
4.1
4.2
4.3
4.4
5
USER INTERFACES ............................................................................................................................... 8
HARDWARE INTERFACES ..................................................................................................................... 8
SOFTWARE INTERFACES ...................................................................................................................... 8
COMMUNICATION INTERFACES ........................................................................................................... 8
NONFUNCTIONAL REQUIREMENTS ................................................................................................ 9
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
ARCHIVAL ........................................................................................................................................ 9
AUDITABILITY ..................................................................................................................................... 9
AUTHENTICATION............................................................................................................................... 9
AUTHORIZATION ................................................................................................................................ 9
AVAILABILITY ..................................................................................................................................... 9
COMPATIBILITY .................................................................................................................................. 9
CONFIGURABILITY .............................................................................................................................. 9
DATA INTEGRITY ................................................................................................................................ 9
EXTENSIBILITY ..................................................................................................................................... 9
INSTALLABILITY ................................................................................................................................... 9
INTEGRATABILITY ................................................................................................................................ 9
LEVERAGABILITY/REUSE ...................................................................................................................... 9
Page ii
NYC Departments of Correction and Probation Portal Implementation
5.13
5.14
5.15
5.16
5.17
5.18
5.19
5.20
5.21
5.22
5.23
5.24
5.25
5.26
5.27
LICENSING/LEGAL ........................................................................................................................... 10
LOCALIZATION ................................................................................................................................ 10
MAINTAINABILITY ............................................................................................................................. 10
MULTIPLE ENVIRONMENT SUPPORT.....................................................................................................10
OPERABILITY ...................................................................................................................................10
PERFORMANCE ............................................................................................................................... 10
PERSONALIZATION ........................................................................................................................... 10
PORTABILITY ....................................................................................................................................10
PRIVACY ........................................................................................................................................10
RELIABILITY ......................................................................................................................................10
ROBUSTNESS ...................................................................................................................................10
SCALABILITY ....................................................................................................................................10
SECURITY ........................................................................................................................................10
UPGRADEABILITY ............................................................................................................................. 10
USABILITY/ACHIEVABILITY .................................................................................................................10
APPENDIX A .......................................................................................................................................... 12
Page iii
RCMS Probationer Reporting Kiosk – Business Requirements
1 Introduction
1.1 Purpose
The purpose of this Business Requirements Specification document is to identify and define the business and functional requirements for the NYC Departments of Correction and
Probation portal implementation. This document is intended for use by Business Analysts, User Interface Developers, the System Architect and Software Developers.
This document incorporates by reference the following deliverables:
User Interface Design
It should also be used as a reference when creating the Software Architecture and Design Specification
1.2 Scope
It is easy to reason that these agencies could spend years utilizing and implementing all
of the functionality that portals provide. Therefore, the scope of this project will be limited
to configuring and delivering the IBM Websphere Portal. Once users have been categorized, identified, and entered into employee directories the following portal functions will
be implemented:

Document Management: A document management system will be implemented through the portal to manage the Department of Probation’s Executive Policies and Procedures (EPAP).

Intelligent Notification Service: A Use-of-Force/Incident Management notification system will be developed for the Department of Correction uses IBM’s Intelligent Notification Service.

People Search: The portal will be configured to allow the departments to search
for employees, inmates and probationers.
1.3 Supporting Material

DOP Request for Proposal for Task Order B

TCS Proposal for Task Order B

The Portal Implementation Project Charter
Page 1
RCMS Probationer Reporting Kiosk – Business Requirements
1.4 Definitions and Acronyms
Term
Definition
EPAP
Executive Policies and Procedures
INS
Intelligent Notification Service
PO
Probation Officer
CO
Correction Officer
DC
Deputy Commisioner
AC
Assistance Commisioner
DD
Deputy Director
Page 2
RCMS Probationer Reporting Kiosk – Business Requirements
1.5 Business Interaction Model
1.6 Overview
The portal will provide a means to integrate various DOP and DOC applications. It will
provide a way for the Agency staff to publish/read content, look up details of Agency staff
and subscribe to receive notifications to Jail Incidents.
The three objectives of this portal will be:
Incident Notification: Allow Agency staff to subscribe to various Jail Incidents. Whenever any of these “incidents” occur, they are logged onto a PC system in the facility. This is
then emailed or paged out to the subscribed staff.
Content Publishing and Search: Allow MAPS team to publish EPAPS. This will also allow the MAP team to create draft versions of the EPAP for circulation and approval from
the various responsible authorities. When these EPAPS are posted on the portal, the
Agency staff will be able to read this by one of two ways: a) Searching for the EPAP by
keyword OR b) Browsing through the relevant categories to find the EPAP.
Directory Search: Allow staff to search for a DOC/DOP employee by either name or Department. This directory will be kept updated on a daily basis. The records for a particular
employee will show his/her details plus their position in the org structure.
Page 3
RCMS Probationer Reporting Kiosk – Business Requirements
2 Overall Description
2.1 Product Perspective

2.2 Product Features
2.3 Actors, Rolls and Business Function
2.3.1
Personas
2.4 Operating Environment
2.5 Design and Implementation Restraints
2.6 Assumptions and Dependencies

Page 4
RCMS Probationer Reporting Kiosk – Business Requirements
3 Functional Requirements
3.1 Functionality by Use Case
3.1.1
Overview
3.1.2
Use Case Reference
3.1.3
Business Functionality
1. Goal
i. Validation Steps to Achieve Goal
a. Sub Steps
ii.
Page 5
RCMS Probationer Reporting Kiosk – Business Requirements
3.1.4
Process Workflow
Page 6
RCMS Probationer Reporting Kiosk – Business Requirements
Page 7
RCMS Probationer Reporting Kiosk – Business Requirements
4 External Interface Requirements
4.1 User Interfaces
The portal will provide an interface for: a) Updating employee data b) Publish EPAPs. c)
Search for content on the portal. d) Subscribe/unsubscribe to receive notifications.
4.2 Hardware Interfaces

Client Machine - Processor Hardware – P4 1GHz, memory 256 MB, 17” monitor

Server Machine - Processor Hardware – Dual P4 2.4GHz, 2.5 GB RAM, 36 GB logical disk space.
4.3 Software Interfaces
4.4 Communication Interfaces
The RCMS Kiosk is an internet application that uses several communication protocols for
its functionality:

HTTP

HTTPS

TCP/IP

JDBC
Page 8
RCMS Probationer Reporting Kiosk – Business Requirements
5 Nonfunctional Requirements
5.1 Archival
5.2 Auditability :
The system will keep a count of the content accessed on the portal. It will store the following
information: a) Which profile accessed the document b) What is the total number of times a
document was accessed.
5.3 Authentication:
All the content on the portal will be accessible only after the user logs in.
5.4 Authorization
5.5 Availability:
The portal will be available 24x7.
5.6 Compatibility:
The portal will be compatible with IE 5 and above.
5.7 Configurability
5.8 Data Integrity
5.9 Extensibility:
The portal should be flexible enough to allow adding more applications/portlets if required in
the future.
5.10
Installability
5.11
Integratability
5.12
Leveragability/Reuse
Page 9
RCMS Probationer Reporting Kiosk – Business Requirements
5.13
Licensing/Legal:
The System shall be open source that adheres to the GNU General Public Licensed (GPL) .
For more information on public licensing software please read the following:
http://www.opensource.org/docs/osd.pdf
5.14
Localization:
The portal shall support multiple languages and shall have the capability to configure a new
language. No special effort shall be made to support non-US measures, currencies calendar
formats etc.
5.15
Maintainability
5.16
Multiple Environment Support
5.17
Operability
5.18
Performance
5.19
Personalization
5.20
Portability
5.21
Privacy
5.22
Reliability
5.23
Robustness
5.24
Scalability
5.25
Security
5.26
Upgradeability
5.27
Usability/Achievability
Page 10
RCMS Probationer Reporting Kiosk – Business Requirements
Page 11
RCMS Probationer Reporting Kiosk – Business Requirements
Appendix A
Page 12