Quality dimensions
Data Quality-Based Requirements Elicitation for Decision Support Systems 6
Copyright ?© 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission
of Idea Group Inc. is prohibited.
lection, and document generation, and from any phase it is possible to go back to
any former one. The whole process can be summarized as follows: on the one hand,
the data consumer??™s functional requirements are analyzed, unified, and documented.
On the other hand, the quality of data in the data sources is collected from the data
producer users. This information is then analyzed as a whole, and a collection of
documents is produced. These documents will allow matching the requirements
with the available data. In the remainder of this section we introduce the general
framework of the methodology, and the conceptual basis over which it is built. Each
phase of the methodology will be described in detail later in this chapter.
Framework
We first define the participants, concepts, techniques, and tools that will be used in
the requirement analysis process.
??? Team: The methodology defines the following roles and participants in the team
that will carry out the project: (a) project leader: manages the working team and
interacts with the customer; (b) training leader: carries out the training of the users
on the concepts, methodologies, or technologies associated with the project; (c)
requirements engineer: performs requirements elicitation, working jointly with
the users (must be an experienced professional); (d) query and data manager:
analyzes the queries; and (e) information administrator:.
Pages:
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153