Vicki Gold

Introduction to Basic Assessment and Outline

last updated -August 22, 2011

Grades will be divided as follows:

2% - For Extra Credit
20% - Final Exam

Outline
  1. Introduction to Computing
  2. MHS acceptable use policy
  3. Introduction to Game Maker with Click Ball Tutorial
  4. First Game in Game Maker
  5. File Systems
  6. Introduction to Real Basic Programming
  7. RB - Flow of Control
  8. RB - Calculator
  9. RB -Conditionals
  10. RB -Conditionals - Black Jack. Two-for-One, Rock-Paper-Scissors, and Prime Numbers
  11. RB -Loops Exercises and GM
  12. Stick Figure RB
  13. Technology of Tomorow Project
  14. Game Maker for Art and Technology Fair
  15. Internet Safety
  16. Pong Project and Presentation in RB (this is subject to change)
  17. Mastery Objective Portfolio's
  18. Final Project in RB or GM
  19. Finalize Portfolio's

Basic Programming Assessment

Basic Running of the Program

  1. The program successfully compiles and runs. This means both the (.rpb or .gmk ) and .exe program runs
  2. The program reasonably fulfills assignment requirements according to rubrics and Web site requirements.
  3. The .rbp and .exe are on the H:/Basic/REALbasic/AssignmentFolder or the .gmk and .exe are in the H:/Basic/GameMaker/Projectfolder. Presentations go with their appropriate project folder unless told elsewise.

 

Thoroughness and accuracy

The program fulfills assignment requirements, and produces correct results in all situations.To demonstate this capacity the program is required to be put through a reasonable amount testing. Test results should be handed in along with the final submission.

Design of user experience

The program provides a good experience for the user. Program output has a well-designed layout and is easy for the user to understand. Proper grammar and spelling are used. Windows, and all fields are to be meaningfully labeled.

 Descriptive variable names and comments

Comments at a miminum should describe how who wrote the code, when was it written, and what the program does. Comments are a necessity in your program or points will be deducted. In addition, variable and function names are to be meaningfully well chosen and follow industry convention. (I will describe what the industry naming conventions are necessary when appropriate.)

Programming style and readability

Spacing and (comments) are used to make the program code easy for humans to read. Indentation is used to show the structure of the program. I will not help debug code that is not indented correctly.

Extras

To earn an A, or additional credit the student must go beyond the required rubrics and statements, by adding something of their own creation to their program or presentation. In general this means using an "an Event, Action, or piece of code" in your project that you have NOT tried. To avoid unhappiness, it is wise to previously check that your functionality agrees with what I consider appropriate.

Submission on time

The program was turned in by the specified due date, or late with a valid excuse. (5 points are deducted for each day late.) Beyond an appropriate amount of time at the teacher’s discretion, late work will not be accepted at all.)

Very Important: If you try a new piece of code and it does not work please do not delete it. Comment the chunk of code out, and in your comments explain what you were trying to accomplish. You will get points for trying.

Rubric for Basic Project Assessments

A

The project's code executes and exceeds the requirements for the project. (The requirements for each individual project is posted on the Web site - http://goldclasses.com) . The student exceeds expectations on their understanding and ability to document their design and code. The student is able is work independently.

B

The project's code executes and fulfills requirements. (The requirements for each individual project is posted on the Web site - http://goldclasses.com). The student is able to present a reasonable written explanation what the code does. The student is able is work mostly independently.

C

The code fulfills a small subset of the requirements. The student was not attentive or was disruptive in class and produced little independent work determined by the students capacity to explain their work.

Rubric for Basic Project Presentation Assessments

A

The presentation explains the code and describes any special design decisions. The presentation is well organized and is clearly stated. The student used helpful visuals to aid in the discussion. The student goes beyond the stated requirements.

B

The student presents an explanation of the code and describes any special design decisions. The presentation is well organized and clearly stated.

C

The student's presentation is not well thought out. A reasonable understanding of the design and code is not displayed.

D

Irreverent or inappropriate material is placed in the presentation.

Rubric for Basic Lab Assignments Assessments

A

The Lab Assignment fulfills and exceeds requirements. (The requirements for each individual project is posted on the Web site - http://goldclasses.com). The student is able to present an in depth written explanation of what the code does. The student's successful ability to work cooperatively with their classmates.

B

The Lab Assignment executes and fulfills requirements. (The requirements for each individual project is posted on the Web site - http://goldclasses.com). The student is able to present a reasonable written explanation of what the code does. The student's ability to work cooperatively with their classmates.

C

The Assignment was not completed independently nor was it understood. Written explanation insufficient.