Welcome to FIT2012 Digital Media Authoring for Semester 1, 2009. This 6 point unit is part of the Multimedia Applications major of the Bachelor of Information Technology and Systems degree. The unit has been designed to provide you with an understanding of the principles and practices of programming within a multimedia authoring environment. It explores developing applications using the current version of Flash and ActionScript 3.0.
At the completion of this unit students will have a theoretical and conceptual understanding of:
At the completion of this unit students will have developed attitudes that enable them to:
At the completion of this unit students will have the skills to:
At the completion of this unit students will have developed the teamwork skills needed to:
FIT2012 Digital Media Authoring is a core unit in the Bachelor of Information Technology and Systems - Major in Multimedia. It is a pre-requisite for FIT2016 Human Computer Interaction for Multimedia, FIT3039 Studio 1, FIT3033 Principles of Educational Multimedia.
Monash is committed to ‘Excellence in education’ (Monash Directions 2025 - http://www.monash.edu.au/about/monash-directions/directions.html) and strives for the highest possible quality in teaching and learning.
To monitor how successful we are in providing quality teaching and learning Monash regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through Unit Evaluation Surveys. The University’s Unit Evaluation policy (http://www.policy.monash.edu/policy-bank/academic/education/quality/unit-evaluation-policy.html) requires that every unit offered is evaluated each year. Students are strongly encouraged to complete the surveys as they are an important avenue for students to “have their say”. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.
Faculties have the option of administering the Unit Evaluation survey online through the my.monash portal or in class. Lecturers will inform students of the method being used for this unit towards the end of the semester.
Contact hours : Tuesday 1-2pm & 4-5pm
Contact hours : Monday 11-12noon; Tuesday 1-2pm
Lectures will be used to present and explain programming principles and practices within the context of the authoring environment of Flash.
Laboratories will be used for practical experience in the development, coding, testing and debugging of the functions specific to the authoring environment.
Monash aims to provide a learning environment in which students receive a range of ongoing feedback throughout their studies. You will receive feedback on your work and progress in this unit. This may take the form of group feedback, individual feedback, peer feedback, self-comparison, verbal and written feedback, discussions (on line and in class) as well as more formal feedback related to assignment marks and grades. You are encouraged to draw on a variety of feedback to enhance your learning.
It is essential that you take action immediately if you realise that you have a problem that is affecting your study. Semesters are short, so we can help you best if you let us know as soon as problems arise. Regardless of whether the problem is related directly to your progress in the unit, if it is likely to interfere with your progress you should discuss it with your lecturer or a Community Service counsellor as soon as possible.
| Week | Topic | Study guide | References/Readings | Key dates |
|---|---|---|---|---|
| 1 | Overview of the Unit, Overview of Flash Basics, Game Development & Design Principles | Assignment Overview & Documentation, Drawing tools and techniques, Appropriate organisation of timeline | Green: 1 and 2 | Complete Lab tasks |
| 2 | Flash Symbols, ActionScript Basics, Navigation & Events | Applying interactive affordance in Flash, Navigation working with buttons, Drop Menus, MovieClip behaviour and hierarchy | Green: 3 and 4; Shupe: 1, 2 & 5 | Complete Lab tasks |
| 3 | Flash Animation Basics | Animation in Flash Using Tweening Techniques, Motion Guides and Masks | Green: 6 & 7 | Submit completed Game Specification Document |
| 4 | Using Flash Components, Input and Form Elements | Create a basic component-based form, Accept input from components and store in variables | Green: 9 | Complete Lab tasks and Submit Splash Animation |
| 5 | Scripted Animation, MovieClip objects | Linking objects to MovieClips, using the Flash Display List feature, conditional programming | Shupe: 4, 7, 8, 9 | Complete Lab tasks and Submit Options Selections |
| 6 | Reading from text and XML files), using variables to track data, random numbers | Using externally loaded SWF content, Load data from text and XML files, exploring Flash's built-in random function | Green: 11; Shupe: 14 | Complete Lab tasks and Submit Navigation / Graphic Game Prototype |
| Mid semester break | ||||
| 7 | Flash object oriented design, Introduction to custom classes | Planning and creating an external class, Public/private methods and variables | Shupe: 3 & 6 | Complete Lab tasks and Submit Randomisation |
| 8 | Exploring keyboard events, Using Movie Clips to Change States | Capturing keyboard events, Moving objects with the keyboard, collision detection | Shupe: 3 & 10 | Complete Lab tasks |
| 9 | Advanced ActionScript Techniques, Arrays, Math functions, Strings and Saving Data | Using arrays, random numbers, text formatting and saving data in context by building simple applications | Green: 6; Shupe: 4, 6 & 10 | Complete Lab tasks and Sumbit Data Tracking |
| 10 | Using Sound Objects and Video in Flash | Basic use of externally loaded streaming content (background music and effects), FLV video with Flash Video components | Green: 5 & 8; Shupe 11 & 12 | Complete Lab tasks |
| 11 | Optimising Flash for Web and CD Publishing | Demonstrating using a Pre-loader,Programming Checklist, Debugging and Tweaking Game Code | Green 13; Shupe 13 | Submit Music and Sound Effects |
| 12 | Publishing Flash Movies - CSS, HTML | Additional web publishing techniques | Green 4 & 10; Shupe 13 | Submit completed Game Development Project |
| 13 | Revision | Student Game Demonstrations | ||
Foundation Flash CS4 for Designers
By Tom Green, David Stiller
Friends of Ed (2008)
ISBN-10: 1-4302-1093-1
ISBN-13: 978-1-4302-1093-1
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
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.
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:
30 Day Trial/Evaluation versions of the named software can be dowloaded for personal use if neccessary from the following websites:
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, supplementary resources may also be posted.
The Monash University Library site contains details about borrowing rights and catalogue searching. To learn more about the library and the various resources available, please go to http://www.lib.monash.edu.au.
The Educational Library and Media Resources (LMR) is also a very resourceful place to visit at http://www.education.monash.edu.au/library/
All unit and lecture materials are available through MUSO (Monash University Studies Online). Blackboard is the primary application used to deliver your unit resources. Some units will be piloted in Moodle. If your unit is piloted in Moodle, you will see a link from your Blackboard unit to Moodle (http://moodle.monash.edu.au) and can bookmark this link to access directly. In Moodle, from the Faculty of Information Technology category, click on the link for your unit.
You can access MUSO and Blackboard via the portal: http://my.monash.edu.au
Click on the Study and enrolment tab, then Blackboard under the MUSO learning systems.
In order for your Blackboard unit(s) to function correctly, your computer needs to be correctly configured.
For example:
For more information, please visit: http://www.monash.edu.au/muso/support/students/downloadables-student.html
You can contact the MUSO Support by phone : (+61 3) 9903 1268
For further contact information including operational hours, please visit: http://www.monash.edu.au/muso/support/students/contact.html
Further information can be obtained from the MUSO support site: http://www.monash.edu.au/muso/support/index.html
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:
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 5. 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.
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)
30 Game DesignSpecification Document to be submitted by Week3. For more detailed information see the Game Design Specification section of the Unit Outline document (see below).
10 Navigation/GraphicPrototype to be submitted by Week 6.This will demonstrate how you have structured your game and show the majorityof 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 11.
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:
Due date : By 4pm Friday of the specified week
Remarks ( optional - leave blank for none ) :
Weighting : 40%
Length : 3 hours
Type ( open/closed book ) : closed book
Remarks ( optional - leave blank for none ) :
Major project milestones will be submitted by 3pm Friday of the week that they are due to the designated submission box on a CD-ROM and with the appropriate paper Asignment Cover Sheet correctly filled out and attached.
These are available from the Berwick and Caulfield School of Information Technology offices in Building 903 or on level 6 of building H respectively. Further instructions will be provided with the assignment specifications.
The due dates for the submission of assignments are given in the previous section. 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 seldom regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.
Requests for extensions must be made to the unit lecturer at your campus at least two days before the due date. You will be asked to forward original medical certificates in cases of illness, and may be asked to provide other forms of documentation where necessary. A copy of the email or other written communication of an extension must be attached to the assignment submission.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.
Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.
Assessment for the unit as a whole is in accordance with the provisions of the Monash University Education Policy at http://www.policy.monash.edu/policy-bank/academic/education/assessment/
We will aim to have assignment results made available to you within two weeks after assignment receipt.Plagiarism and cheating are regarded as very serious offences. In cases where cheating has been confirmed, students have been severely penalised, from losing all marks for an assignment, to facing disciplinary action at the Faculty level. While we would wish that all our students adhere to sound ethical conduct and honesty, I will ask you to acquaint yourself with the University Plagiarism policy and procedure (http://www.policy.monash.edu/policy-bank/academic/education/conduct/plagiarism-procedures.html) which applies to students detected plagiarising.
In this University, cheating means seeking to obtain an unfair advantage in any examination or any other written or practical work to be submitted or completed by a student for assessment. It includes the use, or attempted use, of any means to gain an unfair advantage for any assessable work in the unit, where the means is contrary to the instructions for such work.
When you submit an individual assessment item, such as a program, a report, an essay, assignment or other piece of work, under your name you are understood to be stating that this is your own work. If a submission is identical with, or similar to, someone else's work, an assumption of cheating may arise. If you are planning on working with another student, it is acceptable to undertake research together, and discuss problems, but it is not acceptable to jointly develop or share solutions unless this is specified by your lecturer.
Intentionally providing students with your solutions to assignments is classified as "assisting to cheat" and students who do this may be subject to disciplinary action. You should take reasonable care that your solution is not accidentally or deliberately obtained by other students. For example, do not leave copies of your work in progress on the hard drives of shared computers, and do not show your work to other students. If you believe this may have happened, please be sure to contact your lecturer as soon as possible.
Cheating also includes taking into an examination any material contrary to the regulations, including any bilingual dictionary, whether or not with the intention of using it to obtain an advantage.
Plagiarism involves the false representation of another person's ideas, or findings, as your own by either copying material or paraphrasing without citing sources. It is both professional and ethical to reference clearly the ideas and information that you have used from another writer. If the source is not identified, then you have plagiarised work of the other author. Plagiarism is a form of dishonesty that is insulting to the reader and grossly unfair to your student colleagues.
The university requires faculties to keep a simple and confidential register to record counselling to students about plagiarism (e.g. warnings). The register is accessible to Associate Deans Teaching (or nominees) and, where requested, students concerned have access to their own details in the register. The register is to serve as a record of counselling about the nature of plagiarism, not as a record of allegations; and no provision of appeals in relation to the register is necessary or applicable.
The Faculty of Information Technology is committed to the use of non-discriminatory language in all forms of communication. Discriminatory language is that which refers in abusive terms to gender, race, age, sexual orientation, citizenship or nationality, ethnic or language background, physical or mental ability, or political or religious views, or which stereotypes groups in an adverse manner. This is not meant to preclude or inhibit legitimate academic debate on any issue; however, the language used in such debate should be non-discriminatory and sensitive to these matters. It is important to avoid the use of discriminatory language in your communications and written work. The most common form of discriminatory language in academic work tends to be in the area of gender inclusiveness. You are, therefore, requested to check for this and to ensure your work and communications are non-discriminatory in all respects.
Students with disabilities that may disadvantage them in assessment should seek advice from one of the following before completing assessment tasks and examinations:
Deferred assessment (not to be confused with an extension for submission of an assignment) may be granted in cases of extenuating personal circumstances such as serious personal illness or bereavement. Information and forms for Special Consideration and deferred assessment applications are available at http://www.monash.edu.au/exams/special-consideration.html. Contact the Faculty's Student Services staff at your campus for further information and advice.