Log book
- Koen Hindriks
- Kunneman, F.A. (Florian)
You each should individually maintain and update a weekly log book. You are advised to continuously update your log book.
To this end, create an individual log book in which you add the main activities that you worked on during the project. You should use a simple text file for this that can be shared with all team members. Please name this file logbook-<your full name>.txt. Make sure to add it to your team's Git repo. This will also make sure your TA has access to your log book from the start of the project.
Structure: structure this log book into weeks (create a Week 1, Week 2, etc. heading).
Content: Maintain a simple list of bullets with brief but specific descriptions of each activity that you worked on that fit on 1-2 lines max (do not write paragraphs). You should think about all the different things that should be worked on such as coding, modifying, updating, testing, designing, analyzing, writing, etc. Each item (bullet) in your log book should have the form: <bullet><date>: <activity-description>, where the activity description should start with a verb (indicating what you did). Some good examples would be:
7-1: Created the Dialogflow agent, downloaded the JSON key file, and updated the flowkey and flowagent parameters in the
.mas2gfile.7-1: Updated the Prolog rule for applyFilter for the cuisine filter.
8-1: Tested the addFilter intent and added new training phrases to make it more robust.
The log book will be used to evaluate your participation as a team member within the team. We can use this as a basis for making individual grade differences at the end of the project.