Collaborative Requirements Engineering: Bridging the Gulfs Between Worlds - Intentional Perspectives on Information Systems Engineering - page 361

Ta b l e 4 Motivations and their implications

Motivation Description Implications

Power Need to control others, authority,

command

Work organisation,
responsibility, control
hierarchy

Possession Desire for material goods, wealth Resource control, monetary

incentives, marketing

Achievement Need to design, construct, organise Goal oriented, to project aims

Self-esteem Need to feel satisfied with oneself Link personal and project

goals, praise personal
achievement

Peer-esteem Need to feel valued by others Team composition, social

feedback and rewards, praise

Self-efficacy Confidence in own capabilities Confidence building, training,

skill matching

Curiosity, learning Desire to discover, understand

world

Extensible systems, self
tutoring

Sociability Desire to be part of a group Collaboration in work

organisation

Altruism Desire to help others Cooperation in work

organisation

Values direct attention to user beliefs that may either suggest non-functional
requirements or perspectives within which to interpret users' motivations and
goals. Finally, emotions give useful feedback on users' views which may not
be expressed in conversation, so they afford another means of developing com-
mon ground by observation of facial expressions, body language and voice tone
to detect frustration, anger, pleasure, etc. Agenda-setting heuristics and manage-
ment of attention to issues within requirements conversations are summarised in
Fig. 5.
The heuristics advise on use of the checklists of values and motivations in
Tables 3 and 4 as agendas within interviews and other RE activities organised in
an iterative cycle of developing mutual understanding.

• Elicit users' and organisation's motivations and values in initial requirements

sessions when high-level goals are discussed.

• Analyse motivations in more detail if requirements for personalisation are

indicated or to reflect individual needs.

• Goals should be interpreted in the light of user values and motivations; which

provide useful consistency checks.

• Motivations and values which have not been cross-referenced to goals during

analysis may suggest missing requirements.

• Emotions provide useful feedback on the acceptability of requirements and pro-

totype designs, especially where users are not confident in providing verbal
feedback.