OJI DEVELOPMENT TASK ORDER STANDARDS

Attachment B - OJI Development Task Order Standards

INTRODUCTION

The OJI System integrates and automates most of the present functions related to administeringunemployment compensation benefits, including, but not limited to, maintaining employerrecords, filing initial claims, processing special claims such as CWC and UCX, determiningmonetary and non-monetary eligibility, requesting separation information, issuingdeterminations, charging employers, charging the mutual account, filing additional claims,processing appeals and issuing re-determinations.

The OJI System provides access for three major users: claimants filing for unemploymentbenefits and/or seeking work, employers funding the benefits, and state staff.

OJI is a web-based system with a centralized statewide database. Information entered and retrievedfrom all call centers, processing centers, one-stop locations and the central office resides in thesame database.

EXISTING ARCHITECTURE

OJI Applications (Claimant, Employer, Staff, OJI-JavaBatch, SIDES applications)

Application development changes must be implemented using the current/existing software architecture. The existing software includes but is not limited to the following:

  • WebSphere Application Server 8.0.0.4
  • Compiled under Java 6 but written using Java 4 and Java 5
  • New java beans utilize struts-like DAO/DTO/service method design pattern
  • DB2 V11 – Database & SQL Stored Procedures on IBM z/OS Mainframe
  • RAD 9.5
  • SAP BusinessObjects Crystal Reports 2013 Support Pack version 14.1.2.1121

RC Express Applications (RC Express Web and RC Express Batch applications)

Application development changes must be implemented using the current/existing software architecture. The existing software includes but is not limited to the following:

  • WebSphere Application Server 8.0.0.4
  • Compiled under Java 6 but written using Java 5 (Online) & Java 4 (Batch)
  • Spring Framework 2.5.6
  • JBoss Seam 2.1.2
  • JSF 1.2 (Online) & JSF 1.1 (Batch)
  • JSP 2.1
  • Facelets 1.1.14
  • RichFaces 3.3.1.GA
  • Hibernate 3.3.2.GA
  • Business Objects & Mapping Files generated using Eclipse Helios 3.6.2
  • DB2 V11 – Database & SQL Stored Procedures on IBM z/OS Mainframe
  • FileNet 5.1.0 (Content Engine and Process Engine)
  • jQuery 1.8.3
  • RAD 9.5
  • Crystal Reports XI 2013
  • Adobe LiveCycle 8.2.1
  • Lastly, other miscellaneous libraries.

CODING GUIDELINES / STANDARDS

The final deliverable will utilize the benefits of each technology/framework of the specific java application and be developed and maintained using IBM Rational Application Developer (RAD). Version of RAD will be determined by JFS.Any technologies or frameworks not specified in this document should not be used without prior approval.

Any new application must be built utilizing the same design as the OJI or RC Express applications.

ANALYSIS

  • List of components and/or objects impacted

DESIGN

  • Provide screen mock ups or wireframes
  • Provide detail design document
  • Provide technical design document
  • State staff will be given opportunity to review (but not approve) documents
  • State staff will be given opportunity to participate in code walkthroughs
  • Database changes will be reviewed and submitted by state staff

DEVELOPMENT

  • Software at integration test level and above must be checked in/checked out of existing version control software
  • Database connections: ResultSets closed and nullified

BUILD AND DEPLOYMENT GUIDELINES/STANDARDS

OJI Applications

Software builds must use the existing build software, including the following:

  • Version control: Serena Dimensions CM 12.2. All application software changes must be made using the existing version control software and existing check in/check out procedures. Branching is not allowed.
  • Build Scripts: Apache Ant 1.8.2. Must use existing Ant scripts to build application jar files and ear files.

RC Express Applications

Software Builds must use the existing build software, including the following:

  • Repository:Archiva 1.3.9. New jar files introduced into the applications but be placed into the Archiva 1.3.9 repository and cannot conflict with existing jar files needed to support the existing software (e.g., Filenet 5.1.0 Content Engine and Process Engine).
  • Dependency Manager: Apache Ivy 2.4.0/IvyDE 2.2.0. Must use the IvySettings.xml and Ivy.xml source files to introduce new .jar files to the applications and ensure all dependencies are resolved cleanly.
  • Version control: Serena Dimensions CM 12.2. All application software changes must be made using the existing version control software and current check in/check out procedures. Branching is not allowed.
  • Build Scripts: Apache Ant 1.8.2. Must use existing Ant scripts to build application jar files and ear files.

Page 1 of 4