Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The information provided here should be sufficient for you to complete the project. For those of you who are interested and want to learn more about conversational patterns and the related coding scheme that we use here (e.g. C4, etc.), see: Moore, R. J., Arar, R. (2019), Conversational UX Design: A Practitioner's Guide to the Natural Conversation Framework. ACM.

Background Knowledge Preparation

Before beginning your project we would like you all to familiarize yourself with some background knowledge needed to successfully complete your project. These tools are Git and Dialogflow.

Everything we think you need to know can be found here:

2023: Getting Started: What to Know About Git and DialogFlow

To test your knowledge of these subjects there are two Canvas quizzes on the subjects that must be completed.

Team Forming and Initial Set Up

By the end of the week, you will need to form teams of 5 and begin to prepare for your project. Roles are divided in this project into three categories: Dialogflow and Filters(2); Visual Support(1); and Patterns and Responses(2). The number in parenthesis is the number of people we recommend you assign to each category. You will still need to work together in many regards, so make sure there is still communication between categories. Together you will set up your project and familiarize yourself with the project tools.

Instructions for the tools and set up can be found here:

2023: Getting Started: The Tools Used

The Roles: D&F, VS, P&R

Dialogflow and Filters

Visual Support

The Visual Support team will incorporate visuals to enrich the conversation. If you have chosen this role we recommend familiarizing yourself with the task by reading our guide.

Visual Support: A Guide

Patterns and Responses

Week - 1 Deliverable

For your Week-1 submission, you need to submit a weekly progress report in .doc format (See Guidelines).

  • No labels