Assessment and Submission

Assessment Scheme

The Final Project is worth 50% of the total grade for CS3217. The grading for the Final Project will be further broken down as follows:

• 5% Project proposal
• 25% Sprint 1 report/presentation
• 25% Sprint 2 report/presentation
• 5% Poster Session (awarded by external judges)
• 10% Team Presentation on Application of Software Engineering Concepts
• 30% Final report/presentation

This assessment scheme reflects the focus of CS3217. To do well in this module, you and your team need to demonstrate that you can take a set of specifications and implement the specifications well by applying appropriate software engineering principles. In addition to the two major intermediate milestones, each team is expected to meet with the lecturer at least on two other occasions. During these meetings, the lecturer will be asking individual members about the design and also specific questions about the parts of the project that they are coding. Up to 5% of the grade will be assigned to each student arising from these question/answers. This is to make sure that every member of the project team is well-aware of what is happening for the project. Project teams are encouraged to meet to discuss their projects before meeting with the teaching staff.

It should also be clear from the above grade distribution that to do well, it is not good enough to finish the project at the last minute, but to do consistent work. Unlike CS3216, sales (fluff) is not a focus of this class and so the poster session is worth very little. Still, it is very cool to be able to show off your work to your fellow students. :-)

Mode of Submission

The following is the list of the deliverables:

• Source code: all code and relevant files should be pushed to the team's assigned GitHub repository.

• Reports: all reports should be in PDF format and uploaded to the respective workbin in LumiNUS. Note that if you are attaching raster images, the resolution should be high enough to

Good luck!