Imagine being a carpenter trying to build a
house without any blueprints. We need to have some idea about what we are trying
to build before we undertake the task of building reports. Following are the set of
requirements that we need for this project. These are actually fairly sparse in terms of
requirements. In my experience, requirements range from an extremely detailed set
of Use Case documents to mock-ups done in Spreadsheets or some graphic format.
These are the reports that users are looking for:
Detailed report about a bug. Show who it is assigned to, take in bug ID as a
parameter (will be target for all Drill Downs).
Report to show overall status of issues. Drill-Down to a detailed list of issue.
Given developer login, show list of bugs assigned to them.
Performance report for users. Show percentage of issues in finished state
versus open state.
??? ??? ??? ???
Chapter 12
[ 271 ]
Create the Libraries
In the case of these reports, we have a pretty good idea about what kind of things
we want to be reusable. First, we know that all of these reports will contain the same
Data Source??”a MySQL connection to the Bugzilla database. We also want to create
a consistent header and layout for the reports. So we will create a Library containing
the Data Source and the header, and a Template containing both.
Pages:
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220