Page 330 - Software and Systems Requirements Engineering in Practice

292 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

T his appendix contains suggestions for creating and managing
a requirements database (RDB).

A.1 Introduction
A requirements engineering database is different from a traditional
relational database in that it is optimized for the storage and
management of requirements. It consists of a front end component
that is optimized for requirements and a back end server that is
only accessible through the front end. A typical configuration is
shown in Figure A.1. One possible configuration has the RE
management software on the server, using a browser to access it.
Another configuration, which is faster but requires that software be
installed on the client, is to have a client application on the user PC
accessing the database on a server. Most commercial databases
support both approaches.
The unique attributes of an RE database (as contrasted with a
traditional database) include
• Schema predefined to support the storage of requirements of
different kinds
• Version control at the requirement (record) level, with user
views of the history of a requirement

Web Browser Client PC with RE
Front End Software

RE Management
Front End

Database

Back End Server

FIGURE A.1 RE database configuration