[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]
Monash University

FIT3144 Advanced computer science project - Semester 2, 2013

This unit is intended to provide practical experience in designing, developing and testing a non-trivial computer science project. Projects are generally software-based, although sometimes they may involve hardware development or investigation of theory. Projects cover the whole process of software (or hardware) development, from analysis through design to implementation and testing. Comprehensive written documentation on the project is required. Students are assigned in groups to a project supervisor. There are no lectures in this unit, although students will be expected to attend regular meetings with their project supervisor. The application problem will normally be drawn from the student's field of specialisation.

Mode of Delivery

Clayton (Day)

Contact Hours

1 hr project meeting/wk

Workload requirements

The workload in this unit is equivalent to a 12 credit point unit, i.e. 24 hours study per week.

Contact hours will consist of regular meetings with your supervisor.

Unit Relationships

Prohibitions

CSE3301, FIT3036

Prerequisites

FIT2004 or FIT3140 plus completion of a named minor or of 24 points of units counting towards a named major.

Chief Examiner

Campus Lecturer

Clayton

David Albrecht

Academic Overview

Learning Outcomes

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.

Unit Schedule

Week Activities Assessment
0   No formal assessment or activities are undertaken in week 0
1    
2   Details for the reading unit will be defined and approved individually by the academic supervisor for each student in a learning contract, which will include objectives, assessment details, due dates and an initial reading list. The details of the agreed assessment will be submitted to the Chief Examiner by the end of week 2 of the semester.
3    
4    
5    
6    
7    
8    
9    
10    
11    
12    
  SWOT VAC No formal assessment is undertaken in 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 learning system.

Assessment Summary

Projects are assessed by individual project supervisors.

Assessment Task Value Due Date
Assessment Contract 100% The details of the agreed assessment will be submitted to the Chief Examiner by the end of week 2 of the semester.

Teaching Approach

You will be presented with information and guided on how to best find solutions for a given problem.

Assessment Requirements

Assessment Policy

Faculty Policy - Unit Assessment Hurdles (http://www.infotech.monash.edu.au/resources/staff/edgov/policies/assessment-examinations/unit-assessment-hurdles.html)

Academic Integrity - Please see the Demystifying Citing and Referencing tutorial at http://lib.monash.edu/tutorials/citing/

Assessment Tasks

Participation

  • Assessment task 1
    Title:
    Assessment Contract
    Description:
    Assessment may be comprised of a research paper, project report, or equivalent, but will be equivalent to the workload associated with one 12 credit point unit.
    Weighting:
    100%
    Criteria for assessment:

    Details for this unit will be defined and approved individually by the academic supervisor for each student in a learning contract, which will include:

    • objectives,
    • assessment details,
    • due dates and
    • an initial reading list.
    Due date:
    The details of the agreed assessment will be submitted to the Chief Examiner by the end of week 2 of the semester.

Learning resources

Monash Library Unit Reading List
http://readinglists.lib.monash.edu/index.html

Feedback to you

Types of feedback you can expect to receive in this unit are:
  • Graded assignments with comments

Extensions and penalties

Returning assignments

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). Please note that it is your responsibility to retain copies of your assessments.

Online submission

If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.

Other Information

Policies

Graduate Attributes Policy

Student services

Monash University Library

Disability Liaison Unit

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.

Your feedback to Us

[an error occurred while processing this directive]