Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To this end, create a single team and separate log book in which for each team member adds , in which you add the main activities that s/he you worked on during the project. We recommend that ask you to use a simple text file for this that can be shared with all team members and add it to your Git . The name of this file should be your full name (firstname_lastname.txt). You should add this file to your git repository in a folder named org at the start of the project, and regularly update and commit(!) it to the repo. This will also make sure your TA has access to your log book from the start of the project.

Structure

...

and content

Structure your log book by creating a Week 1, Week 2, etc. heading), and add individual team member sections by adding your full name for each week. 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 you need to work 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 beare:

Tip
  • 79-1: Created the Dialogflow agent, downloaded the JSON key file, and updated the flowkey and flowagent parameters in the .mas2g file.

  • 712-1: Updated the Prolog rule for applyFilter for the cuisine filter.8Added the c10 greeting pattern.

  • 12-1: Tested the addFilter recipeRecommendation intent and added new training phrases to make it more robust.

...