Our Team follows a standard Software Development Life Cycle for the development of all software applications.

• Requirements Phase
• Analysis Phase
• Design Phase
• Coding/Development Phase
• Testing Phase
• Deployment Phase
• Maintenance Phase
• Applications Support phase

1. Requirements Phase:
   

   During the Requirements Phase, automation needs of the business functions are collected and quantified. The requirements include business rules that govern the work of the user, definition of specific business functions or processes, and levels of security needed to protect the business’ information. During this phase, a Board is established. This Board is comprised of business function and representatives. The Board receives all proposed changes to the requirements, decides if the proposed change should be applied to the system and if accepted, places a priority on the incorporation of the change to the system.

2. Analysis Phase:
   In the analysis phase the requirements gathered in the requirements phase, are used to create report definitions and layouts, screen definitions and layouts, data element definitions, workflow diagrams, and security matrices. This phase culminates in the creation of a “logical” model of the application.

3. Design Phase:
   In the design phase the logical model developed in the analysis phase, is used to develop a “physical” model of the application. The physical model contains business object logic, database schemas identifying relationships, web object design and layout, report calculations and processing, and the security object definition.

4. Coding/Development Phase:
   In the coding/development phase the individual objects or components of the application are coded from the physical model. Once the system objects have been developed, they are gathered and connected together (integrated) to create a working application. The integrated application is placed on a staging server for testing.

5. Testing Phase:
   The testing phase encompasses three testing stages; component testing, requirements testing, and acceptance testing. During component testing, all objects are tested to ensure they work together as specified by the physical design. Once the components are tested and the system operates as designed, the application is tested against the requirements gathered in the requirements phase of development. Once the requirements testing stage is completed, the system is presented to the business function for acceptance testing. In all testing stages, defects are identified and returned to the development/coding phase for correction.

6. Deployment Phase:
   The deployment phase contains two stages, a three- to six-month pilot followed by a national deployment. At the conclusion of the pilot, the finished application is placed on a production server. Users are trained, user guides are delivered, and the system is distributed nationally. The application is then maintained by the Team.

7. Maintenance Phase:
   In the maintenance phase the deployed application is maintained through scheduled backups. Any changes to the application are presented to the Board for approval. If a change or enhancement has been approved by the Board, it is presented to the Requirements Team and the software development life cycle begins again.

8. Applications Support phase:
   The Applications Support phase has two primary roles: applications support and program management for designated programs. The Team is further responsible for the management and coordination of the Information Technology and Users Group.