The output
of the phase includes (1) a list of the queries expected to be posed to the system;
(2) data quality requirements forms; and (3) a quality dimensions hierarchy. Next
we describe the steps of this phase.
??? Interviews.with.users.and.referent.people: Aimed at documenting queries
and the associated quality parameters. Each user provides a list of queries
(expressed as questions in English) the user needs for a daily task. Initially,
the vocabulary is unrestricted. However, certain terms may have different
meanings for different users, or team participants. For example, ???the best customer???
or ???the largest source of buying orders.??? These expressions are disambiguated
and converted to, for example, ???best customer is the one averaging
buying orders for more than $1000 monthly.??? The analyst must identify these
kinds of ambiguous expressions and translate them as explained. The form
QRY_USR is produced. This form contains, for each user and query, (1) user
ID; (2) a query ID (a unique value of the form ???Q??? plus a sequential number);
(3) the query expressed in English; (4) a priority for the query: the requirements
engineer must guide the user in this task, avoiding overestimating the
query hierarchy; (5) a query frequency (the minimum elapsed time between
two instances of the same query); (6) the accepted response time (maximum
time required for getting the query answer); and (7) a global priority for the
query.
Pages:
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167