Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Serializability wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Oracle Database wikipedia , lookup
Functional Database Model wikipedia , lookup
Ingres (database) wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Concurrency control wikipedia , lookup
Relational model wikipedia , lookup
Database model wikipedia , lookup
<Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) Version: TBD Version Date: 04/28/17 < Application Name > Database Design Document (DDD) Version TBD (<Working Draft / Review Draft / Approved>) Produced for: <Company Name> <City, State> <Visibility> <Company>, 2000 Page 1 <Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) Version: TBD Version Date: 04/28/17 Revision History Date Version Description Author 8/13/99 0.1 Initial draft Katherine Vandiver 9/1/00 0.2 Updates- adapted from Database Design Description from DoD DI-IPSC-81437A Eric Adams 0.3 0.4 0.5 0.6 0.7 <Visibility> <Company>, 2000 Page 2 <Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) Version: TBD Version Date: 04/28/17 Table of Contents 1 INTRODUCTION ................................................................................................................................5 1.1 DOCUMENT OBJECTIVES ......................................................................................................................... 5 1.2 INTENDED AUDIENCES ............................................................................................................................ 5 1.3 REFERENCES ........................................................................................................................................... 5 1.4 DATABASE OVERVIEW ............................................................................................................................ 5 1.5 DOCUMENT OVERVIEW ........................................................................................................................... 6 2 DATABASE-WIDE DESIGN DECISIONS .......................................................................................6 2.1 INTERFACES ............................................................................................................................................ 6 2.2 BEHAVIOR ............................................................................................................................................... 7 2.3 APPEARANCE / NAMING .......................................................................................................................... 7 2.4 DBMS PLATFORM .................................................................................................................................. 7 2.5 QUALITIES............................................................................................................................................... 7 2.6 DISTRIBUTION ......................................................................................................................................... 7 2.7 OPERATIONS ........................................................................................................................................... 7 2.8 MAINTENANCE ........................................................................................................................................ 7 3 DETAILED DATABASE DESIGN ....................................................................................................7 3.1 <DESIGN LEVEL> ..................................................................................................................................... 8 3.1.1 <Name> Database ..........................................................................................................................8 3.1.1.1 3.1.1.1.1 4 <Type> Logical Grouping....................................................................................................................... 8 <Type> Field ...................................................................................................................................... 8 DETAILED DATABASE SOFTWARE DESIGN ............................................................................9 4.1 <NAME> SOFTWARE COMPONENT .......................................................................................................... 9 5 REQUIREMENTS TRACEABILITY ...............................................................................................9 6 NOTES ..................................................................................................................................................9 7 APPENDICES ......................................................................................................................................9 <Visibility> <Company>, 2000 Page 3 <Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) Version: TBD Version Date: 04/28/17 Table of Figures Error! No table of figures entries found. <Visibility> <Company>, 2000 Page 4 <Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) Version: TBD Version Date: 04/28/17 1 Introduction The section introduces the Database Design Document (DDD) for <Application> to its readers. 1.1 Document Objectives This DDD for the <Application> software has the following objectives: Describe 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. To serve as the basis for implementing the database and related software units. It provides the acquirer visibility into the design and provides information needed for software support. All sections should remain in this document. If a section is to be tailored out, the section shall remain and contain the words “Tailored out”. 1.2 Intended Audiences This DDD is intended for the following audiences: Technical reviewers, who must evaluate the quality of this document. <Application> developers including: Architects, whose overall architecture must meet the requirements specified in this document. Designers, whose design must meet the requirements specified in this document. Programmers, whose software must implement the requirements specified in this document. Testers, whose test cases must validate the requirements specified in this document. 1.3 References This DDD refers to the following references: <Application> Project Glossary <Application> Software Requirements Specification 1.4 Database Overview This database fills the following purposes: <General nature of the database> <Business context of database> <History of development> <Intended use> <Maintenance objectives> <Visibility> <Company>, 2000 Page 5 <Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) 1.5 Version: TBD Version Date: 04/28/17 <Deployment locations> Document Overview This DDD is organized into the following sections: Introduction, which introduces the database design for <Application> to its readers including referenced documents and an overview of the database including definition, business goals and context. Database Overview, which provides a high level description of the database including its definition, business goals, and context. Database-wide design decisions, which provides decisions about the databases behavioral design (how it will behave, from a user’s point of view, in meeting its requirements, ignoring internal implementation) and other decisions affecting further design of the database. Detailed database design, which will contain a section for each design level (conceptual, internal, logical, physical). Detailed database software design, scripts, data access components and management software. Requirements traceability, which provides traceability from the system or software requirements specification to the database software that implements it. Notes, which contains any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document. Appendices, which may be used to provide information published separately for convenience in document maintenance. 2 Database-wide Design Decisions This section documents decisions about the databases behavioral design (how it will behave, from a user’s point of view, in meeting its requirements, ignoring internal implementation) and other decisions affecting further design of the database. 2.1 Interfaces Design decisions regarding queries or other inputs the database will accept and outputs (displays, reports, messages, responses, etc.) it will produce, including interfaces with other systems and users. <Visibility> <Company>, 2000 Page 6 <Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) 2.2 Version: TBD Version Date: 04/28/17 Behavior Design decisions on database behavior in response to each input or query including actions, response times and other performance characteristics, selected equations / algorithms / rules, disposition, and handling of unallowed inputs. 2.3 Appearance / Naming Design decisions on how databases / files will appear to the user 2.4 DBMS Platform Design decisions on the database management system to be used (including name and version / release) and the type of flexibility to be built into the database for adapting to changing requirements. 2.5 Qualities Design decisions on the levels and types of availability, security, privacy and continuity of operations to be offered by the database 2.6 Distribution Design decisions on the database distribution (e.g., Client/server), master database file updates and maintenance, including and maintaining consistency, establishing / reestablishing maintaining synchronization, enforcing integrity and business rules. 2.7 Operations Design decisions on backup and restoration including data and process distribution strategies, permissible actions during backup and restoration, and special considerations for new or non-standard technologies such as video and sound. 2.8 Maintenance Design decisions on repacking, sorting, indexing, synchronization, and consistency including automated disk management and space reclamation considerations, optimizing strategies and considerations, storage and size considerations, and population of the database and capture of legacy data. 3 Detailed Database Design This section describes the actual design of different databases at varying levels of abstraction. A subsection for each of conceptual, internal, logical and physical levels. <Visibility> <Company>, 2000 Page 7 <Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) 3.1 Version: TBD Version Date: 04/28/17 <design level> 3.1.1 <Name> Database This subsection specifies all design constraints associated with the <name> database. The <name> database shall be a <type of> database. The <name> logical database schema consists of the following logical groupings: <Type> Logical grouping <E-R or equivalent diagram> 3.1.1.1 <Type> Logical Grouping The following table specifies the information stored in the <type> database concerning <type of info in database>, regardless of type. Abbreviations: Priority: Timing (limitations on CRUD operations): Frequency of access: Volume estimate: Inherent ordering: Relationships to other Logical Groupings: 3.1.1.1.1 <Type> Field Field name: Type: Size and Format: Unit of measurement: Range of possible values: Accuracy (how correct) and Precision (number of significant digits): Updateable: Sources / recipients of data: Security / privacy constraints: Synonyms: Order within logical grouping: <Visibility> <Company>, 2000 Page 8 <Company> - <Application> Document ID: DDD <Application Name> Database Design Document (DDD) Version: TBD Version Date: 04/28/17 4 Detailed Database Software Design This section contains subsections for each software module used within the database. This includes but is not limited to: database management scripts, DDL, DML, triggers and stored procedures. See the Software Design Document for the structure of this section. This section may refer directly to the SDD. 4.1 <Name> Software Component 5 Requirements Traceability This section shall map each software component defined above in section 4 to a set of requirements stated in the SRS. 6 Notes This section shall any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document. 7 Appendices This section may be used to provide information published separately for convenience in document maintenance. <Visibility> <Company>, 2000 Page 9