This module is supported by a customized online textbook Software Engineering for Self-Directed Learners (TIC2002 edition), integrated into this module website. While it is in a dynamic Web page format, there is a way to save the main text as pdf files. Printer-friendly versions have been provided too. In addition, a PDF version of the full textbook will be provided at the start of the semester, via LumiNUS.

• The project is to be done individually.
• The project based on a generic project called Duke.
• In the project, you will build a small chatbot, using Java.
• 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 weekly increments will be common to all students, while some will vary from student to student. 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.

Week 13: Final submission

Deadline:

• Soft deadline (for the project report): Wed, Apr 13th 2359 (Wednesday of week 13)
  Hard deadline (for all submissions): Sun, Apr 17th 2359 (Sunday of week 13)
  An extra week can be given (upon request) for a small late submission penalty of -2 marks.

• What's the difference between the soft deadline and the hard deadline? You can get prof's feedback on a draft of the project report up to the soft deadline. Note that feedback on project report draft will be high-level feedback only (reason: the report is graded). To receive feedback, email a draft of the report to the prof before the soft deadline.

• Submissions later than the hard deadline 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. Source code of the working program: push to your GitHub repo
2. Product: Create a JAR file for the final version of the code and submit to LumiNUS, name: {YourName}.jar e.g., JunHao.jar
3. Documentation: a single .docx (preferred) or a pdf file that follows the template file given (available in LumiNUS/Files/Handouts).
   Submission: Upload to LumiNUS. The file name should be your name e.g., JunHao.docx
4. Demo video:
   • Record a demo video showcasing the features of your product.
   • 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: Name the file with your name (to match the jar and the report file) and upload to LumiNUS.

Git, SourceTree

We'll be using Git as our revision control tool (compulsory).

If you are not familiar with Git already, install SourceTree (a GUI for Git, but also contains Git) on your computer.

GitHub

We'll be using GitHub for code hosting (compulsory).

Create a free GitHub account if you don't have one already.

Coursemology

We'll be using Coursemology for coding exercises (compulsory).

• You'll receive the invitation link near to the first lecture.
• More info about assignment submission will be given in the first week's lecture.

Intellij IDEA

We'll be using Intellij IDE for programming. While using Intellij is not compulsory, there will be no help/instructions given for other IDEs.

Install Intellij on your computer. You may use the Community Edition (free) or the Ultimate Edition (free for students).

There is no midterm exam. Information about the final exam is given below.

1. The final exam will be as per the normal exam schedule (you can check exam time from NUSMods), and will count for 60% of the final grade.
2. The exam will be done face-to-face, but using Examplify. SCALE is not allowing remote exam this semester except in some special cases.
   Please use these resource if you haven't used Examplify in the recent past (the behavior may be different from the version you used last semester):
   • slides (refer to the slides on On-Campus exam)
   • video (refer to the Examplify Student Briefing video)
   • try a few practice exams provided in the above two
   • write to NUS CIT (citbox25@nus.edu.sg) if you run into any technical issues
3. You will need to bring your own laptop, which can connect to the NUS wifi network.
4. Recording of your PC screen is not required.
5. Soft copies of notes: only PDF format is allowed. Other formats (e.g., MS Word, .txt, html) are not allowed. No limitation on what the PDF file contains or the number of PDF files to be used.
   You may use any hard copies or written materials too.
6. The Browser should only be used to accessthe module website (including relevant se-education.org pages e.g., Java coding standard). Accessing other websites is not allowed.
   In case the WiFi is disrupted during the exam, have a soft copy of the textbook, the coding standard, and any other relevant document on your computer too.
7. Download the exam (both parts) before you come to the exam. We'll give you the password for opening the exam paper at the starting time of the exam.
8. If you have a doubt/query about a question, or want to make an assumption about a question, please write it down in the 'feedback' text box. Do not try to communicate those with the invigilator during the exam. We'll take your doubt/query/assumption into account when grading. For example, if many had queries about a specific question, we can conclude that the question is unclear and omit it from grading.

Submitting feedback for a question:

1. Click on TOOL KIT.
2. Click on the NOTES tab, if it is not selected already.
3. Type in your feedback in the text box.
4. Tick the REQUEST FEEDBACK checkbox. If you don't, the feedback will not be saved!!!

---

9. Bring your computer fully charged (and bring the charger too), although some charging points will be available at the exam venue.

Format

• The exam will be divided into 2 parts.

Final exam - part 1

• This exam contains 16 MCQ questions. All questions are estimated to be equal size/difficulty.
• You only need to answer 15 questions correctly to get full marks. The extra question is there to cushion you against careless mistakes or misinterpreting a question.
• Questions will appear in random order.
• You will not be able to go back to previous questions.
  Reasons:
  1. to minimize opportunities for collusion
  2. not unreasonable for the materials tested and the proficiency level expected -- i.e., when using this knowledge in a real life SE project discussion, it will be rare for you to go back to revise what you said earlier in the discussion
• Duration: 45 minutes (recommended: allocate 2.5 minutes per question, which gives you a 5 minutes buffer)
• You are required to give a justification/rationale for your answer. The question will specify what should be included in the justification. Answers without the correct justification may not earn full marks. However, we'll give full marks up to two correct answers (per 16 questions) with missing/incorrect justifications (to cater for cases where you accidentally proceeded to the next question before adding the justification).
  Submitting the justification for a question is the same as submitting feedback for a question (explained above), repeated below for your reference:

• Here is an example question. The answer is a and the justification can be OOP is only one of the choices for an SE project.

• Here is another example question. Note the [SELECT ALL] which tells you that this question can have multiple correoct answers and you need to select all of them i.e., it is a checkbox type question
  The answer is A, B, C (and the rationale is A and B).

Final exam - part 2

• Similar to part 1 (e.g., 16 questions, same length).

Exam briefing, mock exam, practice exam paper

• There will be an exam briefing in the penultimate lecture. It will include a minimal mock exam, just to help you understand the structure.
• You will be given a practice exam paper (at least half the size of the full paper) to help you practice timing. That practice paper will be released at least one week before the exam.