Page 338 - Software and Systems Requirements Engineering in Practice

300 S o f t w a r e & S y s t e m s R e q u i r e m e n t s E n g i n e e r i n g : I n P r a c t i c e

4
Release 2 3
1
Product Line
RQT P1 P2 P3 P4
R1
R2
R3
R4

FIGURE A.4 Three-dimensional nature of product line requirements and databases

Camera Feature P1 P2 P3 P4

Lithium Ion Battery X X X X
In-camera Red-eye Remover X X X
Video Capability X
Anti-Shake X X
Continuous Shooting Mode X

18X Zoom Lens X
3-inch Display Screen X X

FIGURE A.5 Example product map

A.5 Summary

In this appendix, we have shown that advanced planning is extremely
important in order to get the most out of a modern RDB. Although
defining a process, its metrics, and the structure and content of
generated material may not seem all that important when a project is
initiated, careful planning is the key to effective database management
as the project size increases. Furthermore, when selecting a database,
needed features should be prioritized. All the current commercial
RDBs can do a reasonable job if used effectively, but not all RDBs will
have all needed features. Sometimes, a missing feature (such as
attribute propagation) can be implemented using the extensibility
features of the database. If a desired RDB feature is not available, then
the purchaser must decide for each case just how important it is.