STAKEHOLDER ANALYSIS

This analysis is conducted to find out which stakeholders are most relevant to take into account when developing the instrument. The definition of stakeholders during this project is “any group or individual who can affect or is affected by the achievement of the organisation’s objectives” [19]. For the stakeholders, the influence and interest will be identified to point out which stakeholder is most important. The stakeholder analysis is divided into three phases, mapping the stakeholders, interest-influence matrix and a conclusion who is most important.

The first phase, mapping the stakeholders for requirement engineering. This is conducted according to Sharp [20], by distinguishing four different categories of stakeholders. These can be identified as users, developers, legislators and decision makers. Each category will be briefly explained:

Users interact, control or use the information from the instrument or even purchase it.

Developers are responsible for developing and creating the instrument. Legislators (institutions) provide rules and guidelines about the instrument which might affect the operation and the developing of the system.

Decision-makers (managers or controllers) making structures which relate to the developing of the instrument.

During the second phase, for each category the stakeholders will be rated on terms of interest and influence. This rating will be done by low (1), medium (2) or high (3)

interest. The level of interest is to identify the involvement of the stakeholder within the development. And the level of influence indicates how much influence the stakeholder has on the developing of the instrument. This rating helps with producing a stakeholder analysis matrix, where an overview is given of all the involved stakeholders and their interest and influence.

The last phase, to put it more simply the important stakeholders will be pointed out. This will be done by the use of the ratings, to show the relevancy of each

stakeholders. These stakeholders will be used for interviews, questionnaires or brainstorms. This is important for the requirements which should be made.

3.3

BRAINSTORM SESSIONS

For generating new viewpoints on the research questions, brainstorm sessions are conducted. These brainstorm sessions need to provide sustainable answers on where to implement the instrument, how to students and what kind of reflection method is required. First individual brainstorm sessions are held to generate multiple ideas, for mapping what the instrument could do. As evident of this outcome new individual and joint brainstorm sessions were conducted. These brainstorm sessions were same for all three brainstorms the individual, with fellow students and with an expert.

Mind mapping [21] is a brainstorm technique, which is useful to organise the thoughts more productively. They show shape of the thoughts, relevant of each point and how the facts are related towards each other. This will to help organise each brainstorm session, also this is one of the few brainstorm sessions which can be conducted when working individual. Another point is that it is easy to communicate with other parties.

3.4

QUESTIONNAIRES

To easily collect lots of data from a large group of stake holders in the ideation phase, questionnaires were being held. The large group during this project are the students. According to Moore [22] gathering information for requirement engineering, is done by interviews and participatory design as traditionally forms. This however requires face- to-face communication with the stakeholders. Due to the amount of information and time, these forms of gathering information this is not possible. Therefore questionnaires are used to create a rough image what the attitude and viewpoints are from Creative Technology students towards reflection. The outcomes are used to conduct a part of the preliminary requirements.

3.5

INTERVIEWS

Interviews are also being held in the ideation phase with reflection experts and a project supervisor. For requirement engineering [22] doing interviews with stakeholders is an effective way of gathering information. Therefore these interviews are conducted, to get more insights were reflection can bring a contribution and what indented learning outcomes. Also to validate if the project is on the right track. According to DiCicco-Bloom [23] three different interview techniques can be applied:

Structured interviews, is where the interviewer prepared a set of questions, the questions are asked in a specific order. Thus, is multiple interviews were being held every stakeholder would be asked the same question.

Semi-structured interviews, in this case the interviewer prepared a set of questions but these are guidelines for the dialogue. The questions are open and need to help with the construction of new questions during the dialogue.

Unstructured interviews, in this last form the interviewer did not prepared any questions. These questions are based on observations of the interviewee made by the interviewer. This should help to guide the dialogue.

For both, the state of the art (see Chapter 2) and the ideations phase semi-structured interviews are used. This form has been chosen over the two other forms because the researcher wants to search new insights. While beginning with a structured form, during the dialogue new insights could arise. Where the researcher could switch from the

structured form to an unstructured one, this can lead to new discussion. However this takes a lot of time, this approach will give lots of insights, as has been pointed out before. The outcomes will be used, similar to the questionnaires, for the preliminary

3.6

IPACT

To explain the concept through the eyes of the user and put in a normal day scenario, the iPACT method will be used. The goal of iPACT [24] is to clarify the envisioned goal of the instrument towards the user. The iPACT method stands for Intention, People,

Activities, Context, and Technologies. As first in the intention is stated what the goal of the system is towards the user. Next are the people, who are the users, described with the use of personas, who will interact with the system. Next are the activities, which describes the activities of the personas related to the instrument. The context section will describe in which context the instrument will be used. As last, the technology which show what the instrument needs to do. All the above announced components are used to describe a user scenario, from the user’s perspective towards the concept.

3.7

FICS

To explain the concept through the eyes of the designer, the FICS method will be used. The FICS method stands for Functions, Interaction, Content and Services. The functions (and events) will be described, these are the reactions and actions of the system. The next part, the interaction (and usability), will be used how the user interacts with the system. Furthermore, the content (and structure) will show, in chronological way, the information transmission of the system. Lastly, during the services the used services for the concept will be described. All the above announced components are used to describe a user scenario, from the system’s perspective.