All projects must be turned in on the due date given. You are responsible for ensuring that all files are turned in on time. All documents turned in must include your name or team's name.

You should include only code, text, HTML, or PDF, and possibly image (gif or jpeg) or sound (.au or .wav) files. You are free to use any environment available to complete your work, however, you are responsible for converting it into one of the standard formats listed above (most current programs can save or print files to a variety of alternate formats).

Note: It is recognized that meeting schedules are difficult. thus, you should plan well in advance when trying to schedule time with your clients or your readers. The entire team is expected to attend the initial introductory meeting with each client and reader. You should also strive for all attending additional meetings, but at least two students must be present for any meeting.

Project Milestones

To keep your projects on track, we will expect you to complete several milestones approximately every two weeks during the semester by meeting with your client.

• Project Choice, due Tuesday, September 6
  Submit top three choices for clients, what role you expect to play, and any other relevant experience you have (2-3 paragraphs)
• Project Executive Summary, due Wednesday, September 14
  Describes purpose and operational overview of the application including a discussion of its value to potential users (2-3 paragraphs)
  • Reader #1 and students will meet 9/14 - 9/16 to read and discuss interactively.
  • Additional written feedback may be given by Reader #1 by 9/19
  • Final draft given to clients by 9/21
• Project Research and App Sketch, due Wednesday, September 21
  In class PowerPoint-like presentation to client of app you intend to build, including justifications for how it fits their requirements (as long as necessary)
• Project Plan
  Presents an overview of the goals, priorities, and deliverables for the client. Specific items required for the document include: Project Executive Summary, Design Goals (negotiated with client), Team Priorities for each of the 3 sprints, Technology choice justification, Concerns or risks the client should know
  • Initial draft to Reader #1 by 9/28
  • Written feedback from Reader #1 by 10/5
  • Meet with Reader #1 no later than 10/14 for an interactive discussion of the final draft
• Project Sprint #1, due Wednesday, October 5
  In class demo to client of first draft of app, attempt to implement features agreed to in Project Plan
• Project Sprint #2, due Wednesday, October 19
  In class demo to client of second draft of app, attempt to implement features agreed to in Project Plan
• Project Sprint #3, due Wednesday, November 2
  In class demo to client of third draft of app, attempt to implement features agreed to in Project Plan
• Project User Testing, due Tuesday, November 15
  Provide client's user testers with some background on the application, instructions for conducting the testing, and a feedback survey to be completed at the conclusion of the test, including: Description of Application, Overview of user test plan, Draft of instructions for user testers, Draft of user post-test survey
  • Initial draft of testing documentation to Reader #1 by 11/9
  • Meet with Reader #1 for an interactive discussion and feedback on the User Test and Instructions
  • Feedback on Final Testing Documentation from Reader #1 by 11/14
• Project Repsonse to User Feedback, due Tuesday, November 29
  In class demo to client of fourth draft of app, attempt to respond to issues raised during User Testing
• Technology Transfer, due Tuesday, December 6
  Tech Transfer Documentation: The Tech Transfer Documentation contains all the information the client needs to use, maintain, and upgrade the application after the design team has disbanded. Essentially there are three components of this package; information for users of the application, information for managers responsible for the application, and information that programmers may need for future modifications to the application. Specific requirements for these documents include: User Documentation/Help Files/FAQ (for non-technical users as necessary for your particular application), Client application maintenance Document (for slightly technical clients addressing how to install, update, or change key components of the app), In-code comments (for programmers), Comprehensive project code design document for future programmers that may maintain your application
  • Initial introduction meeting with Reader #2 by 11/3 (send Project Executive Summary to READER #2 prior to this meeting
  • Initial draft of Technology Transfer Documentation to Reader #2 by 11/9
  • Meet with Reader #2 11/16 - 11/18 for an interactive discussion of draft Project Plan
  • Second draft of Tech Transfer Documentation sent to Reader #2 by 11/30
  • Written Feedback from Reader #2 to students on Final Tech Transfer Documentation by 12/5
  • Final Tech Transfer Documentation delivered to Client and Instructor by 12/10