Masters Software Engineering Project (SWEN90014) // Assessment

Additional details

Each project team of 4-5 students will be assessed based on the engineering artefacts produced during the project and on the deliverables produced at the end of the project. Specific timing of artefacts is dependent on the team's project plan, to be defined in coordination with their supervisor.

80% of each student's mark will be made up from a team mark. All team members will receive the same team mark, unless there are exceptional circumstances to warrant individual marking.

A team’s mark consists of the following components.

1. The engineering analysis, design, release and process-related documentation, requiring approximately 65-70 hours (50%) and including:

• A project management component assessing the team’s ability to manage a repeatable process
• An analysis and design component assessing the team’s ability to apply software engineering principles and techniques to the development of a software system
• A test planning component assessing the team’s ability to apply software engineering knowledge of validation and verification.

2. Final release of Software, in week 12, requiring approximately 35 – 40 hours, (30%) that assesses the team’s ability to develop a non-trivial software system using software engineering principles and techniques

3. 20% of each student's mark will be based on their individual contribution to the project, assessed on the same quality criteria as points 2 and 3

A component of each submission addresses each of the Intended Learning Outcomes (ILOs). ILOs 1, 2, and 4 are specifically addressed by the final release (item 2)

ILO 3 is specifically addressed via the project management component of item 1

All students are expected to participate in team meetings and workshops and contribute towards analysis and process related engineering documentation, coding and other team activities. Each student is expected to spend around 120 hours during the semester for project activities.