[an error occurred while processing this directive] [an error occurred while processing this directive]
[an error occurred while processing this directive]
[an error occurred while processing this directive]

Academic Overview

Learning Objectives

At the completion of this unit students will have -
A theoretical and conceptual understanding of:

  • the roles and responsibilities of clients and developers in a multimedia or games development project;
  • the methodologies, tools and techniques required for delivering a functional multimedia system or game.
Developed attitudes that enable them to:
  • approach the development process ethically and professionally.
Developed the skills to:
  • develop a significant multimedia/game application, primarily testing, evaluation, finalisation, documentation, and delivery;
  • apply project management techniques to a multimedia/game development project;
  • integrate multimedia, programming, and technical skills in the testing and evaluation of a system prototype;
  • develop effective user and system documentation;
  • evaluate personal performance and performance of a development team.
Demonstrated the communication/teamwork skills necessary to:
  • communicate effectively with clients and members of the development team;
  • work effectively in a team.

Graduate Attributes

Monash prepares its graduates to be:
  1. responsible and effective global citizens who:
    1. engage in an internationalised world
    2. exhibit cross-cultural competence
    3. demonstrate ethical values
  2. critical and creative scholars who:
    1. produce innovative solutions to problems
    2. apply research skills to a range of challenges
    3. communicate perceptively and effectively

Assessment Summary

Practical Assignments: 100%. Assignments will include group and individual components.

Assessment Task Value Due Date
Project Plan / Prototype Evaluation 20% Week 5, 25 August 2011, 5pm
Process Journal Submission 1 20% Week 7, 8 September 2011, 5pm
Formal Product Presentation 10% Week 12 (in Studio)
Final Product Delivery and Process Journal Submission 2 50% Week 14, 2 November 2011, 5pm

Teaching Approach

Studio teaching
Studio teaching is a facilitated active, participatory, peer learning approach.

Feedback

Our feedback to You

Types of feedback you can expect to receive in this unit are:
  • Informal feedback on progress in labs/tutes
  • Graded assignments with comments

Your feedback to Us

Monash is committed to excellence in education and regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through SETU, Student Evaluation of Teacher and Unit. The University's student evaluation policy requires that every unit is evaluated each year. Students are strongly encouraged to complete the surveys. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.

For more information on Monash's educational strategy, and on student evaluations, see:
http://www.monash.edu.au/about/monash-directions/directions.html
http://www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html

Previous Student Evaluations of this unit

If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp

Required Resources

There are no specific software requirements for this unit due to the varying nature of the projects chosen. After choosing your project you will be required to use the most appropriate development software. Some general packages that will be of primary use include:

  • Microsoft Project
  • Microsoft Visio
  • Adobe Photoshop and Illustrator
  • Maya
  • Microsoft Visual Studio .Net

Note that software required will be that of all other Multimedia units at Berwick and Games Development units at Caulfield and will be available for student access in computer labs.

Unit Schedule

Week Activities Assessment
0   No formal assessment or activities are undertaken in week 0
1 Unit Expectations, Process Journals  
2 Review of the Project Planning Process  
3 Project Plan Document and Prototype Evaluation  
4 Project Analysis and Project Change  
5 Presentation of Findings Project Plan / Prototype Evaluation due Week 5, 25 August 2011, 5pm
6 Implementing Project Change  
7 Project Development and Research Process Journal 1 due Week 7, 8 September 2011, 5pm
8 Testing Process, Testing Documents  
9 Folios and Careers  
10 System Testing  
11 Presentation Skills  
12 Project Hand-Over Presentation due Week 12 (in Studio); Process Journal 2 and Final Product Delivery due Week 14, 2 November 2011, 5pm
  SWOT VAC No formal assessment is undertaken SWOT VAC
  Examination period LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/
academic/education/assessment/
assessment-in-coursework-policy.html

*Unit Schedule details will be maintained and communicated to you via your MUSO (Blackboard or Moodle) learning system.

Assessment Requirements

Assessment Tasks

Participation

This unit has a group based assessment component of 60% and an individual component of 40%

To pass in this unit a student must obtain:

  • 40% or more in the individual assessment, and
  • 40% or more in the group assessment, and
  • an overall unit mark of 50% or more.

If a student does not achieve 40% or more in the unit group assessment or the unit individual assessment 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.

Due to the nature of group work in this subject, it is expected that all students will attend 100% of classes. Failure to do so may result in difficulties with passing the unit.

If you are absent for more than two tutorial sessions you must supply a medical certificate or other appropriate documentation. For applying for special consideration refer to the link provided under 'Extensions and penalties' at the end of this section.

If you are finding problems with this requirement please ensure you speak to your unit adviser as early as possible. It is your responsibility to ensure that you can make this commitment before you embark on this subject.

Please note that attendance at tutorials without any study outside of allocated class times will not be sufficient to complete the work required.

Make sure you have a copy of the project you are working on with you when you attend classes.

Assessment procedures for a non–performing team member

If the unit assessor, or one or more team members, becomes concerned regarding the contribution of one or more members of a group then the unit assessor will determine, using the project documentation, examination of Process diaries and discussion with the students concerned whether the student or students are making an equitable contribution to the work of the group.

