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

Ta b l e 3 Values: elicitation hints and implications for RE process management

Value concept Related terms Potential sources Process implications

Trust Openness, integrity,

loyalty,
responsibility,
reliability

Relationships with
other individuals/
departments,
privacy policies

Less control,
milestone checks,
improved team
confidence

Collaboration Cooperation,

friendship,
sympathy,
altruism

Relationships with
others, awareness
of others (office
politics)

Improved team
cooperation,
shared awareness

Morals/ethics Justice, fairness,

equality, tolerance

Behaviour towards
others, opinions of
others' behaviours

Openness and
honesty in team

Creativity,
innovation

Originality,
adventure, novelty

Work processes,
problem solving

Creativity,
workshops,
facilitators

Aesthetics Beauty, nature, art Self appearance,

reaction to
images, shapes,
art and design

Team members,
designers,
storyboards

Security Safety, privacy, risk Data management

policies, attitudes
towards change

Hazard/threat
analysis

Personal
characteristics

Serious/playful,
introvert/
extrovert,
systematic/
opportunistic

Self image, personae
scenarios,
psychological
questionnaires

Customisation
analysis for
personal RE, team
conflict
management

Motivation Ambition,

achievement

Ambitions, goals,
career plans

Stakeholder
analysis, rewards,
incentives for
members

Beliefs and
attitudes

Cultural, political,
religious topics

Leisure interests,
user background,
reaction to news
events

Stakeholder analysis,
team composition,
incentives

arrive at a common set of values; alternatively, system configuration/customisation
may need to be considered (e.g. different levels of security controls mapped to
stakeholders who regard security as very or not important). Values and motivations
are used to direct attention during interviews and requirements meetings, and sup-
plement the agenda that would be suggested by goal-oriented RE. They also provide
contextual information for interpreting users' goals and assumptions. For example,
focusing on motivations before users' goals provides more contextual information
on longer-term drivers for users' interests which can then be used to explore more
specific goals. Motivations also focus attention on developing a common ground of
understanding with individual users which will be important for personalisation (see
Table 4) .