Q11: Project Proposal

Table of Contents


Objectives

  • Start working with other guild members to develop a final guild project.
  • Develop a plan for the final guild project.
  • Develop the core concept of the project.
  • Identify the subsystems to be completed by each guild member.

Academic Honesty

Read the Scholastic Honesty Policy and Assignment Integrity policies of the syllabus. Here are some clarifications for this particular assignment:

  • You are expected to work with your guild to develop a project proposal.
  • You may get help from people other than your guild members but must attribute ideas.

Project Proposal Guild Specifications

Start by reading the entire Course Project to understand what you will be working on over the coming weeks. Then all guild members must work together and are jointly responsible for completing the following requirements.

  1. Develop a project concept that is either a game or interactive simulation.
  2. Write a proposal document with a heading for each section shown below in bold.

    Here is an example Project Proposal.

  3. As a heading near the top of the document, state the guild name. For example:
    CS-12GP Project Proposal
    Guild: Phoenix
    
  4. Guild members: state the name of the guild and list the guild members (first and last name) involved in the project. For example:
    1. Phoenix Guild Members
    ------------------------
    Cody Coder
    Dan Developer
    Ed Parrish
    Emma Engineer
    Paula Programmer
    Leroy Jenkins -- N/A
    

    Contact guild members you have not seen or heard from recently and ask if they are planning to contribute to the project. If the person does not contribute, then list N/A (not available) after their name like: Leroy Jenkins -- N/A.

  5. Core concept: clearly describe the core concept, which includes the core mechanics, in words. For example:
    II. Core Concept
    ----------------
    Our guild project is a platform game like Super Mario Brothers. However, the main character is Jungle Jane. Jane's goal is to save George from the evil creatures who have abducted him while he was napping. Jane's core mechanics are walking, runing and jumping on various jungle platforms and creatures. Jane will need to use her skills to outwit the evil creatures and free Jungle George.
    

    The core mechanic is the system of play in the game and are the main actions that the player performs repeatedly. In the above description, the core mechanics are walking, running and jumping on platforms and creatures.

  6. Game subsystems: organize the game coding into subsystems with planned objects and their classes. A subsystem is a self-contained system within a larger system. In the project, a subsystem is group of software classes, not just methods within a class. No one can be responsible for only art or audio assets and everyone is responsible for coding the use of collisions, animation, images and sound in their subsystem.

    It is also important that each subsystem is as self-contained as practical so that the failure of one subsystem does not cause the entire project to fail. However, some subsystems will always be critical to project success so choose wisely.

    Here is an example heading for this section:
    III. Game subsystems
    --------------------
    

    Assign a guild member as the primary owner of each subsystem and its classes. All subsystems and classes must be named and have a single person as the owner.

    The guild is responsible for ensuring that each guild member has a subsystem that is allocated enough scope for the classes to code in their subsystem. The guild member is then responsible to contribute the information for their subsystem(s) to their section of the overall document.

    If the subsystems are largely identical, make certain that each subsystem has some significantly unique aspect so that the guild member can express originality. The guild member is then responsible for clearly describing the significantly unique aspects of their subsystem (see next section).

    If the project is derivative, then indicate which subsystems and classes are new to meet originality requirements.

  7. The proposal must be typewritten, not handwritten, with good grammar and spelling. Review each other's contributions for content and correct grammar, spelling and semantics as necessary for a well-written document. Make certain that class names and descriptions are included in the content.

Note that the project proposal document must be submitted to Canvas as a .txt, .rtf, .doc or .docx file and every guild member must turn in a paper copy to the instructor.

Project Proposal Solo Specifications

Each guild member is individually responsible to complete the following part of the project plan for their assigned subsystem.

  1. Subsystem label: develop a short label (one to three words) for your chosen subsystem and include the label with your name attached like:
    Main Characters: Paula Programmer
    

    This means you are the sole owner of this subsystem of complete software classes. Under your unique label, include the following information with the subheadings shown below in bold.

  2. Subsystem description: list at least three class names that you will write with a short description of how the objects provide a significant role in the project and will have at least 100 lines of code combined when written like:
    Description: The main characters who walk, run and jump and throw projectiles.
    Classes include:
    1. Sprite: superclass of game characters that can run and jump
    2. Jane: the user-controlled character
    3. George: the NPC that must be rescued.
    
  3. Object collisions: describe the planned collisions for objects of your subsystem for which you will write the code. for example:
    Object Collisions:
    -Jane walks, runs and jumps on platforms.
    -Jumping on a creature kills it.
    -Jane dies when creatures run into her.
    

    The proposal must describe at least two collisions where you will write the code and the purpose of those collisions. Thus each guild member is responsible for defining a set of collisions interacting with their subsystem for which they will write code. If you cannot describe these collisions then your subsystem is not adequate.

  4. Planned animations: identify and describe at least two animations planned for your subsystem, for which you will implement the animation code. For example:
    Planned animations:
    -Jane walking, both left and right.
    -Jane running, both left and right.
    -Jane jumping, both left and right.
    -Jane throwing projectiles, both left and right
    -George walking back and forth inside his prison.
    
  5. Planned images and sources: list at least three specific images for your subsystem, the sources of the image and a short description of the how the image will be used in your subsystem. For example:
    Planned images:
    -Jane standing: standing still when not moving.
    -Jane moving: a series of images when Jane moves either left or right.
    -Jane throwing: a series of images when Jane moves either left or right.
    -George pacing: walking back and forth inside his prison.
    -Image sources: Charas, online RPG character generator
    http://charas-project.net/
    

    Note that an image name is NOT enough of a description.

  6. Planned sounds: list at least two sounds, the sources of the sounds and a short description of the how the sound will be used in your subsystem. For example:
    Planned sounds:
    -Jane grunting when she hits a wall.
    -Jane success sound (yodel?) when she outwits or defeats an enemy.
    

    Note that you will be responsible for writing the code that controls the playing of these sounds.

  7. Incorporate your subsystem information into the proposal document for the guild to review as described in the Guild Specifications.

    For an example, see the Project Proposal.

