Requesting and Developing New Web Applications
Request to Initiate a New Project
The Webmaster will be first point of contact on new web projects.The Webmaster will:
- Gather general information from the requestor, via email, regarding the scope and goals of the project.
- Do an initial analysis of the request. If it is a basic website, then the Webmaster will continue to process the request within his group. If the request is for more than what can be accomplished within the Collage Content Management System, the Webmaster will forward it, along with suggestions, to the rest of the application review group.
Online Discussion
The members of the application review group will share their recommendations or concerns about the project. If there are reasons at this point to not move ahead, these will be handled on a case by case basis. Otherwise, an Analysis Meeting will be scheduled.iCIT Analysis Meeting
In this meeting, the Webmaster, Academic Web Coordinator, and Senior Web Developer will meet with the customer and the customer's developer(s) to identify and analyze the project requirements. The objective of this meeting is to clearly identify the following. (The customer will be expected to provide a document addressing each of these points.)- General project goals, scope, and business need
- Specific functions of the application
- Potential users
- Timeline
- Required resources
- Ability to use ASP.NET / C# / SQL Server
- Other technologies to be used
- Need for enterprise data, such as student records
- Sensitivity of data and other security concerns
- Alternatives to custom development, such as third-party solutions
Application Review Group Meeting
The members of the application review group will meet to approve or reject the external development request and return the decision to the requestor. If the proposal is rejected, further discussions with the requestor will be held to identify alternative solutions.
If the project is approved for external development
The iCIT Senior Web Developer will hold the following meetings with the customer’s developer(s):Initial Design Meetings
- 1 hour meeting to discuss our expectations regarding design and design documentation.
- 2 hour meeting to review and analyze the design.
- 30 to 60 minute meetings as needed until the Senior Web Developer has signed off on the design.
Development Meetings
1 hour meeting per 40 hours of development time. At least half of the meeting time will be dedicated to reviewing code. This will also be the best time for the customer’s developer to get answers to coding questions.Pre-Release Meeting
1 hour meeting to discuss the testing process that the customer’s developer should follow and the iCIT QA process.QA Release Meeting
This meeting will include the customer’s developer, customer, and members of the application review group.In this meeting, the customer’s developer will provide a full demonstration of the functionality of their application.
Following this meeting, iCIT staff will perform final testing and code review.
The iCIT Senior Web Developer will hold additional meetings with the customer’s developer as needed if the application fails to pass QA.
