| Name | Personas |
| Abbreviation | PER |
| Learning Cost | 80 |
| Playing Cost | 100 |
| Suggested Phases | 1 |
Engineers
| Mechanical Engineer | Industrial Design | System Engineer | Electrical Engineer | Production Engineer | Software Engineer |
| ✗ | ✔ | ✗ | ✗ | ✗ | ✗ |
Technique and Issue Views
| BusinessNeeds | Stakeholder | Stakeholder Needs | System Requirements | System Structure Architecture |
| ✗ | ✔ | ✔ | ✗ | ✗ |
| System Functional Architecture | Detail Hardware Design | Detail Service Design | Detail Software Design | Manufacturing Operations |
| ✗ | ✗ | ✗ | ✗ | ✗ |
Technique Traits
| Identify Stakeholders | Elicit Needs | Remove Ambiguity | Layman's Terms | Technical Terms | Teamworkings |
| 2 | 3 | 3 | 3 | 0 | 2 |
| Traceability | Prioritizing | Exploring Breadth | Inside the Box | Outside the box | V&V |
| 2 | 0 | 0 | 0 | 0 | 0 |
Verification and Validation
| Analysis | Calculus | Inspection | Demonstration | Test |
| ✗ | ✗ | ✗ | ✗ | ✗ |
Towards the end of the 20th century, the technique Personas was introduced by software designers Alice Cooper to understand, analyse and represent specific segments of the user market. Developing personas helps identify goals, desires, and limitations of users in order to create a better targeted service. This is done by analysing the market in order to recognize its different segments and creating a persona that constitutes an hypothetical representation of the user needs and experience. Today this technique is widely used in the field of Human-Computer Interaction. [1]