Project Extra Credit

  1. Up to two (2) points of guild XP is given for original artwork, ideas and concepts. For example:
    1. Original drawings included with the proposal (both paper and digital form required)
    2. A description of new game play ideas or novel simulation mechanics
    3. A description of unique and interesting combinations of puzzles, combat, dexterity challenges, hidden objects or revelations

    These are guild extra credits and apply to all guild members equally. For images, include a paper copy of the images as well as submitting the images files to Canvas.

Grading Criteria

The instructor will evaluate your assignment using the following criteria. Each criteria represents a specific achievement of your assignment and has a scoring guide. The scoring guide explains the possible scores you can receive.

Some scoring guides have a list of indicators. These indicators are a sign of meeting, or a symptom of not meeting, the specific criterion. Note that a single indicator may not always be reliable or appropriate in a given context. However, as a group, they show the condition of meeting the criterion.

For information on grading policies, including interpretation of scores, see the syllabus page.

Project Proposal Criteria

Everyone starts with 20 points and the instructor will subtract points for not meeting the requirements based on the following criteria.

General Specifications
  1. -20 if you do not submit your proposal (see How to Submit) either on paper or electronically, if the proposal is not a game or simulation, of your part has no programming.
  2. -10 if you did not work with your guild or your name is not mentioned in the project. (I assume a Leroy Jenkins)
  3. -4 if you did not bring a paper copy to class; -3 if your paper copy of the proposal is handwritten; -1 if you did not put your name on your copy.
Guild Specifications
  1. -20: Proposal is not a game or interactive simulation. (gs1)
  2. -4: Proposal is not well organized with headings for each of the specified sections. -2: Well organized but missing headings. (gs2)
  3. -1: Proposal missing a Guild Name heading with a guild name stated. (gs3)
  4. -2: Proposal missing a Guild Members section with guild members listed. (gs4)
  5. -4: Proposal missing a Core Concept section. -2: Core concept is not clear or the core mechanics are not described. (gs5)
  6. -4: Proposal missing a Game Subsystems section clearly identifying a subsystem for each guild member with objects and classes that could have at least 100 lines of code. -2: Subsystem, objects or classes are not clearly named and described. -1: Classes not clearly identified. (gs6)
  7. -2: Proposal is handwritten. -1: Grammar error found. -1: Spelling error found. (gs7)
Solo Specifications
  1. -1: Missing a Subsystem Label for chosen subsystem. -1: Subsystem missing a single owner. (ss1)
  2. -3: Missing Subsystem Description for chosen susbsystem. -1: Subsystem description incomplete. -1: Need at least three classes described. (ss2)
  3. -4: Missing Object Collisions section describing object collision for chosen subsystem. -2: Object Collisions section does not clearly describe at least two collisions or the purpose of the collisions in the subsystem. (ss3)
  4. -4: Missing Planned Animations section that describes two or more animations for chosen subsystem. -2: Planned Animations section does not clearly describe at least two animations for subsystem. (ss4)
  5. -2: Missing Planned Images section that describes or shows three or more images. -1: Planned Images section does not clearly describe or show at least three specific images and their sources for the subsystem. -1: Missing image sources. (ss5)
  6. -2: Missing Planned Sounds section that describes planned sounds for the scenario. -1: Planned Sounds section does not clearly describe at least two planned sounds and when they will be used in the code for for the guild member's subsystem. (ss6)

Maximum Score: 20, plus extra credit

How to Submit

Submit means that you are presenting your work for consideration and grading. Follow these instructions carefully and exactly to turn in your quest (assignment) and maximize your XP:

  1. Choose one person in your guild as the "submitter" who will submit the final project proposal from which everyone is graded.
  2. The submitter ensures that all the parts are combined correctly and submits the project into the Q9 quest slot of Canvas.

    Do NOT submit solo versions of the project as the last submission by anyone in the guild will be counted as the final version for the entire guild.

  3. In addition, all students bring a paper copy of your guild proposal to class to turn in for grading comments.

    Make certain to write your name at the top of the front page so the instructor knows which student turned in the paper.

Please do not add any extra characters to the above folder names. Also, do not put any spaces or special characters like #, : or $ in zip file or folder names.

If you make a mistake, you can resubmit up to the deadline but must resubmit all assignment files.

Home | Canvas | Schedule | Syllabus | Room Policies
Help | FAQ's | HowTo's | Links
Last Updated: April 24 2017 @19:22:57