The University of Western Australia
School of Computer Science and Software Engineering

School of Computer Science and Software Engineering

CITS5551/CITS5552 Software Engineering Design Project

Project Management Proverbs

Nothing is impossible for the person who doesn't have to do it himself.

The sooner you begin coding the later you finish.

Any project can be estimated accurately (once it's completed).

The most valuable and least used WORD in a project manager's vocabulary is "NO".

The most valuable and least used PHRASE in a project manager's vocabulary is "I don't know".

It takes one woman nine months to have a baby. It cannot be done in one month by impregnating nine women.

You can con a sucker into committing to an impossible deadline, but you cannot con him into meeting it.

At the heart of every large project is a small project trying to get out.

If you don't stand for something, you'll fall for anything.


The project is a capstone experience in which students integrate and apply knowledge and skills acquired in earlier units to a substantial real-world design challenge relevant to their discipline. Students work in teams, typically with four to six members, and are supervised by an academic and/or industry mentor. Teams are responsible for managing their project as well as reporting against milestones and preparing the necessary design documentation. The academic objectives of the project are to lead students through a systematic engineering design and synthesis process and to better prepare them for professional practice as engineers. The focus of this unit is on teamwork skills and the design process.

Unit coordinator: Dr Tim French
Consultation: Monday 12-2pm in CSSE Rm 2.14.


Friday 10-11, CSSE rm 2.28
There is a weekly seminar that will be used for general unit information, guest seminars from industry and student presentations. All students are expected to attend every week. The tentative schedule is:
Week Date Topic
1 4 August Unit Introduction progress reports and project assignment
2 11 August Requirements gathering, client interaction and IP
3 18 August Using GIT
4 25 August Testing, validation and CI
5 1 September (CITS5551) Requirements documentation and prototype development
6 8 September (CITS5551) Essay topic discussion
7 15 September CITS5551 Tech Seminars
10.00: Group 8
8 22 September CITS5551 Tech Seminars
10.00 Group 9
- 29 September Midsemester break
9 6 October CITS5551 Tech Seminars
10.00: Group 10 Prototypes and presentations discussion.
10 13 October CITS5552 final presentations
10.00: Engineering Portfolio
10.30: Indoor Navigation
11 20 October CITS5551 final presentations
10.00: Underground Localisation
10.30: Robot VR
12 27 October CITS5551 final presentations
10.00: Akumen Slack-bot
10.30: Early Dementia Detection
11.00: Zika Virus Modelling
13 3 November CITS5551 prototype presentations
10.00: Group 8
10.20: Group 9
10.40: Group 10


The assessment for CITS5551 consists of reflective writing, a technology seminar, the preparation of requirements document. The unit allows for students, working as a team, to negotiate their own deliverables, the formats of those deliverables and their own metrics for success.
  • The reflective writing exercise will involve students writing a report on aspects of softwaree project management
  • Technology seminars will be presented by students to the rest of their group. Students should identify a technology area relevant to their project, and present a strategic analysis on whether the technology would benefit the project
  • The System Requirement Document is a contract between the team and the client. It should include prototypes and mock-ups, as well as traditional paper documents
The assessment for CITS5552 consists of the delivering the final system, validation of the final system and peer review.
  • The System Delivery is done at the conclusion of the system development. The complete system needs to be presented to the client, all software artifacts need to be handed over to the client, including a user manual.
  • A Maintenance Manual needs to be provided toensure the client has can install, maintain and continue to develop the system
  • The System Validation Document records the validation activities that are used to ensure the quality of the product, as well as a critical assessment of the product based on these measures
  • Students are reviewed by their peers, mentors, clients and themselves on their professionalism and contribution to the final project
The specific items are:
Assessment % of final mark Assessment Dates
Semester 1 start
Reflective Writing 30% 5pm Friday, 3rd November, 2017
Technology Seminars 30% 10am, 15 September, 2017
System Requirements Document and Prototype 40% 5pm Friday, 3rd November, 2017
System Presentation 40% 10am Friday, 13th October, 2017
Maintenance Manual 20% 5pm Friday, 3rd November, 2017
System Validation Document 20% 5pm Friday, 3rd November, 2017
Peer Review 20% 5pm Monday, 10th November, 2017

This Page