C SC 401 Programming Practicum II

Spring 2009 Project Deliverables

Auggie, Matthew and Ryan
The Best Team:

2 April 2009

Softare Design Specification

The Software Design Specification (SDS) document shall consist of:
  1. Introduction
  2. System Architecture Description
  3. Data and Database Structures
  4. Design decisions and tradeoffs
  5. Credits
To assure uniform formatting, the design document will be a single web page that you produce by editing SDS_template.html. Please save a copy of this file, rename it appropriately and replace template text with your own (look especially for the phrase "goes here"). For best results, edit the HTML code directly rather than through a WYSIWYG editor. The "code view" editor in Dreamweaver MX is a good alternative to Notepad (I'm using it right now).

Usability Study

Since your project is intended for general computer users and does not have known clients, you will benefit from the experiences of someone outside the team using your software beginning with the prototype stage. Be sure to read chapter 7 of Object Oriented Software Engineering (CSC 325 text), "Focusing on users and their tasks," before proceeding any further. Then focus on Section 7.5, Evaluating User Interfaces, pages 273-276.

Design and conduct one or more usability studies, then document the experience. This document should address:

Software

The source and executable code plus any necessary data files and databases.

Schedule of Deliverables

Thursday April 23 First Draft Software Design Specification.
Thursday May 7 Second Draft Software Design Specification.
Thursday May 21 Final Software Design Specification.
Thursday May 28 Usability Study.
Tuesday June 9, 1:30 pm Project Presentation and Demo (details later).
[ C SC 401 | Peter Sanderson | Math Sciences server  | Math Sciences home page | Otterbein ]
Last updated:
Peter Sanderson (PSanderson@otterbein.edu)