Development Process for Programming
Request Form
To request programming work, fill out this request form for new applications, enhancements to existing applications, code reviews, and program registrations.
The Web Solutions Team will contact you to get more detailed information about the request. This information is used to form the basis of the Requirements Document (see below), and provides the scope of the project review and approval.
Programming proposals are reviewed by the Dean's Office to align priorities with limited resources. Proposals may be approved contingent upon funding.
Meeting
After the work has been approved the client will meet with the programmer(s) to discuss the project in depth and you will provide them with detailed requirements in regard to the application. Code Reviews may not need a meeting to proceed.
Requirements Document and Estimate
A requirements document, that includes time estimates by task, will be created from the information gathered from the client. This document should include all functions, features, data needs, and time estimates for the entire application. The document will also include dates of when programming work will begin and the approximate time of completion. The requirements document must be approved by all parties before work by WeST can begin.
Programming work
Programming work will begin as agreed on. During the process the client will be kept informed of work accomplished and tasks completed. The time estimates are just that, estimates. If a task is taking longer than originally estimated, the programmer would let you know immediately, so you won't be caught unaware at the end of the project.
Verify Input forms and functions of same
During the programming process, the client will be kept informed of work accomplished and will be asked to sign-off on input screens and the data that is on them. There is a certain responsibility that the client takes on. Prompt response to questions asked by the programmers will ensure that the work is done quickly and correctly. Only the client can determine if the process that is being created actually fills the need of the application.
Review/Revision
As tasks are completed, it is the reponsibility of the client to review and/or revise the screens and functions. It is easier to change the process of the programs during development, rather than after.
Quality Assurance
As input screens are signed off on, the programmers will ask the Web Development team for input on the "look and feel" of the screens. The input is necessary to ensure that the screens are usable as well as functional. After the look and feel is complete, the client will be shown the screens again for approval and more complete testing.
Testing Sign-Off
All screens and functions will be tested by the client to ensure proper functionality. It is the responsiblity of the client to ensure that testing is done. We will not put any program into a production environment without proper testing, preferably by more than one person.
Future Maintenance
Regular Maintenance, as defined in the requirements document, will be done by WeST as needed. Programs that create errors will also by corrected by us.
Future Enhancements or changes to applications will need a new request and approval before work is done.