Report
The end report should span no more than 10 pages, and discuss the progress, functionality, and results of your project. We recommend writing this in latex.
Use the following structure for your report:
...
explain your agent’s basic conversational features (functionality), discuss the progress you were able to make and how you tested your agent, and the overall findings of your project.
| Note |
|---|
Your report should not exceed 10 pages. You are allowed to add additional materials in appendices of your report (following the 10 main pages that we will grade). Your main report, however, should be self-comprehensive (a reader should get it without having to access the appendices). |
| Info |
|---|
We recommend writing your report in latex. |
Your report needs to have the following structure:
Title
Add a title. Also add your group number, student names, emails, and student numbers right below the title.
Introduction (max. 1/2 page):
...
Briefly introduce your cooking assistant project. Mention each group member’s contribution to the projectrecipe recommendation agent project, and describe your aims for the conversational agent.
How does
...
your agent interact? (1-2 pages):
...
How do components interact with each other to get the conversational agent? You should probably minimally mention the database, patterns, specific MARBEL/GOAL properties like memory and agenda, Dialogflow Intents/Entities, Selection functions and how they work, how visuals work, etc.
Extensions(1-2 pages):
...
Provide a functional specification of your agent, describing its main capabilities and the different flow(s) of the interaction a user can have with the agent. Make sure that you give a complete coverage of the features of your agent, so they can be tested based on your description.
Design choices and rationale (
...
2-
...
3 pages):
In this section, you should describe the different design choices you have made while implementing your agent. Make sure to give motivation to each of them. Design choices are any tasks These design choices are twofold. First, the tasks that are open to interpretation in the instructions. This should include but not be limited to training phrases used (that were not provided), visuals (essentially everything), conversational patterns and agent responses. . Second, the different extensions that you have made, adding among others to, for example, the agent functionalities, persona, conversational directions. Make sure to not only describe these design choices, but also to give a clear motivation.
Agent Testing (1-2 pages):
In this section, you should talk about the way in which you tested your own bot agent continuously. What did you find? Read a bit more about this in Evaluating Your Bot Agent Testing.
...
User Study (2-3 pages):
In this section, you will talk about should explain the testing and data gathered that was described in Data Collection with Your Bot User Study. You should probably very briefly include the test setup, test your goals, data, and results.
Evaluation and Improvements(1-2 pages):
Address the testing that you and the other team did on your bot. If something was identified during testing and you already fixed it that could also be worth mentioning. Identify your FINAL bot’s current advantages and deficiencies. Identify improvements, and describe and motivate how they may be implemented. Evaluate your extensions as well! Why do they improve the bot and how well do they functionthen explain and analyze the data, and discuss lessons learned from your small user study. In the analysis, discuss the performance of some of your extensions separately. To what extent did they improve the interaction with your agent?
Conclusion: (max. 1 page):
Write a brief conclusion about the project itself, as well as a reflection on the process (what went well and what could have been done better?). If, based on the test outcomes, you have ideas on how to improve on the agent if you had more time, this could also be described here.