CSC 397 Class Project : CSC Web Site Redesign

Due: 10 December 1998

Class Photo

 

Project organization will be critical, due to time constraints. Grading is individual.

 

Required tasks:

  1. Identify audience. Completed 12 November by class discussion. Results . . .


    Week of November 16-20
  2. For each type of user (see above), identify what they'll want to know and what they should be able to do. Brainstorming completed 12 November by small group (3-4 students) discussions, each user category covered by two different groups. Brainstorm results . . . Functionality Committee Functionality Committee Results
  3. Visit other CSC dept websites for ideas. My CSAB list would be excellent. See how they are organized, what kinds of information are available, what is good or bad about them. Search Committee Search Committee Results
  4. Identify web page development tools (target is CSC server). Which are available, and where? Tools Committee Results
  5. Need mechanism to allow development on CSC server (accounts, permissions, etc). Must cooperate with CSC sysadmin.
  6. Agree upon guidelines and standards: Standards Committee Results

    7. design guidelines, look and feel, terminology, documentation, web page hierarchy structure.


    Week of November 23-27

  7. Develop Detailed specifications consistent with guidelines (colors, fonts, etc).
    Standards Committee II: Jeff, Jeff, Jeremy. Standards Committee Results
  8. Develop procedure for publishing web pages as they are developed.
    Publishing Committee: Jim, Josh, Andrew. Publishing Committee Results
  9. Design the Home Page.
    Home Page Committee: D'Lynn, Nichole, Scott, Rich. Committee Results Top Level Structure (Word doc)
  10. Specify detailed Web Site Page Structure.
    Structure Committee: John, Rick, David, Ryan. Structure Committee Results


    Week of November 30 - December 4
  11. Reconcile results of last weeks committees, where overlaps occur. Reconciliation Report
  12. Final walkthrough of structure by whole class, and web page development assignments. Outline
  13. Finalize web page publishing guidelines and procedures. Web Page Publishing Procedure
  14. Form teams and start working on web pages! Teams


    Week of December 7 - 11
  15. Finalize pages and submit to Josh for publication!

 

 

 

Return to the Top  

Special Notes:

Do not feel constrained to that which can be reasonably developed this semester. Design can include capabilities that will be implemented later.

On the other hand, we must leave the patient in better shape than before the operation!

Note that we have an alumni registration and survey application ready to go online (from spring 98 SE maintenance project -- D'lynn, Nichole, and Rich were all involved)

Note that we have WHAT application already in place (CGI).

Return to the Top   

 

Committees can be formed according to task. Committee list might be:

  1. installation, integration and version control
  2. determine guidelines and detailed specifications.
  3. quality assurance (compliance to specifications)
  4. decide on development tools and assure their availability
  5. detailed analysis, including exploration of other dept web sites.
  6. final approval of guidelines, content, structure: committee of one (guess who).
  7. integration/installation of existing apps: WHAT and alumni registry/survey.
  8. Maintenance (manual for future webmaster).

 

What are the interdependencies among tasks? How will this affect the schedule and committee lifetimes and memberships?

Return to the Top  

[ CSC 397 | Pete Sanderson | Computer Science | SMSU ]

Last reviewed: 3 December 1998

Peter Sanderson ( pete@csc.smsu.edu )