Wiki source code of Design Patterns and Ontology
Last modified by Clara Stiller on 2022/02/23 10:33
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | Before starting with the Design Patterns you should figure out for whom you are designing the technology for: | ||
2 | |||
3 | ==== Personas==== | ||
4 | * First Step is to create Personas to get a feel about who the audience is | ||
5 | * Persona is an individual character, try to make the person "come alive" by adding detailed descriptions | ||
6 | * Profile of a Persona should include: | ||
7 | ○ General information like gender, age, living situation, job/education, hobbies, former life | ||
8 | ○ Personal goals | ||
9 | ○ Stereotypes of the person group, but also untypical characteristics "go beyond stereotypes" | ||
10 | * You should provide one persona for each Stakeholder, sometimes more than one per Stakeholder can be helpful when the character differs a lot per person | ||
11 | |||
12 | ==== Storyboard==== | ||
13 | * Create a story with the Personas as the main character | ||
14 | * Focus on the interactions and relations of the different persons and how do they interact with the robot | ||
15 | |||
16 | |||
17 | |||
18 | Then you can start designing the pattern: | ||
19 | |||
20 | === Design Patterns=== | ||
21 | |||
22 | //"A reusable solution to a recurring problem. [Design] patterns try to | ||
23 | capture the common invariant properties of the problem and the | ||
24 | essential relationships needed to solve the problem. (...) They are | ||
25 | abstract solutions that allow a designer to reuse ideas that worked in | ||
26 | the past for commonly faced problems."// | ||
27 | |||
28 | *Use these factors in your design patterns: | ||
29 | ○ Behavior Pattern | ||
30 | ○ Positive effects | ||
31 | ○ Negative effects | ||
32 | ○ Claims | ||
33 | |||
34 | ==== Team Design Patterns (TDP)==== | ||
35 | * Pattern that shows how the team works together | ||
36 | * Consists of several design patterns which are connected with arrows | ||
37 | * Divided into physical (brick above heads) and cognitive work (colored heads) | ||
38 | |||
39 | [[image:TDP.png]] | ||
40 | |||
41 | ==== Interaction Design Patterns (IDP)==== | ||
42 | * Shows interaction between two people | ||
43 | |||
44 | |||
45 | |||
46 | === Ontology=== | ||
47 | |||
48 | A specification of a conceptualization. That is, an ontology is a | ||
49 | description of the concepts and relationships that exist within a | ||
50 | certain domain. | ||
51 | |||
52 | The Ontology provides a language for the interaction, which ensures a mutual understanding. | ||
53 | Meaning the robot need to has a basic understanding of our world, you have to represent common (abstract) concepts both, robot and human, need to interact (examples: emotions, (music) genres) | ||
54 | |||
55 | example: | ||
56 | [[image:Ontology.png]] | ||
57 | |||
58 | |||
59 | ==== Frame-based Ontology==== | ||
60 | |||
61 | * Frames represent stereotyped situations in the form of a group of | ||
62 | interrelated concepts with a fixed structure (Minsky, 1975). | ||
63 | * Schemata represent situational experiences that are stored in long- | ||
64 | term memory in the form of patterns (Tannen, 1993). | ||
65 | * Frames can be regarded as schemata, representing structures of | ||
66 | expectation constructed from previous experience. | ||
67 | |||
68 | [[image:frame_based_ontologies.png]] | ||
69 | |||
70 | |||
71 | |||
72 | |||
73 | |||
74 | |||
75 | |||
76 |