• The project is to be done individually.
• The project based on a generic project called Monty.
• In the project, you will build a small chatbot, using Python.
• The project is to be done in small increments. You will be given a schedule of what increments to be done in each week.
• Some project increments will be common to all students, while some will vary from student to student (to be announced near to the date). That means your final product will be unique in terms of total features, but some features will be common to other students in the class.
• Constraints:
  1. You should not use relational/SQL databases e.g., MySQL
  2. The software should work in a Windows computer that has Python 3. If your software needs other software to be installed (e.g., third-party libraries), please get prof's permission first.

Week 13: Final Submission

Submission Deadline: Sunday of week 13 (2024-11-17 23:59).

• An extra week can be given (upon request) for a small late submission penalty of -2 marks.
• Submissions later than the above one-week extra time are liable to a late submission penalty, to be fair to those who submitted on time. But given you are part-time students, late submission penalty will be more lenient than otherwise (e.g., -1 per day) and will be on a case-by-case basis.

Deliverables:

1. Code of the working program: zip (not rar) the code.
   • Submission: via Canvas assignments
   • File name: {Your Name}.zip e.g., Jun Hao.zip
2. Project report: a single .docx or a pdf file that follows the template given (template file will be available in Canvas).
   • Submission: via Canvas assignments
   • File name: {Your Name}.docx/pdf e.g., Jun Hao.docx
   • Optionally, you can get feedback on an early project report draft by emailing it to the prof no later than 2024-11-13 (i.e., week 13 Wednesday). Note that such feedback will be limited to high-level comments only (reason: the report is graded), and given only once per student.
3. Demo video:
   • Record a demo video showcasing the features of your product. You can use any screen recording software for this. One simple way is to start a Zoom meeting and record the meeting while screen-sharing your demo.
   • Use the exact version of the code you submitted (i.e., the demo should match the submitted code exactly).
   • Recommended length 7 minutes, max length 10 minutes.
   • Audio narration is optional if the demo can be understood without the audio.
   • Ensure the video is in a format that can be played by any computer.
   • Submission: via Canvas assignments
   • File name: {Your Name}.mp4 e.g., Jun Hao.mp4
4. Code Reuse Declaration:
   • Submit the Canvas survey 'Code Reuse Declaration' when it opens in week 13, to declare your level of code reuse in the project.
   • This is compulsory. You must submit this even if you did not reuse any code.

Deadlines

• Deadline for weekly tasks:
  • If a specific deadline is given, adhere to that.
  • If no specific deadline is given,
    • Soft deadline: try to complete tasks allocated to a week before the following lecture.
    • Hard deadline: In case you fail to meet the soft deadline, there will be no penalty if a task is done within one week after the soft deadline.

Plagiarism

• You may view/discuss others' work or get help from others. However, the work you submit should be your own. In case of similar submissions, marks will be divided among those submissions e.g., if your submission scored 8/10 and there is another submission that is similar to your work (beyond coincidental similarity), each submission will get 4 marks (new policy: NUS requires all plagiarism cases to reported to the university).
• If you reuse/adapt code from elsewhere (e.g., from an online site such as stackoverflow), you must cite the source in the code. e.g.,

  # Solution below adapted from https://stackoverflow.com/a/16252290
  {Your implementation of the reused solution here ...}