Factores Protectores y Factores de Riesgo:

In contrast to focus groups, surveys do not require the attendance of a supervisor/interviewer and due to the simplicity of spreading it, a large amount of answers can be gathered. Therefore, surveys are suitable when many answers are required. However, surveys can only specify certain questions, such as “Yes” and “No” or a Likert Scale [76]. Individually typed information does not aid in evaluation of results, leading to only a limited diversity of insights. The collected data can be used to confirm assumptions or show tendencies that should be further explored.

3.1.3 Idea Generation: Brainstorming

As the ideation phase aims to generate multiple concepts to find a suitable solution for the opposed problem, an idea generation technique must be applied. One of these techniques is brainstorming, introduced by Osborne in 1939 [85]. Brainstorming describes the process of idea generation individually or in a group. This process adheres to a set of rules:

1. The problem needs to be clearly stated.

2. All ideas need to be documented, also when not feasible. This can be done using e.g. a mind- map.

3. One cannot interrupt other participants.

4. The brainstorming phase finalizes with an evaluation, i.e. discussion of every idea, potentially leading to new ideas.

3.1.4 Prototypes

As the ideation phase does not intend to create a finalized prototype, it does require the generation of multiple concepts for a first exploration of possibilities and user-reactions. This can be done utilizing low-

28

fidelity prototypes [82], allowing the iteration of multiple design-approaches relatively quickly in order to find the most suitable solution. Methods for low-fi prototyping are pen and paper or video prototypes.

1. Pen and Paper Prototypes are the fastest and simplest method. One can create prototypes using drawings resembling multiple pages of an interface where one “click” leads to the next. It offers a first impression of functionalities and a possible look and feel. Whereas the pen and paper prototype may be made from sketches or well-designed in a more advanced version, depends on what purpose it serves, i.e. what should be tested. For example, instructions for the SRB may be presented as a pen and paper prototype in a sense of showing where elements could be placed and how the user feels about it.

2. Video prototyping is based on storyboards in order to examine what may be positive and what may be negative. As video-instructions such as animations may be considered for the final prototype, a simplified video-prototype could be created for testing.

After having created the concepts, they serve to gain insights from stakeholders. Therefore, meetings need to be arranged. This includes inviting stakeholders and preparing questionnaires.

3.2 Specification

As the ideation serves as the concept iteration for finding the final solution, the specification explores functionalities and user specification to conclude with further specifications. Overall, this section covers the specification of user experiences, functions and the requirements for a final prototype to be implemented in the realization phase. Each step requires different methods for successful specification. In the end, the requirements are re-evaluated, forming the final version of requirements.

3.2.1 Functional Architecture

The functional architecture visualizes the functionalities of the envisioned product in a flow-chart, showing the relations of each component to each other. Utilizing a level-approach, the functionalities are specified with increased detail after each level until they are too abstract to be further specified.

29

3.2.2 Experience Specification

Human-centred design requires an experience specification of the user-group. While the required information can be retrieved from the earlier conducted stakeholder-analysis, the specification can be done using a PACT-analysis [80] standing for people, activities, contexts and technologies.

1. People can be specified using personas representing the average user of the product.

2. Activities can be specified using storyboards representing the usage process of an average user. 3. Contexts can be specified using scenarios in different physical or social contexts, such as

inside/outside a building.

4. Technologies can be specified by explaining how the envisioned product uses technology to achieve the user’s desired effect.

3.2.3 Requirement Analysis

After having collected information using background- and state of the art research, as well as a stakeholder analysis, the insights are evaluated and transformed into functional and non-functional requirements. These allow to fulfil the needs and expectations of the stakeholders as emphasized in human-centred-design. When the requirements are set, they are categorized based on importance using the MoSCoW-technique, i.e. stating which requirement must, should or could be implemented in the final product [79].

3.3 Realization

The realization finalizes the product by developing the concept into the envisioned product. It is based on previously set specifications and requirements resulting from stakeholder-opinions. It is the result of user- centred design and multiple iterations.

As the final concept of the DIY-instructions is not clear, the method for realization cannot be specified. Independently of the chosen concept, the model of design process by Felker [86] describes the realization process of instructions and will be applied to realize the envisioned product (see figure 3.3). While the pre-design steps of “determine function”, “define audience” as well as “determine contextual constraints” are already covered by the specification phase, the other steps will be applied in the realization phase. Only the post-design step “evaluate” will be covered by the evaluation phase.

30 Figure 3.3 A model of the design process (Felker, 1980) [86].

“Review and Edit” however, will use the evaluation method of asking a professional to review the first version to identify the biggest problems in terms of design [86]. This evaluation does not determine the usability of the envisioned product but allows to quickly improve the overall appearance in order to avoid mistakes for a more detail-oriented user-testing process.

3.4 Evaluation

The evaluation phase concludes the process and is used to verify whether the requirements from the ideation phase and throughout the process are met. Overall, it serves as a verification of success or failure in realizing the product. Therefore, different aspects are taken into consideration and different approaches can be utilized in order to come to a conclusion. On the hand, functional testing has to be conducted verifying the incorporation of (must have) functional requirements and guaranteeing a functional prototype, on the other hand, user testing has to be conducted verifying the inclusion of user needs.

31

3.4.1 Functional Testing

Conducting a functional test, it can be determined whether all functionalities were incorporated. With reference to the functional requirements, this test can determine if at least all the must-requirements were met, and the envisioned product can be used for user testing or needs revision.

3.4.2 User Testing

During a user test a representative of the target group interacts with the designed prototype. The purposes of user testing in this graduation project are to test the usability of the prototype and to find out whether the prototype fulfils the user’s needs [76]. Thus, problems with the prototype can be identified, if present. Before conducting a user test, a user testing protocol is created in advance to ensure that testing is smooth as well as consistent and yields interpretable results.