Database Design Description model text

The Database Design Description (DBDD) describes the design of a database, that is, a collection of related data stored in one or more computerized files in a manner that can be accessed by users or computer programs via a database management system (DBMS). It can also describe the software units used to access or manipulate the data.

DATABASE DESIGN DESCRIPTION

FOR THE

ACCESS CONTROLLER

CONTRACT NO.

CDRL SEQUENCE NO.

Prepared for:

Prepared by:

This document contains No. of pages pages

REVIEW AND HISTORY PAGE

CONTENTS

Insert the "Table of Contents" here.

Consult DI-IPSC-81437 and the 'Documentation Standard' when preparing this document.

1. SCOPE

1.1 Identification.

Identify the system and software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

1.2 System overview.

State the purpose of the system and software to which this document applies.

1.3 Document overview.

Summarize the purpose and contents of this document.
This document comprises of six sections:

• Scope;
• Referenced documents;
• Database-wide design decisions
• Detailed design of the database;
• Requirements traceability;
• Notes

Describe any security or privacy considerations associated with its use.

2. REFERENCED DOCUMENTS

2.1 Project documents.

Identify the project management systems documents here.

2.1 Other documents.

2.1 Precedence.

2.1 Source of documents.

3. CSCI-WIDE DESIGN DECISIONS

This section shall be divided into paragraphs as needed to present CSCI-wide design decisions, that is, decisions about the CSCI's behavioural design (how it will behave, from a user's point of view, in meeting its requirements, ignoring internal implementation) and other decisions affecting the selection and design of software units that make up the CSCI.

To be continued

4. CSCI ARCHITECTURAL DESIGN

Describe the CSCI architectural design in this section.

4.1 CSCI components.

4.2 Concept of execution.

4.3 Interface design.

5. CSCI DETAILED DESIGN

6. REQUIREMENTS TRACEABILITY

The following shall be included in this section:

• Traceability from each software unit identified in this SDD to the CSCI requirements allocated to it.

6. NOTES

This section contains information of a general or explanatory nature that may be helpful, but is not mandatory.

6.1 Intended use.

This software design description shall ...

6.2 Definitions used in this document.

Insert here an alphabetic list of definitions and their source if different from the declared sources specified in the 'Documentation standard'.

6.3 Abbreviations used in this document.

Insert here an alphabetic list of the abbreviations and acronyms if not identified in the declared sources specified in the 'Documentation Standard'.

6.4 Changes from previous issue.

Will be "not applicable" for the initial issue.

Revisions shall identify the method used to identify changes from the previous issue.

This page is under construction

Back to Home page MANAGING STANDARDS Home page

Please send any beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk