Spring 2000
Team Project Evaluation Form
CSC120 Building and Managing Web Sites
Team Project Name: Group 1 - SKW & Associates
Grading |
Project Proposal/Report: |
28.5/30 |
Presentation: |
12/15 |
Web Pages: |
32.5/35 |
Peer Evaluations |
9/10 |
TOTAL |
82/90 |
Peer Ratings
Question |
Score
1 (low) 10 (high) |
Site's ability to allow users to quickly identify the site's purpose and
major features. |
9.13 |
Use of a consistent navigation scheme(s) across the site/sub-sites. |
8.53 |
Use of consistent color and style from page to page. |
9.38 |
Ability of site to be meaningfully rendered by most web browsers. |
8.94 |
Use of subdirectories to group content for site management and allow
future growth. |
9.13 |
AVERAGE |
9.02 |
Selected (and Paraphrased) Peer Comments:
- There were linking errors. I would suggest a more extensive testing process.
An effective solution could be to have someone outside the team run through the
site, as a fresh pair of eyes can more easily find errors.
- Maybe cut down on the vertical width of the title and subtitle, as this is wasted real
estate.
- Perhaps changing the order of the links on the navigation bar. It seems odd that
"site index" is the third link.
- Staff page is not consistent with the other pages (no left navigation menu).
- No back buttons on several of the pages.
- On some of the pages, the side navigation bar does not go all the way down the page.
This is not consistent with the first page.
- In government and public agency projects, it makes more sense to start at the most
current and work back. For example: 2000, 1999, 1998.... instead of
...., 1998, 1999, 2000.
- In the content, use plain text instead of Bold is because it is annoying.
- Make the users aware that the "Resume" link is a downloadable Word document.
Otherwise they will become annoyed and impatient when the link takes a long time to
load.
- The search feature should be placed in the navigation bar area instead of the home page.
- Quick loading site. The site is not image heavy, but the images that are included
are there for a reason and add to the site content.
- Good site structure that follows most of the best practices guidelines.
- "Conservative" look and feel matches nicely with the business (engineering).
- The map to show the physical location of the office was a nice feature.
- Small photos are well done, and the layout is nice and clean.
- The navigation bar is easy to use and consistent throughout the site (except the staff
page).
- It is useful that you added the search feature to the first page. This allows
users to search for something immediately.
- Site works on lower resolution and sizes well.
Instructor Comments:
Overall: You did an excellent job. Your site looks very professional
and measured, which was exactly the type of site your client wanted. Your project
report was excellent. Aside from make the changes regarding the resume,
your site would be ready to go live. However, I did include other suggestions
(as did your classmates) to make your site even better. Great job!
- While the resume fulfilled the requirement for a downloadble file, there
were several things aspects of its implementation that were problematic. For
one, the resume content would be more user-friendly in HTML format, since
there is no special formatting in the resume. The link to the resume on the
left navigation bar is not good because it does not let the user know they
are going to a non-HTML file (especially bad since it is a MS Word document
rather than a PDF file). On the site index, the downloadable resume should
the include the file size in KB. If you are considering going live with
this, please consider these changes. Also the resume is located in a
directory called "text", which is an odd name--perhaps
"documents" as a start--perhaps "resumes" would be
better still.
- On project photos page, avoid the "click here" type of text. Try
"Enlarged view (69 KB)"
- I am not sure what went wrong with the database wizard on your staff
directory, but you did try.
- It seems like the map page could really have both maps on it IF you could
work on shrinking the maps in size, both height/width and file size.
If you are going into production with this, consider hiring a graphic artist
type (I have at least one suggestion) to make smaller map files for you.
- I would agree with your classmates that the footer is bit busy.
- In your style sheet, do not name classes after HTML elements
(.Body). Either define the BODY element, or give the class a more
meaningful name.
CSC120 Home Page
CSC 120 http://www.valtara.com/CSC120/
Copyright 1999, 2001 Valtara Digital Design