Wiki source code of Design Patterns and Ontology
Version 3.1 by Haoran Wang on 2022/02/26 21:09
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | The lecture on design patterns made us really understand how and why to use the personas and their user stories. This means the interactions need to be carefully planned to let in as few gray areas as possible. | ||
| 2 | |||
| 3 | The personas need to be stereotyped so that they can represent a typical stakeholder. However, they also need to have their own specificities, maybe sometimes unusual hobbies, personalities, or behaviors, for instance, to look more authentic and allow for more case testing (after all, nobody is a walking stereotype). | ||
| 4 | |||
| 5 | The design pattern is a reusable high-level solution to a recurrent problem. This means the pattern can be applied to many different but similar situations. | ||
| 6 | To make a design pattern successfully, there is first the need for an ontology, i.e., the main concepts of the application. The upper layer of the ontology is an overview, that generically explains how things are connected, while the lower layers provide specifics for the actual interactions. | ||
| 7 | |||
| 8 | The interactions can also be further described in the user stories (interactions between the robot and users). |