Embedded Files
CHECKPOINTS
Your project is divided into three checkpoints:
Alpha
Beta
Release
On each checkpoint, you'll be graded on GOALS and PROCESS
GOALS (50%)
The quality of your work
Measured by:
Meeting contract goals
Code quality
PROCESS (50%)
Meeting deadlines
Up to date and correct Trello
Including all elements with your submission (code, jar, screenshots, description, instructions, etc)
FINAL GRADE
The majority of your grade will be based on your final project's quality. This is a significant grade for Q4 and serves as your final exam grade.
Seniors:
If you are in a mixed-grade group, the Alpha will serve as your final grade.
If you are in an all-senior group, you'll submit an extra checkpoint halfway between Alpha and Beta. This will be your final grade.
RUBRIC
50% - Execution
30% - Code Quality
10% - Ambition
10% - Audience Score
DOCUMENTS
On the first day of our project, you'll complete three different things and send them to Mr. M
TRELLO
How To Use IT
Purpose
Project Management Tool
Acts as a "To Do" list to coordinate your group
All of the info on how to set up your Trello can be found on the link to the left
Today in Class...
Create a Trello and invite your group members.
Set the Trello to "public" rather than "workspace visibile."
Send Mr. M a Schoology Message with a link to the Trello's URL. Do not invite him as a member.
Configure your Trello following the instructions on the left
CONTRACT
Template
Purpose
Acts as an agreement between your group and Mr. M about what will be completed on each phase.
Today in Class...
Copy the template on the left and invite all group members as editors
Invite Mr. M to your contract as an editor (mmalafarina@bcps.org)
Transfer ownership of the document to Mr. M
Fill out the contract for Alpha, Beta, and Release
Each goal should be clear and measurable
DESIGN DOCUMENT
Purpose
A document to keep track of all of your game's organization and content
Used to communicate that information between group members and Mr. M
Today in Class...
Create a google doc in any format you wish
Invite Mr. M to your design document as an editor
Create a basic version of your design document that has at least:
An overview of your gameplay
Outline of inheritance hierarchy and major classes
Page updated
Google Sites
Report abuse