Building & Managing Web Sites with Microsoft Technologies
Team Project: Sample Write-Up Format

Here are the instructions for the write up of the project. A sample project write up is available to show how each of the sections would be implemented.

I. Introduction

  1. The project is described in general.
  2. The overall purpose of the site is described.
  3. An overview of where the actual pages will reside.

II. Analysis, Schedule, and Requirements

A. Analysis Section.

The visitors to the site are identified. Visitors are categorized into groups (Actors), and their goals identified. A good way to portray this is with a matrix.

  Goal 1 Goal 2 Goal 3 Goal 4
Actor 1 X X    
Actor 2   X   X
Actor 3     X X

In addition the analysis section should outline your design plan. What will be the tone and style of the site. What navigation paradigm will be used. What overall content organization will be followed? Where and how will host the site. Who will do the maintenance? What is the plan for protection and backup of the site?

B. Schedule

A schedule is derived and will be agreed on. For each item in the schedule a milestone is assigned. For each milestone there should be a meeting or sign-off. An narrative overview is given. A sample schedule is below:

Phase # Date Milestone
1 3/15/99 Look, Feel, Navigation and other UI features agreed to.
2 4/15/99 Skeleton of Web Site and Home Page Completed
3 6/15/99 Goal 1 and Goal 2 completed and tested. DB structure finalized.
4 8/15/99 Goal 3, Searching and static content is completed and tested.
5 9/15/99 Goal 4 ASP pages completed and tested.
6 11/1/99 Roll-Out of Final Version

C. Requirements Description and Matrix

Each of the users goals constitutes a requirement. Each of the items identified above is a requirement. For each requirement the responsible entity and the due date is identified. A matrix is made that clearly illustrates all requirements. (The matrix below is abbreviated, more or different items may be required.)

Number Done By Phase Requirement (Description)
1.0.0 -------- -------- Features of the Home Page
1.1.0 Team 1 Look and Feel Design
1.2.0 Developers 1 Navigation
1.3.0 Developers 4 Searching via index server. (Goal 4)
1.4.0 Developers 4 Advanced searching on database. (Goal 4)
1.5.0 Developers 2 Home page links
1.6.0 Customer 2 Static Content Provided To Team
2.0.0 -------- -------- Tasks To Support Goals
2.1.1 Developers 3 Task 1 For Goal 1
2.1.2 Developers 3 Task 2 For Goal 1
2.1.3 Developers 3 Task 3 For Goal 1
2.2.1 Developers 3 Task 1 For Goal 2
2.2.2 Developers 3 Task 2 For Goal 2
2.3.1 Developers 4 Task 1 For Goal 3
2.3.2 Developers 4 Task 2 For Goal 3
2.3.3 Developers 4 Task 3 For Goal 3
2.3.4 Developers 4 Task 4 For Goal 3
2.4.0 Customers All Testing of Actor Goals
3.0.0 -------- -------- Maintenance, Security and Site Planning
3.1.0 ISP 2 Web Site Prepared for Team use by ISP
3.2.0 ISP 6 On going backup, site security and server maintenance
3.3.0 Customers 6 Providing new web site content

III. Roles and responsibilities (who and when)

In this section the general roles and responsibilities are outlined. Once again a brief narrative followed by a matrix is best.

Role Customers Developers ISP
Participate in all design meetings X X  
Derive and Transform Static Content X    
Maintain Web Site X X X
Design Look Feel and Navigation X X  
Design Site Architecture   X  
Build Active Content   X  

IV. List of deliverables (what and when)

Description of each deliverable, and a matrix of delivery dates

Phase Deliverable
6 Completed Web Site
3 DB Layout, ERD, Data Dictionary. List of Stored Procedures and Views.
4 List of Index Server Dictionaries, Search Page Criteria and Function
5 ASP Pages
2 Static Pages

V. Risks and assumptions (CYA)

In this section list of the possible sources of risk, your plan for risk management, and assumptions that will effect the schedule of deliverables.

VI. Budget, Facilities and Resources (where, how)

Here, list all of the facilities and resources the project will need and how much they will cost. If the project is for an internal customer, the developer cost is in time instead of money. Equipment and services costs will be the same in all cases. You should make a matrix of the required facilities and who will provide them. If the project is under contract for money, the terms of payment should be spelled out here, how much at each phase and so on. Sometimes, the terms on ongoing maintenance are specified.

VII. Conclusion

Summarize the project, resources, goals, and milestones in words. Convince your client (and your instructors) that you have a good plan, a good design, you know what you are doing, and that you will deliver on time and in budget.

For other insights on project write-ups see downloads section.

Return to Team Project

CSC 120   
Copyright 1999, 2001 Valtara Digital Design