Variables and Decision Structures
Guidelines and Assessment Rubric
We're going to add/modify some features of the class photo file from
assignment 3:
- An introduction screen that has some sort of a title and a means of
moving on to the pictures.
- A "credits" button that takes you to a credits page with a
comprehensive list of those who worked hard on your class photo file
(e.g. yourself).
- A "go back" button on the credits page that takes users back to
the last image they were viewing. (this might not be
the "first" or "last" pictures).
- A well organized library, (hint: stick your buttons in one folder
and your pictures in another).
- Use if() statements to make sure the previous, next, first, and
last buttons only navigate to different picture frames,
not to the "credits" area or the intro page (the if
statements will only be necessary for the previous and next
buttons).
If you are already well versed in Flash: Extend your array-based
assignment 03 to a randomized sequence of photos/names (this will help
prevent the primacy and recency effect in rehersal that comes out of
cognition which is a fancy way of saying that we remember more readily
what we see first and what we see last). This should be an easy switch
to make, let me know if you have questions about it.
- Deliverables: flash development file (.fla)
- File Naming convention: assignment4{YourName}.fla (so if your name
were Sam Walker you would name the file assignment4SamWalker.fla).
Assessment Rubric
Your assignment will be assessed using the following rubric:
Criteria |
Points |
Do you use a consistent naming convention for layers, symbols, and
pseudo-symbols in this case the image bitmaps? Did all of your layers
have a meaningful name? (e.g. "layer 1" is not an option) |
1 points |
Is your project easy to change and update?
- you should have only the number of instances you absolutely need
for each symbol.
- you should use consistent tab stops for your code don't be shy
about using the autoformat button in the actions window.
- Finally, you should not have any "magic numbers." For the purposes
of this class, a magic number is defined as a value in ActionScript
that is used in more than one piece of code, but not updatable in one
place.
|
3 points |
Do you have a well organized timeline (related layers are near each
other, elements are where they are promised e.g. student photos are in
the pictures layer, not the buttons layer). |
2 points |
Are all of the required elements (see above) present and working
correctly? |
4 points |
Total |
10 points |