Databases Reference
In-Depth Information
For example, if a group of stakeholders has expressed concerns about using roles
to grant users access to data, they should be able to guess that roles are listed in your
map in the area labeled Security. From within that part of the map, they will see how
role-based access is listed under the authorization area. Although there are multiple
ways to display these topic maps, one of the most popular is a tree-like diagram that
places the highest category of concern (the -ilities) on the left side of a tree, and then
presents increasing levels of detail as you move to the right. We call these structures
quality trees
. An example of a quality tree is shown in figure 12.6.
This example uses a three-level structure to break down the concerns of the proj-
ect. Each of the seven qualities can be further broken down into subfeatures. A typical
single-page quality tree will usually stop at the third level of detail because of the limi-
tations of reading small fonts on a single page. Software tools can allow interactive
sites to drill further down to a requirements database and view use cases for each
requirement.
Solution support
Full-text search
Full-text search on document data (H, H)
XML search
Searchability
Fast range searching (H, H)
How important
to this project?
Score rank via XQuery (M, H)
Custom scoring
Easy to add new XML data (C, H)
Drag-and-drop
XML importability
Batch import tools (M, M)
Bulk import
Easy to transform XML data (H, H)
XQuery
Transformability
Transform to HTML or PDF (VH, H)
XSLT
Works with web standards (VH, H)
Use open source software (H, H)
No license fees
Affordability
No complex languages to learn (H, H)
Standards-based
Staff training (H, M)
Use established standards (VH, H)
Standards
Sustainability
Use declarative languages (VH, H)
Ease of change
Customizable by nonprogrammers (H, H)
Use W3C standards (VH, H)
Web services
Interoperability
Mashups with REST interfaces (VH, H)
No DB translations
Works with W3C Forms (H, M)
Prevents unauthorized access (H, H)
Collection-based access (H, M)
Centralized security policy (H, M)
Fine-grain control
Security
Role-based
Figure 12.6
Sample quality tree—how various qualities (-ilities) are grouped together
and then scored. High-level categories on the left are broken down into lower-level
categories. A short text describing the quality is followed by letter codes to show how
important a feature is (C=Critical, VH=Very High, H=High, M=Medium, L=Low) and how
well the proposed solution meets the requirement.
