MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_01C5FBFC.396F1A00" This document is a Single File Web Page, also known as a Web Archive file. If you are seeing this message, your browser or editor doesn't support Web Archive files. Please download a browser that supports Web Archive, such as Microsoft Internet Explorer. ------=_NextPart_01C5FBFC.396F1A00 Content-Location: file:///C:/D09ACA34/front.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" DUSC: Dynamically Updating Service Calendar

 

 

DUSC: Dynamically Updating Service Calendar=

Final Report

 

Michael Dotterer (mdotter1@wam.umd.edu)

Michael Reilly (mjreilly@wam.umd.edu)

November 8, 2005

Abstract<= /p>

 

The design and development of the Dynamically Updating Service Calendar (DUSC) is discussed.  This product is intended for use by the Epsilon Mu Chapter of Alpha = Phi Omega National Service Fraternity at the Univers= ity of Maryland, College Park.  Design decisions were made to be consistent with the eight golden rules of interface design, as proscribed by Shneiderman and Plaisant.  Fla= sh and MySQL were chosen as development platforms for the user interface and back-= end database, respectively, though alternatives such as Asynchronous Java and X= ML (Ajax) and PHP are = also considered.  Informal surveys = of Brothers of the Epsilon Mu Chapter were conducted to determine early usabil= ity considerations, and a full usability test was conducted later.  Changes were made to the DUSC syst= em in response to these suggestions and observations.  While the product is still approac= hing completion, chapters from Mas= sachusetts have expressed interest in using the DUSC system themselves once it is finalized.
Credits

 

Michael Dott= erer

  • User needs assessment (concrete task examples; system requirements)
  • Low-fidelity prototype 2 (design; description; walkthrough)
  • Usability test design (pretest and posttest questionnaires)
  • Back-end MySQL database development

Michael Reil= ly

  • DUSC Product Proposal
  • User needs assessment (introduction)
  • Low-fidelity prototype 1 (design; description; walkthrough)
  • Usability test design (users and task list)
  • Conducted formal usability test
  • DUSC: Dynamically Updating Serv= ice Calendar Final Report (except the Low-fidelity prototype 2 description, which was drafted by Michael Dotterer)

 

Michael Dotter= er and Michael Reilly (equal contributions)

  • References
  • Informal usability test survey
  • Fr= ont-end Flash development

 

------=_NextPart_01C5FBFC.396F1A00 Content-Location: file:///C:/D09ACA34/front_files/header.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii"

   &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;        - 3 -<= !--[if supportFields]><= ![endif]-->        &= nbsp;           &nbs= p;  

------=_NextPart_01C5FBFC.396F1A00 Content-Location: file:///C:/D09ACA34/front_files/filelist.xml Content-Transfer-Encoding: quoted-printable Content-Type: text/xml; charset="utf-8" ------=_NextPart_01C5FBFC.396F1A00--