As part of the course architecture redevelopment, the 3rd year CS project is being updated to a ?capstone? project running over 12 credit points. This is part 2 of that project.

Introduced for course architecture programs. Effective semester 1, 2016

Reason for changes made on 15/06/2016: Collaborative teamwork is now an explicit ULO.

03/07/2018: Admin - adding Reasons for Change on behalf of CE - this update brings the handbook in sync with FIT3161 as well as Allocate+; which has been discussed with ADE as well as Faculty Admin.

21/09/2020 Admin: Update to include new assessment and teaching approach fields as per Handbook requirements.

19/07/2021 CE: More even distribute of assessments across the semester, and improved tracking of student progress with weekly progress reports.

Core in the BCS degree, capstone research project (part 2).

On completion of this unit, students should be able to:

1. evaluate and select research methods and techniques of data collection and analysis appropriate to a particular project;
2. search, access, and analyse research literature as part of the process of developing solutions to problems;
3. work effectively in collaborative teams;
4. develop and test a substantial piece of software or hardware;
5. explain and reflect upon the purpose, operation, success and value of the developed project in writing and orally;
6. write a report explaining methodology, outlining their contributions and the contributions of others, and documenting the developed project from appropriate perspectives, for instance that of a user, researcher or developer.

0201

This unit provides practical experience in researching, 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 unit is the second part of a 12-credit point project sequence; the first part and entry point for the project is FIT3161.

Recommended resources

Technological requirements

On-campus

Problem-based learning Students (in pair teams) who have completed the initial planning and research in FIT3161 are now required to fully implement their computer science project. Students are encouraged to take responsibility for organising and directing their learning with support from their supervisors.

Seminars

Students will also be introduced to various aspects of computer science research and project development in seminars run by guest lecturers.

In-semester assessment: 100%

1. Journal Entries: - 5% - ULO: 1, 3, 4, 5, 6
2. Interim Presentation: - 5% - ULO: 3, 4, 5
3. Final Presentation: - 10% - ULO: 3, 4, 5
4. Software Deliverable: - 25% - ULO: 1, 2, 3, 4, 5, 6
5. Final Report: - 35% - ULO: 1, 2, 3, 4, 5, 6
6. Team Management: - 5% - ULO: 3
7. Weekly Progress Reports: - 5% - ULO: 1, 2, 3, 4, 5, 6
8. Project Management Reports: - 10% - ULO: 1, 2, 3, 5, 6

Minimum total expected workload equals 12 hours per week comprising:

(a.) Contact hours for on-campus students:

(b.) Additional requirements (all students):

FIT3161