Your CA3 team grade has been emailed to you, along with some comments. Most team put in extra effort towards the end of the semester and delivered something delightful at the end. Most of the presentation went very well with good demos that impressed me and the examiners. We have a few more teams in the “exceeded expectation” category. Well done!

For individual grades, again, I tried my best to evaluate based on my observation, your edit log, the peer review, and the self-reporting survey. I also check through the commit log on github and read the code submitted. Again, there are students who made clear and excellent contributions beyond what the other team members have done. These individuals received a better grade than the team grade. There are three who clearly serve as the pillar of the team during the implementation period, writing significantly more code than the rest. Bravo!

As per last time, if you feel that your grade is unfair, please do not hesitate to email me before midnight, Sunday, 6 December 2015.

Read more..

The final presentation schedule was posted under Schedule in case you are not aware.

Here is a reminder of the tips I gave during the last lecture.

• Start with a bang. Introduce your team and yourself.
• Give a compelling motivation of your project. If your project aims to solve a problem, explain the problem.
• Give a short demo of your work. A short 2-3 minutes canned demo (in the form of a video with narration) is best.
• Explain the key features of your solution. What are the key/unique requirements?
• Explain how you elicit the requirements (survey? interview?) and highlight key findings.
• Show and explain your design and architecture. Highlight key design decisions.
• Other things you have done: planning, UI evaluation, implementation, code review, testing, continuous intergration, etc, that you think are noteworthy to highlight. Show evidence of what you have done instead of just saying it.
• End strongly with confidence.
• Prepare some backup slides (anticipate what questions will be asked).
• Prepare to cut some content if you run out of time.
• Everyone in the team should take turn to present.

Your CA2 team grade has been emailed to you, along with some comments. With a longer period of evaluation (5 weeks vs. 2 weeks for CA1), my expectation is higher in terms of the amount and quality of work done, so more teams fall below my expectation this time. Only one team that managed to “wow” me and got an “exceeded expectation” grade.

For individual grades, I tried my best to evaluate based on my observation, your edit log, the peer review, and the self-reporting survey. Again, there are a few students who made clear and excellent contributions beyond what the other team members have done. These individuals received a better grade than the team grade. There are also a few who have fallen behind more significantly than others, in terms of contribution to the team, technical aptitude, and doing what is asked (e.g., peer review). I had to give out a “poor” grade for a few of you.

As per last time, if you feel that your grade is unfair, please do not hesitate to talk to me.

Read more..

We will have our last class gathering of the semester this coming Thursday, where the remaining four teams will share their project with the class.

I will also go through some tips and guidelines for your final presentation.

Final Report

The deadline for submitting the final report is 12 November, 2015, 2359.

What should be included in the final report?

The final report should contain at least the following sections (sections marked with [*] are new):

• Introduction
  • What is the motivation behind this project?
  • What is the overall vision or goal of this project?
• Software Requirement Elicitation
  • What activities did you perform to gather/validate the requirements of your project? Include the details (e.g., for user survey, you can mention the questions you asked, who the participants of the survey are, what did you find from the survey, etc). If it gets too long, put the details in the appendix.
• Software Requirements
  • What are the requirements (functional, non-functional) of the project?
  • Remember to include the abuser stories/misuse cases and highlight how you mitigate these with your requirements.
• Software Architecture and Design
  • What is the architecture of the software you are going to build? What are the components? how they interact with each other?
  • What are some major design/implementation decisions that you have made? How did you come about making those decisions? (you may include the QOC)
  • [*] What does the interface looks like? How did you evaluate and improve the usability of your project?
• [*] Software Planning and Project Management
  • How did you prioritize the tasks? plan your sprint? assign tasks to team members?
  • What tools do you use for group communication and management? (provide links)
  • What is the workflow for development? (commit, branching, code review, pull, etc)
• [*] Software Implementation and Testing
  • What has been implemented so far?
  • How much testing has been done? How is it done? (please show evidence)
  • How is code review practiced in the team? (please show evidence)

What makes a good report?

A good report would be something that is well structured, clearly written, and easy to read. Use figures, tables, cross-references, when necessary. The content should flow smoothly from one section to another, with connections between chapters and sections.

The report should NOT be just a concatenation of all your Google Drive documents. Although what you have written so far will constitute a large chunk of the content, care should still be taken to connect all the dots and link the different sections together.

Is the report graded?

The final report will be factored into your CA3 grade.

How to submit the report?

You should submit a single PDF file named team-final.pdf, where team is the name of your team in CamelCase, in one word, into a IVLE workbin that has been created. You only need to submit one copy of the report per team.