Indiana Interactive plays an active role in re-engineering the business processes of Indiana government as it pertains to online services, and also has embarked on the next generation of portal solutions.
The primary focus on application development has centered on development estimation, application design and coding, legacy application integration, code review and load testing.
Our application developers benefit from code-sharing, technical experience and best practices available in 23 NIC state portals. All of these benefits offer our staff a unique advantage, which leads to higher quality and faster deployment of applications.
All new development is in Microsoft .Net, and follows IN.gov's latest design standards detailed in the Application Style Guide.
Application development occurs within the Project Lifecycle. The Project Lifecycle as outlined within the IN.gov program follows the below phases:
- Project Initiation
To begin the project process, please submit a request using the Project Request Form.
- Project Scoping
Once a project request is received, the IN.gov team will review the request and reach out to your agency contact to setup an initial meeting and begin the scoping effort.
- Project Business Requirements Document (BRD)
A BRD is created after the scoping process. This document will include detailed information pertaining to the business requirements of the application.
- Project Task Order/Statement of Work
Once the BRD is approved by the agency, a Project Task Order (TO) will be created. The TO will detail the scope of the project and include cost and project timeline information.
- Functional Specifications
After all signature approvals are received on the Project Task Order, the functional specifications for the project request will be defined and approved by the agency.
Upon agency approval of the functional specifications, the development of the agencies project request will begin. Applications will use the standard application header.
- Quality Assurance (QA) Testing
An internal quality check of the application will ensure all aspects of the project request are functional according to the BRD and the functional specifications document.
- User Acceptance Testing (UAT)
UAT testing begins on the application when it has passed the internal QA testing plan. UAT is conducted by the agency using their internal testing plan.
- Load Testing (optional)
IN.gov has the ability to test the application to be sure it can handle a peak load of concurrent users. Load testing is done per agency request and it is important to share peak times the website/application will be accessed along with the expected traffic. This ensures your application is operating efficiently at all times.
- Application Deployment
Once all of the above steps are complete, the agency must provide final approval to launch the application.
- Warranty Period
For a period of two weeks, any issues/bugs found within the website/application will be resolved. This warranty period guarantees your satisfaction with the final deliverable.
IN.gov will continue to support your application if any issues arise that occur within the expected functionality of the website/application at no cost. Support does not include enhancements or changes to the functionality as the website/application was intended to perform. These requests will need to be handled via a separate online form.
NIC (NASDAQ: EGOV) is the nation's leading provider of government Web sites, online services, and secure payment-processing solutions. The company's innovative eGovernment services help reduce costs and increase efficiencies for government agencies, citizens, and businesses across the country. The NIC family of companies provides eGovernment solutions for more than 3,000 federal, state, and local agencies that serve 98 million people in the United States. Additional information is available at http://www.nicusa.com/.