FIT2012 Digital media authoring - Semester 2, 2010

Berwick

Caulfield

Prerequisites

Prohibitions

Teaching approach

This unit will be delivered via a 2 hour lecture and a 2 hour tutorial class each week.

Lectures will be used to present and explain programming principles and practices within the context of the authoring environment of Flash.

Tutorials will be used for practical experience in the development, coding, testing and debugging of the functions specific to the authoring environment.

Timetable information

For information on timetabling for on-campus classes please refer to MUTTS, http://mutts.monash.edu.au/MUTTS/

Tutorial allocation

On-campus students should register for tutorials/laboratories using the Allocate+ system: http://allocate.its.monash.edu.au/

Unit Schedule

*Please note that these dates may only apply to Australian campuses of Monash University. Off-shore students need to check the dates with their unit leader.

Prescribed text(s) and readings

Foundation Flash CS4 for Designers
By Tom Green, David Stiller
Friends of Ed (2009)
ISBN-10: 1-4302-1093-1
ISBN-13: 978-1-4302-1093-1

ActionScript - Your Visual Blueprint for Creating Interactive Projects in Flash CS4
Rob Huddleston
Wiley Publishing Inc (2009)
ISBN-13: 978-0-470-48194-3

See also: "Recommended Reading" below for a list of recommended references.

Text books are available from the Monash University Book Shops. Availability from other suppliers cannot be assured. The Bookshop orders texts in specifically for this unit. You are advised to purchase your text book early.

Recommended text(s) and readings

Learning ActionScript 3.0 - A Beginner's Guide
By Rich Shupe with Zevan Rosser
O'Reilly (2008)
ISBN-10: 0-596-52787-X
ISBN-13: 978-0-596-52787-7

Required software and/or hardware

All software required for use in this unit can be accessed from allocated campus laboraties/tutorial rooms.

The software used in this unit consists of:

• Adobe Flash CS4 Professional
• Adobe Photoshop CS4
• Adobe Illustrator CS4

30 Day Trial/Evaluation versions of the named software can be dowloaded for personal use if neccessary from the following websites:

• http://www.adobe.com/

Equipment and consumables required or provided

Study resources

Study resources we will provide for your study are:

available on the FIT2012 web site on MOODLE. It will host lecture slides, weekly tutorial requirements and assignment specifications. In addition, assigned homework tasks and supplementary resources will also be posted.

Overview

Faculty assessment policy

To pass a unit which includes an examination as part of the assessment a student must obtain:

• 40% or more in the unit's examination, and
• 40% or more in the unit's total non-examination assessment, and
• an overall unit mark of 50% or more.

If a student does not achieve 40% or more in the unit examination or the unit non-examination total assessment, and the total mark for the unit is greater than 50% then a mark of no greater than 49-N will be recorded for the unit.

The unit is assessed with one major assignment with 3 major project milestones and 5 minor project milestones (60%) and a three hour closed book examination (40%). To pass the unit you must:

Assignment tasks

Assignment coversheets

Assignment coversheets are available via "Student Forms" on the Faculty website: http://www.infotech.monash.edu.au/resources/student/forms/
You MUST submit a completed coversheet with all assignments, ensuring that the plagiarism declaration section is signed.

Assignment submission and return procedures, and assessment criteria will be specified with each assignment.

Assignment submission and preparation requirements will be detailed in each assignment specification. Submission must be made by the due date otherwise penalties will be enforced. You must negotiate any extensions formally with your campus unit leader via the in-semester special consideration process: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html.

