|
|
|
COMP3100/3500/4500
-
Software Engineering Group Projects
|
|
Proposed assessment scheme (to be confirmed in week 1)
|
The table shown below lists each of the assessment items that must be completed during the course. As noted in the table, some items are to be completed by individual students, while others are to be completed by teams.
Student marks will be determined as noted in the table.
Moderation
Final marks may be moderated by the School of Computer Science examiners' meeting.
Assessment Items
| Week Due
|
Semester One
|
Marks
|
| Weeks 8 and 9 |
Project Review 1
During the year, each team will participate in three Project Reviews. Each review will be conducted during a 1.5 hour meeting attended by the project team, academics (including the course examiners and others) and client representatives. They will be held at the end of terms 1, 2 and 3, and will comprise the following components:
- 15 mins: Setup. The team will ensure that all computers, software and data are ready for the review.
- 15 mins: Team Leader Presentation. Team leaders will provide an overview of what was planned for the term, what was achieved, what was not achieved (and why), the major activities undertaken by each team member and objectives for the next stage of the project.
A PDF copy of the presentation shall be made available to your client, mentors and the course examiners in advance of the review.
- 60 mins: Questioning. Academics and clients will question the team about all aspects of the project to date. In the case of COMP4500 students, the focus will be on project management. For COMP3100/3500 students, the focus will be on technical aspects of the project.
Teams will be required to have on-line or local access to all project artefacts including documents, source code, repository and other logs, running software, web sites and specialised hardware. During the review, team members will be expected to quickly locate and display requested information. They must be able to demonstrate any running code.
Note that Project Reviews will not be a simple presentation and a few questions. They will act as a form of examination, and as such, questioning of EVERY team member will be thorough.
Assessment.
The course examiners and team mentors will use these project reviews to assess the state of each project and award a team mark that reflects project progress. A mark for each individual student will then be determined by adjusting the team mark (up or down) depending on the student's contribution. This contribution will be determined by considering student performance during the review, observations made by mentors during mentor meetings, and peer assessments.
|
20 |
| Week 8 |
Peer Assessment 1
Each student shall prepare a Peer Assessment Report using the supplied template.
Completed reports must be submitted to the Chair of Examiners.
Assessment.
Peer assessments are mandatory, but they do not attract any marks.
|
N/A
|
| Week 7 |
Project Poster
The team shall create a poster summarising:
- Project context - client, current situation, need for new system
- Concept for new system - architecture, functions, processes
- Expected impact of new system
Assessment.
Posters will be assessed by the course examiners and all team members will receive the same mark.
|
5
|
| Week Due
|
Semester Two
|
Marks
|
| Weeks 1 and 2 |
Project Review 2
Details as per Project Review 1.
|
20
|
| Week 1 |
Peer Assessment 2
Details as per Peer Assessment 1.
|
N/A
|
| Week 2 |
Reflective Report
Each student shall submit an individual reflective report that addresses the following issues:
- What activities have you undertaken?
- What value did they deliver to the project and why?
- What obstacles have you encountered and how did you overcome them?
- What have you learned?
In addition to the above issues, COMP3500 students must also address the following:
- What lessons will you take into COMP4500 or COMP4540?
Assessment.
Reflective reports will be marked by team mentors.
|
10
|
| Weeks 9 and 10 |
Project Review 3
Details as per Project Review 1.
|
20
|
| Week 10 |
Peer Assessment 3
Details as per Peer Assessment 1.
|
N/A |
| Week 12 |
Pre-showcase Presentation
Each team shall deliver a 10 minute presentation that demonstrates the software they have developed during the course.
Following the presentation, teams will be subject to 5-10 minutes of questioning by attendees.
Teams may invite their clients to attend these presentations.
Assessment.
Presentations will be assessed by the course examiners and team mentors, and all team members will receive the same mark.
|
5
|
| Week 12 |
Software and artefact submission
At the end of the project, each team shall deliver all final project artefacts to their client and the course examiners.
Artefacts shall be delivered on CD and hard-copy as appropriate. Two copies of electronic media shall be delivered.
Assessment.
The course examiners and team mentors will determine a team mark for each team's final deliverables. A mark for each student will then be determined by adjusting the team mark (up or down) depending on the student's contribution. This contribution will be determined by considering observations made by mentors during mentor meetings, and peer reviews.
|
20
|
| Week 12 |
Peer Assessment 4
Details as per Peer Assessment 1.
|
N/A |
| Week 13 |
Showcase
All students are required to participate in the Project Showcase. This Showcase will be attended by clients, industry representatives, academics, students and other invited guests. This is your opportunity to show off your year's work and maybe to interest someone in employing you.
From the pre-showcase presentations, two or three teams will be selected to provide a formal presentation of their work to Showcase guests.
Assessment.
Participation in the Showcase is mandatory, but it does not attract any marks.
|
N/A
|
|