Analysis of Early Aspects in Requirements Goal Models: A Concept-Driven Approach - Transactions on Aspect-Oriented Software Development - page 52

Fig. 8. Repertory grid for media shop
Construct names are merely convenient labels to remind the person of the thoughts
and feelings that the construct provoked, and hence are not transferable to another
person without discussion and negotiation [42].
On the other hand, the concrete entities are exchanged, because to make
comparisons across individuals and investigate construct similarity requires that
they each construe the same set of elements [22]. We assume that people focusing
on similar topics would agree on the definition of a common set of concrete tasks
within the area of interest, i.e., when presented with specific and relevant tasks
that are devised by others, people are likely to grasp the essential meaning behind
the notions.
In the media shop example, the tasks from different viewpoints are consoli-
dated and shared. Then, each stakeholder rates all twenty tasks (elements) on
his or her own softgoals (constructs) using the 5-point scale defined in Fig. 6.
Figure 8 presents an integrated view of individual repertory grid filled up by the
customer and the developer.