Overview of SRJC Web site Projects

Many clients find it helpful to read an overview of how the class works and learn what their role will be in the Web construction process. This class can be divided into 4 phases which I refer to as the Web Development cycle.

1. Planning
2. Production
3. Testing
4. Handoff

The planning phase begins when the clients meet before the semester begins to discuss the process of becoming a client. After the meeting the client should begin to gather all their content, identify some goals for their site, and surf the Web for sites they like.

Students are assigned to a client at the end of the first week of school At that time the instructor notifies the clients if they have received a team.

Next the Project Manager contacts the client and sets up the first client meeting. Before this meeting the Project Manager will send the client a list of questions which will be discussed at the first meeting.

It is very important that the client provide in-depth answers to the questions and as much site content as they can during the first meeting. Although some content is shared during the first meeting, in most cases the team will need subsequent meetings to gather all of the content.

Based on the client information and the site content each member of the team begins to prepare the Web Proposal. The Project Manager writes up a strategic brief, creates a timeline, work chart. contract bid.

The designer begins to design mock ups for the home page and second level pages. These Photoshop documents are not working Web pages, simply pictures of what the pages will eventually, look like.

The Content Developers create a story board, list of deliverables, production standards and places all the content in the shell site. A shell site is defined as a web site which has the content displayed on all the pages which will eventually make up the site, but does not look like the finished product. The pages are plain white pages, with black text, and blue links. After producing these documents the Content Developer reviews them with the client to assure they are accurate.

The Programmer investigates the Web server capabilities, develops a plan for the scripts they will modify or build, and creates the Technical Brief. Depending on the needs of the client the programmer may also create a new database or convert an existing one to use with their Web scripts.

Once the Web proposal is shown to the instructor it will be presented to the client. At this time the client needs to ask questions about any areas of the proposal which are confusing, or which need to be changed. The content is finalized and reviewed by the client . The client will be expected to "sign off" on each page of the shell site. After the proposal has been approved by the client we can move from the planning to the production phase of the class.

Meanwhile the designer and client are working together to develop mock ups which represent the look and feel of the site. After receiving client approval the Designer slices up the Photoshop mock up into Web images and builds a sample second level Web page using HTML, we call this a template page.

The Content Developers take the template page and start making each page of the site. They use the design from the template page and the content from the shell site. As they work on each page they upload it to the development site and then contact the Designer so they can approve the final look of the pages. The Designer and Content Developers work together to resolve any problems or unexpected issues.

The programmer makes any form pages or Web pages which are created from their Web Scripts, They use the designers template to make sure their pages match the other pages at the site.

Now the project moves into the testing phase. The completed site is tested in 4 ways:

1. Classmate testing done by the Content Developer
2. Client testing done by the Designer
3. Typical User testing done by the Project Manager (please note that the client will be asked to provide the names and email addresses of typical users)
4. Hardware and Software testing done by the Programmer or another team member if no programmer is assigned to that team.

If HTML errors or typos are found they are corrected, however major design changes or content revisions cannot be implemented at this stage.

Finally the site is prepared for handoff. All the web pages, web images, scripts, PDF files, and flash animations are placed in a folder on a CD (compact disc). Finally a client manual is created, this document is intended to help the client understand what they have been given and how they can make minor revisions to the pages. The client and instructor each receive a copy of the CD which is prepared by the Project Manager.

We all get together to show off the sites and celebrate our hard work.