1.1 System Identification
This section shall identify the scope of the system being described in the particular SDD. This section shall identify the boundaries of the system concisely and only to the extent necessary to explain the physical scope of the system that is covered by this SDD and shall identify the interfacing systems that are not covered by this SDD. This subsection is anticipated to be only about one paragraph or so long.
1.2 Limitations of this SDD
This section shall explain any limitations that may exist on the SDD (i.e., on this latest version). If the scope of the SDD is limited in some way, the reader needs to be made aware of that limitation. For example, the current version may be preliminary and provide basis information for only the safety requirements. Similarly, if certain sections of the SDD have not been fully addressed or developed completely at this time, the reader should be informed of this limitation.
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|DOE STD- Content of System Design Descriptions.pdf||application/pdf||211.5 KB||English||DOWNLOAD!|
Purpose of a System Design Description
An SDD identifies the requirements associated with structures, systems, and components (SSCs), explains why those requirements exist (that is, provides the bases for the requirements), and describes the features of the system design provided to meet those requirements. As part of a configuration management change control process, the SDD helps ensure consistency among the engineering requirements for systems, the actual installed physical configuration, and the associated documentation. The SDD is a central coordinating link among the engineering design documents, the facility authorization basis, and implementing procedures. An SDD does not originate requirements or basis information, but rather collects that information into a convenient usable form. The SDD consolidates information about a particular system into one document. This provides the advantage that a reader does not have to wade through many different documents and pull out the pertinent parts or have to decipher the details in vendor technical manuals and engineering documents.