is prohibited.
nonfunctional requirements as a whole, addressing data quality and completeness
of the operational data sources. We give tools allowing answering the following
questions: (a) can we answer the set of queries required by the user with the data
currently available in the data sources? (b) what is the quality of the answers we
will obtain? (c) does this quality satisfy users??™ requirements? This is a subject often
ignored in other proposals. The outcomes of the process are a set of documents
and a ranking of the operational data sources that can satisfy the users??™ quality and
information requirements, based on two parameters denoted local and global data
source performance. As far as we are aware of, no other proposal has addressed
the problem in this way. Of course, the analysis may also trigger corrective actions
over data that do not reach the required level of quality. Finally, each phase of this
methodology needs a technical solution from the software engineering or data
warehousing communities. For instance, for requirements elicitation we adapt the
GQM (goal question metric) methodology. For data source selection we introduce
a technique based on QFD (quality function deployment).
In this chapter we first review related work and study the differences between DSS
and operational systems with respect to requirements elicitation.
Pages:
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141