CSC 360

Spring 2015

Craig Miller

Weekly Notes

Assignments

Technical References

Team Project 4
Software-based Prototype
Due Friday June 5 before 11:30pm

Overview

For the last installment of the team project, you will develop a working prototype of the product you have designed and evaluated. A functioning back-end is not required. Instead, the submitted code should be adequate for demonstrating tasks and running usability tests.

Requirements

  • The submitted files should demonstrate at least one core task with working interactions that complete the task. The application may work with canned data known to work on pre-determined user input.
  • Good development practices should be followed and include the following:
    • Well organized code with consistent indenting
    • Appropriate use of comments including authorship
    • Files are organized separating document structure, page formatting, interaction control and, as appropriate, content data
    • Clean, effective visual design (simple is fine)
  • A summary document that includes the following:
    • A description of the core tasks and how they are implemented
    • A summary of the process which led to the current implementation
    • A summary of how individuals contributed to the project

Submission

Create a zipped folder containing your code and summary report (PDF is preferred). Submit the zipped file to D2L.

Grading

This project is worth 20 points. The following criteria will be used for scoring the report:

  • Design and implementation. The code is well written and organized. It effectively demonstrates the core tasks.
  • Code completeness.The code is complete and addresses all requirements.
  • Process. The report effectively summarizes interview and testing results and how they led to the presented design.
  • Document completeness. The summary report addresses all required elements.