If it is determined that the student or students are not making an equitable contribution to the work of the group they may be deemed to be a non-performing team member.

In the event of this determination being made the group component of their assessment will be multiplied by a factor of up to 0.5 to arrive at a raw score.

  • Assessment task 1
    Title:
    Project Plan / Prototype Evaluation
    Description:
    Project Management is fundamental to success in Studio.

    Students undertaking a one semester project will develop a project plan, which lays the foundation for your project during the semester. In this document you must analyse the problem you are solving and prepare a plan for development of the product. The plan should cover such areas as user requirements, task breakdowns, scheduling, quality issues, and the like.

    Students continuing on a project from FIT3039 will complete a Prototype Evaluation, evaluating the outcomes of FIT3039 and adjusting the initial project plan to reflect any changes to that plan.
    Weighting:
    20%
    Criteria for assessment:
    • Attention to technical detail and scope of project           
    • Clarity & design of layout / inclusion of relevant sections
    • Innovation in application and originality of concept
    • Evidence of research undertaken and testing strategies
    Due date:
    Week 5, 25 August 2011, 5pm
    Remarks:
    Full assignment details will be posted on MOODLE
  • Assessment task 2
    Title:
    Process Journal Submission 1
    Description:
    This is the first submission of your individual project documentation. This consists a journal that should show your contributions and reflection on the project. It will contain written reflections, analysis, drawings, screenshots, and any other material that provides insight into your role on the project. This first submission should place inherent focus on the research and design elements of the project.
    Weighting:
    20%
    Criteria for assessment:
    • Evidence of individual research being undertaken and reflection on learning
    • Discussion of individual designs, brainstorming  and reflection on these activities
    • Discussion of group achievements, successes and problems
    • Evidence of a process / methodology and discussion of skills developed / used
    Due date:
    Week 7, 8 September 2011, 5pm
    Remarks:
    Full assignment details will be posted on MOODLE
  • Assessment task 3
    Title:
    Formal Product Presentation
    Description:
    This is a formal presentation / demonstration of the product, including discussion of the process undertaken.
    Weighting:
    10%
    Criteria for assessment:
    • Clarity of presentation
    • Demonstrated development in skills
    • Demonstrated understanding of key processes undertaken
    • Discussion of problems encountered and solutions implemented
    Due date:
    Week 12 (in Studio)
    Remarks:
    Full assignment details will be posted on MOODLE
  • Assessment task 4
    Title:
    Final Product Delivery and Process Journal Submission 2
    Description:
    This is the delivery of the final product. Delivery includes formal handover of all product content, as well as a second submission of your individual project journal. The journal should show your contributions and reflection on the project. It will contain written reflections, analysis, drawings, screenshots, and any other material that provides insight into your role on the project.
    Weighting:
    50%
    Criteria for assessment:
    • Intuitive / transparent design implementation
    • Suitability of product as a working proof of concept
    • Innovation & originality of content
    • Evidence of individual research being undertaken and reflection on learning
    • Discussion of individual designs, brainstorming  and reflection on these activities
    • Discussion of group achievements, successes and problems
    • Evidence of a process / methodology and discussion of skills developed / used
    Due date:
    Week 14, 2 November 2011, 5pm
    Remarks:
    Full assignment details will be posted on MOODLE

Examinations

Assignment submission

It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/plagiarism-procedures.html) for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at http://www.infotech.monash.edu.au/resources/student/forms/. Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an online quiz).

Extensions and penalties

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.

Returning assignments

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

Other Information

Policies

Monash has educational policies, procedures and guidelines, which are designed to ensure that staff and students are aware of the University's academic standards, and to provide advice on how they might uphold them. You can find Monash's Education Policies at:
http://policy.monash.edu.au/policy-bank/academic/education/index.html

Key educational policies include:

Student services

The University provides many different kinds of support services for you. Contact your tutor if you need advice and see the range of services available at www.monash.edu.au/students The Monash University Library provides a range of services and resources that enable you to save time and be more effective in your learning and research. Go to http://www.lib.monash.edu.au or the library tab in my.monash portal for more information. Students who have a disability or medical condition are welcome to contact the Disability Liaison Unit to discuss academic support services. Disability Liaison Officers (DLOs) visit all Victorian campuses on a regular basis

Responsibility for student work

Students should note that they are, at all times, responsible for their work. All relevant material should be backed up on a regular basis to CD, DVD or Flash disks. The university has CD & DVD burners in the computer labs and blank CDs/DVDs may be purchased through the on-campus bookstore. Loss of assignment work due to hardware failure, virus or theft will not be accepted as reasons for late or non-submission of work. Students must hold an exact copy of all work which they submit for assessment, this copy should be held until your final result for the unit is released.

Reading List

A list of recommended readings will be made available on the unit website. Due to the wide variety of projects, a definitive list will not be available, however some general books that may help include:

Schwalbe, K., Information Technology Project Management 5th Edition

Satzinger, J. W., Jackson, R.B., Burd, S.D. and R. Johnson (2008) Systems Analysis and Design in a Changing World, 5th Edition

Monash University libraries should provide a good selection of technology related texts. For advice on the best choice of text for specific technologies, please speak to unit staff.

[an error occurred while processing this directive]