[an error occurred while processing this directive] [an error occurred while processing this directive]
[an error occurred while processing this directive]

Working with Access Idaho

<< return to Web Application Development

What software development process is used by Access Idaho?

Each web application project follows a development lifecycle consisting of eight phases.

Engagement

The agency describes the high-level objectives of the project, identifies key project members, decides on the data access and billing plans, and submits a Letter of Engagement [DOC] to Access Idaho. The project's Management Team will meet to discuss the agency's objectives. If the needs of the agency mesh with the skills of Access Idaho, the project will be added to the Access Idaho project queue.

Inception

Representatives from Access Idaho and the agency hold pre-requirements meetings to define the project's goals, motivation, timeframe, scope, and risks. Project team members are included as needed. Inception generally consists of one to three meetings and lasts one to two weeks. The phase ends when the Project Definition is approved by the Executive Project Sponsor.

Requirements Gathering

The Agency Project Leader and the Access Idaho Project Manager meet with business users who understand the agency's current processes and team members from both the agency and Access Idaho who will be doing the project work. The requirements of the project are specified, the project's products and deliverables are defined, and prototypes are built and tested for usability. A work schedule is developed that defines which workers will complete which tasks, and task completion dates and deliverables are defined and assigned. Requirements Gathering generally consists of four to eight meetings and lasts two to four weeks. The phase ends when the Requirements Specification and Prototype have been approved, the Service Level Agreement has been signed by the Executive Project Sponsor, and the Project Schedule has been approved by both the Executive Project Sponsor and the Access Idaho General Manager.

System Design

Technical workers from Access Idaho and the agency design the system. This work generally includes the agency sending technical specifications to Access Idaho. System design generally lasts one to two weeks. The phase ends when the system design has been agreed to by the technical team members.

Implementation

The technical team members build the web application and the administrative tools and reports which are part of the project's deliverables. User interface testing is performed at the end of this phase. Implementation generally lasts four to six weeks. The phase ends when the Beta version of the product is released to the agency.

Agency Testing

A formal Beta release meeting is held to show the application in its near to final form. Team members from the agency test the application, including the interactions of the application with the agency's data, and raise any issues which are encountered. Any necessary changes are made, and a new Beta version of the application is released. This cycle may be repeated several times. Agency testing generally lasts two to four weeks. The phase ends when the Beta Release has been approved for production by the Executive Project Sponsor and the Access Idaho General Manager.

Deployment

The application is moved into the production environment using the agency's production data. The application's URL is publicized to potential users. Agency business users are trained to help the agency's customers use the application. Agency financial specialists are trained to use the billing reports to reconcile any funds collected by Access Idaho and sent to the State Treasurer's office. The Deployment phase generally lasts about one week.

Closure

Closure represents the end of the project, and the moving of the application into general operation. A closure meeting will be held with the Project Executive Sponsor, the Agency Project Leader, the Access Idaho General Manager, and the Access Idaho Project Manager to discuss how operations work, how change requests should be handled, and general support expectations. Closure generally consists of a single meeting and lasts about one week. The phase ends with the Closure Meeting.

In this section:

[an error occurred while processing this directive]
[an error occurred while processing this directive]