EECS448:Project4

Navigation
Home
Information
Syllabus Schedule
Classwork
Labs Projects

Evaluations

Due Thursdays December 12th by 11:59pm

• Exit Interview
• Assessment of your project 3
• Self Assessment
• Teammate Assessment

Due Dates

All teams must have all code and artifacts on their team's github repo by December 1st, 11:59pm

Submission

One member from each team should send an email to myself and both TAs with the following:

1. team name
2. team roster
3. url for github repo

Overview

In Project 4, you will be finishing the product that you prototyped for project 3.

Project 4 Requirements

Final Demonstrations (25%)

• Each team will present their final products to the whole class
• Presentations will take place the weeks of December 2nd and 9th
  • We have a basic headphone jack, HDMI hookup, and a doc cam for mobile devices
• Each team member must speak
• Attendance is required until all teams have given a presentation

TO ENSURE ATTENDANCE FOR ALL PRESENTATIONS I RESERVE THE RIGHT TO GIVE THE FINAL EXAM ANY DAY DURING THE LAST TWO WEEKS OF CLASS

Artifacts

• (5%) Product Backlog
  • Document that shows what is complete/incomplete from the product backlog
• (5%) Documentation
  • HTML file produced by JavaDoc or equivalent
• (6%) UML Diagrams
  • (2%) State Diagrams
  • (2%) Use-case diagrams
  • (2%) Class diagrams
• (5%) Meeting log
  • Meeting times and locations
• (5%) Gantt Chart
  • Contains all tasks to complete projects 3 and 4
  • Timeline starts in when you began project 3
  • Time scale: days
• (5%) Project 3 assessment
• (5%) Teammate assessments
• (4%) Self assessment
• (5%) Bug list
  • List of all known bugs, even those you don't currently have tests for
  • May list this on your github page
  • Every application has bugs. If you don't know of any bugs, you're not looking hard enough.
• (5%) User's Manual
  • Create a document complete with screen shots and descriptions for a layperson to use your product.
  • Page requirement: Approximately 5 pages
• (5%) Deployment plan
  • Make a plan on how to get your product into market
  • Do research and write a report estimating how much it will be to put your product into the market
  • Example costs:
    • app store costs
    • costs to get your game on XBoxLive
    • costs to print disks for distribution
    • costs to buy domains
    • costs to attend conventions and conference and set up booths
  • Page requirement: Approximately 5 pages
• (5%) Maintenance plan
  • Do Research and write a report estimating how much will cost to maintain your product for the next year
  • Examples
    • Costs for hiring developers
    • Monthly or annual fees for servers or domain names
    • Monthly or annual fees for your distribution platform (e.g. app store, XBox live)
  • Page requirement: Approximately 5 pages

Test Suite (10%)

• Must add a one-click test option in your final product
• Prints to screen, console, or file the summary of test suite being ran and the results of those tests
• You should run a suite of tests to verify the core functionality
• You are not required to test API, libraries, or other code you didn't write
• Recall, writing every possible test isn't feasible. Write smart tests for the essential functionality of your project

Other requirements (5%)

• Exit interview
  • An assessment of the company (the 448 course)
  • Will be posted later