• Assignment task 1

  Title:

  Game Development Project

  Description:

  The practical project will be based on the Flash CS4 authoring environment covered during the semester.
  
  From the following game scenarios, select one to develop for your major assessment task. It is important that you select carefully because the Game Design Specifications will be required by Week 3 and a complete navigational/graphical prototype will be required by Week 6. This is to ensure that you have an appropriate amount of time to implement the programming aspects of the game, and to assist in time management of the project.

  • Variation on a "Muncher-style" Game (suitable for novice programmers)
  • A Multi-player Dice Game (suitable for intermediate programmers)
  • Variation on a "Millionaire Hot Seat" Quiz (suitable for advanced programmers)

  The Game Design Specification documentation is designed to outline and organise the development process of the project. Appropriate headings are provided as a guide to what you should include in the design specifications for your selected game project. Be aware that part of your final assessment will include how well you develop your project in accordance to what you stipulate in this document. In other words, a small but completed project will score very well as opposed to a large incomplete one!
  
  The Navigation/GUI Prototype will demonstrate how you have structured your game and show the majority of your interface design. The game components DO NOT have to function for this prototype as dummy data and/or game components can be used to show the overall look-and-feel of the game. The prototype should include a clearly defined internal structure on the time line (as demonstrated in labs), clearly show the main screen elements of the game, and an example of each major screen of the game. [NOTE: the individual screen elements are only there to show their position on the screen and DO NOT have to function at this stage. All that is required is a complete screen layout with appropriate design suited to the game you are developing.]
  
  The final part of this assessment is the submission of a functional game, developed according to the game specification documents submitted in Week 3. Each scenario includes 5 common components for must also be successfully integrated into the final game. These will also be covered in the weekly lab tasks conducted throughout the semester and will be assessed separately but are an integral part of your final mark. These components cover the basic functions or features required to make the game have at least an elementary level of interaction. Additionally, you must successfully integrate the 3 project enhancements as described underthe individual game scenarios. These enhancements cover a range of graphic,animation, audio and programming options to allow students to target their strengths and apply them accordingly. 
  
  Weekly tasks will be available to download from MOODLE. It is expected that students will download the materials relevant to each week's activity. Working through each activity will give students an understanding of various techniques and their suggested application, however, it will be up the each individual student to determine how to best implement these techniques to best suit their needs. 

  Weighting:

  60%

  Criteria for assessment:

  The project will be worth 60% of the final grade and will be marked out of 100. The marks for this project will be assigned as follows:

  Game Design (40)

  25      Game Design Specification Document to be submitted by Week 3.  For more detailed information see the Game Design Specification section of the Unit Outline document (see below).

  15      Navigation/GraphicPrototype to be submitted by Week 6.  This will demonstrate how you have structured your game and show the majority of your interface design. The game components DO NOT have to function for this prototype as dummy data and/or game components can be used to show the overall look-and-feel of the game.

  Game Implementation (60)

  15      Successful integration of the 5 common project requirements (5 requirements x 3 marks each). These will also be covered in the weekly lab tasks conducted throughout the semester. These are the basic functions or features required to make the game have at least an elementary level of interaction and will be set for submission in Weeks 4, 5, 7, 9 and 10.

  30      Successful integration of the 3 project enhancements in the final project (3 enhancements x 10 marks each). These will also be linked to the weekly lab tasks. These enhancements cover a range of graphic, animation, audio and programming options to allow students to target their strengths and apply them accordingly. The criteria for successful implementation is the enhancement working without error, logical and efficient coding with all extraneous code eliminated, appropriate application of good programming practices (ie: use of commenting, naming conventions,variables, properties, re-usability, etc.).

  15      A functional game, including the integration of the 5 common and 3 specific requirements to be submitted by Week 12. The criteria for this component will include:

  • Interface design and brand development including the overall look-and-feel of the game's graphics/interface, consistency of layout and design, and presentation and readability of content (3).
  • The implementation of Flash features including animation,appropriate use of different symbol types, application of different types of media (image/audio), and Flash components (4).
  • The final product is functional and works without error. Items presented within the game must also function correctly (eg: navigation buttons). Internal and external assets must be organised in a logical structure (eg: using folders, naming, etc.), with appropriate navigation structures implemented (8).

  Due date:

  By 4pm Friday of the specified week or in scheduled Lab times

  Remarks:

  Full details are available in the "FIT2012 Unit Outline 10-2" document that is available for download from the MOODLE site.

Examination

• Weighting:

  40%

  Length:

  3 hours

  Type (open/closed book):

  closed book

  Electronic devices allowed in the exam:

  None

  Remarks:

  The end-of-unit examination will be a test of knowledge on all aspects of the unit from conceptual theories, practical development, interactive design principals and practical developmental tools and techniques. The questions will be drawn from a variety of sources including the textbook, lectures and lab notes.

Due dates and extensions

Please make every effort to submit work by the due dates. It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are not regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.

Students requesting an extension for any assessment during semester (eg. Assignments, tests or presentations) are required to submit a Special Consideration application form (in-semester exam/assessment task), along with original copies of supporting documentation, directly to their lecturer within two working days before the assessment submission deadline. Lecturers will provide specific outcomes directly to students via email within 2 working days. The lecturer reserves the right to refuse late applications.

A copy of the email or other written communication of an extension must be attached to the assignment submission.

Refer to the Faculty Special consideration webpage or further details and to access application forms: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html

Late assignment

Assignments received after the due date will be subject to a penalty of 10% per day (including weekend days).

Assignments received later than one week after the due date will not be accepted for assessment unless prior (alternate) arrangements have been made with the unit Lecturer due to special circumstances.

Return dates

Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.

Feedback

Types of feedback you can expect to receive in this unit are:

Informal feedback on progress in labs/tutes

Graded assignments with comments

Quiz results

Solutions to tutes, labs and assignments