[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 knowledge and understanding of:

  • strategies for developing a non-trivial programming, hardware, or theory-based project.
  • how to locate and utilise prior research and methods on a particular topic;
  • how to cite bibliographic references the student has used to understand various components of the project, support claims on knowledge, events, hypotheses and theories;
  • how to document software development from a user and application programming perspective;
  • software development methods: analysis, design, implementation and testing applied to the design and development of a non-trivial project.
Developed attitudes that enable them to:
  • acknowledge the importance of attending and contributing to meetings as a method of gaining important information and ideas about the project;
  • understand the basic requirements of software development from both user and developer perspectives;
  • appreciate the importance of correctly acknowledging the work of others in researching solutions to problems;
  • value the role of work books in documenting a projects progress and keeping track of its development.
Developed the skills to:
  • search, access, and analyse research literature as part of the process of developing solutions to problems;
  • understand the importance of analysis, design, documentation, and testing in developing a non-trivial software project;
  • write a moderately detailed report explaining methodology, outlining their contributions and the contributions of others, documenting the developed project from developer and user perspectives.
Demonstrated the communication skills necessary to:
  • understand the role of the client (or user) in the software development process;
  • appreciate the importance of written communication in documenting project development;
  • understand the importance of assessing time and resource requirements in the successful completion of non-trivial projects;
  • appreciate the importance of time and resource management in order to deliver non-trivial projects to deadlines.

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

Projects are assessed by individual project supervisors.

Assessment Task Value Due Date
Project Specification 20 marks Friday 9 September 2011
Final Demonstration / Presentation 10 marks Week 11 or Week 12 (to be allocated)
Test Report 10 marks Friday 21 October 2011
Workbook 10 marks Friday 21 October 2011
Final Report 50 marks Friday 21 October 2011

Teaching Approach

Problem-based learning
Students are encouraged to take responsibility for organising and directing their learning with support from their supervisors.


Our feedback to You

Types of feedback you can expect to receive in this unit are:
  • Other: Informal feedback on progress in project meetings, and marked project reports

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:

Previous Student Evaluations of this unit

If you wish to view how previous students rated this unit, please go to

Required Resources

For projects students will normally need access to a computer and programming environment.

Individual requirements will be identified by project supervisors.

Unit Schedule

Week Activities Assessment
0   No formal assessment or activities are undertaken in week 0
1 Preliminary Reading  
2 Preliminary Reading  
3 Project Plan  
4 Project Plan  
5 Project Design  
6 Project Design  
7 Test Plan Project Specification due 9 September 2011
8 Implementation & Testing  
9 Implementation & Testing  
10 Implementation & Testing  
11 Presentations Final Presentation / Demonstration due Week 11 (to be allocated)
12 Presentations Final Presentation / Demonstration due Week 12 (to be allocated); Test Report due 21 October 2011; Workbook due 21 October 2011; Final Report due 21 October 2011
  SWOT VAC No formal assessment is undertaken SWOT VAC
  Examination period LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/

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

Assessment Requirements

Assessment Tasks


  • Assessment task 1
    Project Specification
    Includes a project plan, external and internal specifications, and a test plan.
    20 marks
    Criteria for assessment:

    Correctness and completeness of the project plan, external and internal specifications and test plan.

    Due date:
    Friday 9 September 2011
  • Assessment task 2
    Final Demonstration / Presentation
    A demonstration of the software in a working environment.
    10 marks
    Criteria for assessment:

    Quality of working demonstration being presented.

    Due date:
    Week 11 or Week 12 (to be allocated)
  • Assessment task 3
    Test Report
    Report detailing the outcomes of testing.
    10 marks
    Criteria for assessment:

    Completeness of report.

    Due date:
    Friday 21 October 2011
  • Assessment task 4
    A notebook (or computer file) containing weekly entries describing what has been accomplished through the week. Details on how the workbook should be organised are supplied with the project details.
    10 marks
    Criteria for assessment:

    Completeness of workbook, including at least 10 weekly entries.

    Due date:
    Friday 21 October 2011
  • Assessment task 5
    Final Report
    This provides a complete description of the project, the code, its results and interpretation of the results.
    50 marks
    Criteria for assessment:

    Clarity, organisation and completeness of both the report and the code. The quality of the interpretation and analysis of the results will be a significant factor.

    Due date:
    Friday 21 October 2011


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

Returning assignments

Other Information


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

Reading list

Any required or recommended textbooks will be determined by individual project supervisors on a case-by-case basis.

[an error occurred while processing this directive]