Course Requirements



This course's activities center around four major components (see also Grades):
For individual due dates, see the Syllabus.




CLASS ASSIGNMENTS: Specific, weekly assignments are available on the Syllabus.

HTML PORTFOLIO: Each student is required to construct and keep up-to-date an HTML Portfolio. The purpose of the portfolio will beto present yourself to a prospective employer by including the information below. Students may construct their class homepages in a format of their choosing, but they must be aware of aesthetic and stylistic concerns and include the following:
  • Index Page / Introduction
  • Links to Sites Relevent to Area of Expertise (Including Class Project)
  • Professional Autobiography
  • Résumé
  • "Mailto:" Link
  • Hypermedia and Multimedia
  • Writing Samples
Portfolios will be graded by content, organization, and aesthetics in that order of importance. This component of the course will require a strong familiarity with the World Wide Web. "Browsing" and "surfing" are integral for students to gain a knowledge of HTML aesthetics and design; this endeavor must begin immediately and should be continued independently and aggressively throughout the portfolio's development. A full multimedia page is encouraged.

Web design, like any other creative undertaking, requires a specific literacy and competancy which should be desplayed in each portfolio's design.

CLASS PROJECT: The class project will be a class web site or a traditional paper report (20-30 pages minimum) constructed solely by the students addressing technology and technical writing. A topic will be chosen by the class; some topic examples include:
  • An instructions guide for new students in the multimedia classroom
  • An overview of a software program integral to writing
  • A business proposal
  • A proposal for improving USF's Technical Writing Program
  • An analysis of the use of HTML in education and business
The Class Project will be divided into two phases. Phase One: Organization. The first phase will be a single class meeting where two co-directors will be elected by the class. These officers will be responsible for directing the project to completion.

Phase Two: Implementation. The officers will divide the class into sub-groups responsible for various project tasks and then bring the various divisions together for the completion of the project. The C.E.O. will require occasional progress reports submitted by the officers.

Officer Responsibilities. The officers will not participate in the implementation of the project, but will have administrative responsibilities including proposal submission, progress reports, organizational direction, and discipline (if necessary). As mentioned above, the directors are the bosses; what they say goes. They, in turn, will be supervised by the C.E.O., so they will not abuse their power. Only these officers will report problems to the C.E.O. (the instructor) and are in charge of all class operations directly related to the project. The officers will set policies and due dates for the other committee members, and their decisions will ultimately be supported (or vetoed) by the C.E.O.

FINAL REPORT: This report should be a two-page memo to the president of USF outlining the importance of constructing and maintaining multimedia classrooms in the university system. Take examples from what you have experienced in 202 this semester during the individual research, group participation, and classroom activities that you encountered and overcame (or failed to overcome because of poor resources) this semester. Since these reports will be delivered to the addressee, great professionalism and attention will be required from each student.




CLASS PARTICIPATION: Regular class attendance and active participation in classroom discussion, class listserv, and group activities are required. Some assignments will occasionally count for participation: peer editing and other similar activities. Additional assistance can be obtained from the instructor during office hours or by appointment.

Listserv, MUDs, MOOs, and DAEDALUS: Various form of electronic discourse will be utilized by the class. Participation in the class listserv, MUD and MOO meetings, and Daedelus interchanges will be required. Specific assignments dealing with each of these activities will be prompted by the instructor, usually in class. See Listserv for directions on subscribing.




FINAL EXAM: The final will be a cumulative exam based primarily on class discussions, assignments, and reading. A more detailed explanation will follow in the exam review (See Syllabus).




HomePoliciesTech WritingSyllabusLinksProjectsEmailInfo
27 December 1997