Phase Documentation: Concept Document, Addendum
Every project starts out as a general idea to put a process on-line. The Concept phase is designed to help fill out that idea by defining the scope of the project. Agency representative(s) and a Nebraska.gov project manager will decide on questions like: Is this a process that will be open to the entire public, or a specified group? Will this project require an administrative interface, or will it simply allow for users to send information directly to an agency database? Is there a need to build a payment function into the application? How will this project be funded?
Phase Documentation: Functional Specifications, Flow Charts, Prototype
Once the scope, or general outline, of the project has been decided on, the project then moves in to the Planning phase. It is this phase that decides the details of how the different parts of the application will work. Again, the agency representative(s) work with a project manager to ensure that the functionality incorporated in the application will fulfill the agency's business rules and needs. During this phase, an application developer may also be asked to attend meetings to provide technical expertise. It is very important that during the planning phase, everyone in the agency who has knowledge of the process being automated is involved in creating the functional specifications and prototype.
Phase Documentation: Change requests
During the Development phase the programmer creates the application based on the requirements in the functional specification. The project manager and the agency representative(s) may be consulted during this time to answer any questions on the specifications. Development can reveal omissions in requirements, or at times, agency business rules change during this time frame. In either case a change request is required to document the alterations to the original functional specifications.
Phase Documentation: Change requests, Test Plan
When the developer has finished the programming of the application, the project manager then coordinates in-house testing at Nebraska.gov in order to test for bugs, missing functionality, etc. A test plan is created based on the functional specifications, and is completed to ensure all requirements are met. The application is then turned over to the agency for testing. The agency may perform any kinds of tests they deem necessary to verify that the application meets expectation. The agency is also provided with a test plan to complete. If any needed changes/additions to functionality are identified, these are agreed upon by Nebraska.gov and the agency, and written up as a change request. Any alterations to the application will require further testing.
Phase Documentation: Authorization to launch, Agreement for release of funds
A date is chosen to take the application “live”, and when it goes in to production, the agency and Nebraska.gov partner to ensure that all aspects are functioning correctly. This includes user interface, data transfer, payment processing, etc. Nebraska.gov then provides on-going maintenance and technical troubleshooting.