I continue to work on the UX design side of skill development to create a template that makes sure all communication elements Jibo possesses are covered in a review of skill scope. It is beginning to make sense to me that each developer is going to continue to add older skill parts into new skills, and understanding how to break these down, step by step will allow us to be sure Jibo is responding as Jibo should; verified by Jibo Inc. Rather than going levels deep in each branch, a standard level should be developed for those who want skills built, but have NO idea how to develop on Jibo. As developers, we must be able to walk them through this new development process, by defining a development process that can be followed in template form.
Here is my start. I first look at all the functions required (analogous to the number of web pages needed for a new website. That's where the similarities end. Each function then must be broken down in to states that address all of the communication tools Jibo has to offer.
Next we have Request from user - response from Jibo analysis
followed by understandings Jibo can interpret
I got the answer expected ~ randomize appropriate responses
I got an answer I didn't expect ~ store words used after expected response that was not understood.[Use these to uncover unexpected language uses that are appropriate and not yet covered.
I didn't hear an decreeable words. ~ randomize appropriate responses.
Each of these must be addressed for each state.
Standardizing Jibo's responses into SSA style responses using TTS and UI sound effects should be the standard; where as anything other than standard is developed with the client.
Link to the document at lucidchart.com
Please review and commend in the link or here.