A typical dynamic requirements file resembles the following structure.
The Document element is positioned inside the InstanceDocumentRef element which is nested with the overall instance structure of the requirements file. The Document element contains document content and allows a number of attributes and child elements to support authoring. 
The following attributes are available on the element. To view available attributes, select the element and right-click. In the shortcut menu, select Add Attributes.
- BlankAreaMarking: Overrides the insertion of the “This area intentionally left blank.” language. The StyleGuide standard and default setting includes this language in any vertical blank space that exceeds 1.5” in the body of the document (it will not appear at the end of the document if there is more than 1.5” of blank space). Set this value to No if the document you are creating should not print this language. An example of when this language should not be used is on a model form where additional text is not usually allowed.
- Columns: Overrides the StyleGuide standard and default of two (2) columns for the document layout. By setting the value for this attribute to one (1) the document content will span the entire width of the page.
- DataFieldUnderline: Adds document level underlining functionality in the Requirements Editor. The attribute is used to apply underlines to all data fields within an entire document and is exclusively used with the Rendition plug-in.
- DocumentClass: Currently has no impact on the document.
- DocumentSpecificStyle: Currently used to indicate which stylesheet should be used for Non-Runtime publishing.
- InitialPageNumber:
- Language:
- Recordable - Determines if the document is recordable.
- Role - The value SmallBody denotes one-column format for Document content.
The Document element typically contains the following children.
- Tagline
- Note (the Note element must be added, it is not a default element of the Document node)
- Metadata
- Prolog
- Body (comprising sections)
