EECS448:Project3
| Navigation |
|---|
| Home |
| Information |
| Classwork |
Contents
Project 3 Assessments
Due Sunday November 10th, 11:59pm
Due Date
All teams must freeze a PROJECT3 branch of their github repository as of 11:59PM Sunday November 3rd.
The master branch must include all code and artifacts required for this projects. The assessments will be posted after the code freeze date.
Overview
There are two projects left in the course, this one and Project 4. They are going to be connected. What you must do for project 3 is come up with an idea for an application and build a prototype. It can be any platform, any language, anything really. Make sure your idea is scalable enough in scope to last for both Project 3 and 4.
Here are some ideas for you pick from, or you can choose your own. But all team members must agree to the project.
Here are some ideas, if you need inspiration from past 448 students:
- Video Games
- Platformers
- RPGs
- Application that adds functionality to some existing API
- A networked application
- Chat program
- Online data storage
- Drum Machine Webpage
- Rate My Professor but for High School courses
- Social network for exercising with gamification
Project Scale
You will present you prototype to me, at which point I will be give you feedback on the scope. I will decide whether to scale it up or down. I will also have the option to force features into the project or choose to remove features.
Team Score (85%)
Prototype Demo (25%)
I'm not asking anyone to make the next Google here, but if you plan to make the best Cowsay for the rest of the semester, you will fail this project and project 4. On the other hand, if you shoot for the moon and miss, that's still a miss. One of the portions of the remaining projects is to create a realistic goal in the time allotted. Consider Project 3 to the be a sprint, meaning you have to decide what you can accomplish before the deadline.
You'll be building a prototype, so some kind of core set of features to should be represented. Again, I'll use the prototype to determine how you increase or decrease the scope of your project 4.
Modularity (10%)
Is your code extensible? Will you be able to easily expand on it for Project 4? Please see me if you are using a functional language.
Stability (10%)
The components of your prototype that you set out to create should work, but features you have yet to implement don't need to be rock solid of course.
We'll be more lenient with stability for the prototype phase.
Documentation (40%)
Along with your normal auto-mated code documentation, you must provide the following artifacts:
- (5%) Standard documentation
- UML
- (5%) State Diagram
- (5%) Use Case Diagram
- (5%) Class Diagram
- Scrum Artifacts
- (5%) Product Backlog (for the entire product, not just the prototype)
- Each item in the back log should have a name, description, and some rough metric to estimate the needed effort
- (5%) Sprint Backlog (what you plan to complete this sprint, i.e. what's in the prototype)
- (10%) Gantt Chart
- Contains all tasks to complete projects 3 and 4
- Timeline starts October 25th (or earlier if you already started working/researching)
- Time scale: days
- Range of days: October 25th to December 1st
Team Assessments (10%)
As in the past, your teammates will fill out anonymous assessments of your contributions to the team.
There will a special section for bickering over what the project should be.
Self Assessments (5%)
You get to assess your own contributions to the team.
FAQ
- What does FAQ mean?
- Frequently Asked Questions
- Will more question be answered here?
- Probably
Plagiarism
You can use existing libraries (e.g. timing libraries), but you must cite all sources of code you do not create.
Inspiration
/ Follow your dreams, kids! \
\ /
----------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
