Requirements Management, Marketing Robot

What this includes

• The interaction defined: greeting, waving, dialogue, and what the robot says about your range, services and promotions.
• Operating modes, including what the robot is doing between interactions.
• Perception and communication requirements: what it has to notice, and how it is spoken to.
• Interface specifications for whatever it has to connect to on your side.
• A movement concept, including the optional companion behaviour of walking a customer to a location, with the routes defined.
• Error handling written as a requirement rather than left to the build: what it does when it is blocked, crowded, or asked something it cannot answer.
• Test criteria, so there is an agreed way to say whether it works.
• The deliverable is a written software requirements document with a feasibility assessment, including the cases where the finding is that this should not be built.