ITB#: 071I2200046
• Experience with Sybase PowerBuilder preferred
• Experience interfacing web services with client/server application preferred
• Experience with project management methodology preferred, including project plan design and implementation, issue management and system change control The purpose of this project is to convert and migrate all CMIS functionality off the Unisys mainframe environment as quickly as possible, with minimum impact to MDOC users.
1. Software Development, Unit and Integration Testing
Systems analysis, business requirements and functional design is nearly complete; however, additional analysis may be necessary. The senior programmer analyst will be responsible for development, testing, implementation, documentation and technical training of the completed system enhancements. The following is a list of the system enhancements for completion by the senior programmer analyst. a. Data Conversion / Migration for each sub-project
One of the issues in migrating CMIS programs into OMNI is difference in the data. In most cases, data in CMIS cannot be directly migrated into the OMNI databases. There are data type differences and often fundamental differences in the way the data is stored and used. Analysis has been done by MDOC and DTMB for the majority of the migration sub-projects, but each must be reevaluated throughout the development lifecycle for accuracy and consistency. Conversion and migration of existing CMIS data is a requirement for most of the sub-projects. CMIS data must be accurately mapped to new OMNI fields based on functional and system design requirements. Data migration scripts must be efficiently written using best practices minimize time to implement and impact on the OMNI system. The analyst must become familiar with OMNI standards and utilize current processes whenever possible. Data migration testing is unit tested by the developer; User Acceptance Testing must be conducted and approved before moving to production. Migration testing for sub-projects with an OMNI user interface must also undergo integration/regression testing. This is typically accomplished through a mock deployment in a staging database environment. The MDOC will provide users for acceptance testing. b. OMNI System Maintenance/Enhancements
Users currently use a terminal emulator to interface with the CMIS application. All screen-driven functionality currently performed in CMIS must be translated and migrated to the OMNI PowerBuilder application. While considerable analysis has been completed for the sub-projects, some system design documentation remains to be written. System designs must comply with current OMNI GUI and performance standards. Each sub-project with an OMNI interface will follow the development lifecycle to include requirements gathering, functional design, system design, testing and implementation. OMNI code is built on several layers of Sybase ancestor code. Much functionality has been built in and it should be used wherever possible to speed the coding process and ensure consistency of functionality and look and feel of the OMNI application. The analyst must become familiar with the OMNI code foundation. Code review will be conducted to assure compliance with standard coding procedures. The MDOC provides a single point of contact (POC) for each sub-project being developed for the CMIS Migration project. This person acts as the liaison between the business owner(s) and the analyst/developer. The analyst will be expected to communicate possible issues with the POC, keeping the project manager apprised of the situation. All changes to the system design will be preapproved through approved change order processes. OMNI builds are unit tested by the developer; User Acceptance Testing must be conducted and approved before moving to production. All sub-projects will also undergo integration/regression testing. This is typically accomplished through a mock deployment in a staging database environment. The MDOC will provide users for acceptance testing. Deployment of OMNI builds to the MDOC users must be coordinate with other areas of DTMB as well as with the Software Configuration Manager and the Sybase Database unit. DTMB policies and procedures must be learned and followed. c. File Exports
Not every sub-project being migrated from CMIS requires a user interface. There are several instances where file exports are created and transmitted via email or other means to an outside entity or other State of Michigan agency. These sub-projects will involve functional and system design review with the MDOC POC, interaction with the Sybase Database Unit and other DTMB entities as required. d. INSYTE/ADHOC Report Replacement
One of the biggest obstacles to migrating CMIS off the mainframe is the existence of hundreds of reports and data feed files that are created in an INSYTE format for use in ADHOC reports and data input files. The reports and data files are used by MDOC Research and Planning to provide the legislature and other entities with statistical data as required. There are also many Access Databases that have been created in various MDOC facilities that use the data from the INSYTE Input files for critical day-to-day operations. These data files and reports must be identified and recreated for each sub-project before it can be migrated to production. The sub-project most highly impacted by the report issue is the Time Computation project. While considerable work has been done to identify the inputs and reports that need to be recreated, much work remains in determining where creation of dynamic reports makes sense and what needs to be created as currently designed. Mapping of the data fields from CMIS data sets to OMNI Sybase database tables also needs to be done. In addition, the tool that will be used to convert the reports has not yet been chosen. For the purposes of this statement of work, it will be known as business intelligence software. 2. Technical Support and training for DTMB project team Since DTMB assigned development staff will continue support of these applications post implementation, the project manager and the three senior programmer analysts will need to provide technical support and training in order to transfer knowledge of new methods, procedures, processes and techniques used in these projects from the Contractor community to DTMB staff and MDOC staff as directed.
Power Builder Developer with Sybase, mainframe data conversion/migration, any BI tool, web services, and project management experience
Location:Lansing, MI
Duration: 1-3 years
Positions: 3Description:-• Experience with Sybase PowerBuilder preferred
• Experience interfacing web services with client/server application preferred
• Experience with project management methodology preferred, including project plan design and implementation, issue management and system change control The purpose of this project is to convert and migrate all CMIS functionality off the Unisys mainframe environment as quickly as possible, with minimum impact to MDOC users.
1. Software Development, Unit and Integration Testing
Systems analysis, business requirements and functional design is nearly complete; however, additional analysis may be necessary. The senior programmer analyst will be responsible for development, testing, implementation, documentation and technical training of the completed system enhancements. The following is a list of the system enhancements for completion by the senior programmer analyst. a. Data Conversion / Migration for each sub-project
One of the issues in migrating CMIS programs into OMNI is difference in the data. In most cases, data in CMIS cannot be directly migrated into the OMNI databases. There are data type differences and often fundamental differences in the way the data is stored and used. Analysis has been done by MDOC and DTMB for the majority of the migration sub-projects, but each must be reevaluated throughout the development lifecycle for accuracy and consistency. Conversion and migration of existing CMIS data is a requirement for most of the sub-projects. CMIS data must be accurately mapped to new OMNI fields based on functional and system design requirements. Data migration scripts must be efficiently written using best practices minimize time to implement and impact on the OMNI system. The analyst must become familiar with OMNI standards and utilize current processes whenever possible. Data migration testing is unit tested by the developer; User Acceptance Testing must be conducted and approved before moving to production. Migration testing for sub-projects with an OMNI user interface must also undergo integration/regression testing. This is typically accomplished through a mock deployment in a staging database environment. The MDOC will provide users for acceptance testing. b. OMNI System Maintenance/Enhancements
Users currently use a terminal emulator to interface with the CMIS application. All screen-driven functionality currently performed in CMIS must be translated and migrated to the OMNI PowerBuilder application. While considerable analysis has been completed for the sub-projects, some system design documentation remains to be written. System designs must comply with current OMNI GUI and performance standards. Each sub-project with an OMNI interface will follow the development lifecycle to include requirements gathering, functional design, system design, testing and implementation. OMNI code is built on several layers of Sybase ancestor code. Much functionality has been built in and it should be used wherever possible to speed the coding process and ensure consistency of functionality and look and feel of the OMNI application. The analyst must become familiar with the OMNI code foundation. Code review will be conducted to assure compliance with standard coding procedures. The MDOC provides a single point of contact (POC) for each sub-project being developed for the CMIS Migration project. This person acts as the liaison between the business owner(s) and the analyst/developer. The analyst will be expected to communicate possible issues with the POC, keeping the project manager apprised of the situation. All changes to the system design will be preapproved through approved change order processes. OMNI builds are unit tested by the developer; User Acceptance Testing must be conducted and approved before moving to production. All sub-projects will also undergo integration/regression testing. This is typically accomplished through a mock deployment in a staging database environment. The MDOC will provide users for acceptance testing. Deployment of OMNI builds to the MDOC users must be coordinate with other areas of DTMB as well as with the Software Configuration Manager and the Sybase Database unit. DTMB policies and procedures must be learned and followed. c. File Exports
Not every sub-project being migrated from CMIS requires a user interface. There are several instances where file exports are created and transmitted via email or other means to an outside entity or other State of Michigan agency. These sub-projects will involve functional and system design review with the MDOC POC, interaction with the Sybase Database Unit and other DTMB entities as required. d. INSYTE/ADHOC Report Replacement
One of the biggest obstacles to migrating CMIS off the mainframe is the existence of hundreds of reports and data feed files that are created in an INSYTE format for use in ADHOC reports and data input files. The reports and data files are used by MDOC Research and Planning to provide the legislature and other entities with statistical data as required. There are also many Access Databases that have been created in various MDOC facilities that use the data from the INSYTE Input files for critical day-to-day operations. These data files and reports must be identified and recreated for each sub-project before it can be migrated to production. The sub-project most highly impacted by the report issue is the Time Computation project. While considerable work has been done to identify the inputs and reports that need to be recreated, much work remains in determining where creation of dynamic reports makes sense and what needs to be created as currently designed. Mapping of the data fields from CMIS data sets to OMNI Sybase database tables also needs to be done. In addition, the tool that will be used to convert the reports has not yet been chosen. For the purposes of this statement of work, it will be known as business intelligence software. 2. Technical Support and training for DTMB project team Since DTMB assigned development staff will continue support of these applications post implementation, the project manager and the three senior programmer analysts will need to provide technical support and training in order to transfer knowledge of new methods, procedures, processes and techniques used in these projects from the Contractor community to DTMB staff and MDOC staff as directed.
No comments:
Post a Comment