- Finalize the features
- Set up a product website
- Release the product
Aim to finish the iP by this week!
Although the official iP submission deadline is Week 7 Monday, aim to finish the iP by this week's i.e., 2359 before the tutorialweekly deadline so that you can devote more time to the tP after this week. The extra time for the iP (i.e., from week 6 to 7) is meant as a buffer for those lagging behind in the iP.
1 Finalize the features
- You may give the product any name, but do not rename the repo.
- Reminder: you can give the chatbot any personality (there is no need to follow the exact command/response formats given)
- Remember to give credit to any code you reused or solutions you adopted from others. Reuse without giving credit is plagiarism and will be reported to the university for disciplinary action.
Admin Module Policies → Policy on Reuse
2 Set up a product website
- Add a representative screenshot of the product to the
docsfolder.- The file name should be in the
docsfolder and namedUi.pngexactly (even if the file format is notpng, name itpng) - Ideally, the product name is visible in the screenshot e.g., in the title bar of the Window
- The file name should be in the
Admin Team Project (tP) → Tips for Product Screenshots
- Add a brief User Guide (UG)
A-UserGuide: User Guide Add a User Guide to the project. Here is one simple way to do it.
- Update the given
docs\README.md. See this guide to GitHub flavored Markdown (GFMD). - Go to the settings page of your Duke fork and enable GitHub pages to publish from the
docsfolder (you can select a theme too). - Go to
http://{your username}.github.io/duke/to view the user guide of your product.
- If you added the
Ui.pngcorrectly and set up the product website correctly, you should be able to see your screenshot in the iP Showcase page (a link to the iP Showcase page is also available in the top navigation menu → Links).
3 Release the product
- Create a new jar file using Gradle. Creating jar file using Intellij is not recommended unless the project is very simple.
- Do the following smoke tests to ensure the jar file works (reason: it will be used to grade your iP).
- Copy the jar file to an empty folder and test it from there. This should surface issues with hard-coded file paths.
- Pass the jar file to team members and ask them to do a test drive. Assuming some of your team members' OS differ from yours, this should verify if the app is cross-platform.
- Create a new release on GitHub (e.g.,
v0.2) and upload the jar file.