...
- Organizational numeric identifier of the document
- Descriptive and identifying name of the document
- Name of testing (sub)project or use case, if not clear from document name
- Document date
- Version number
- Authors Author or authors and their contacts
- Version history (table with version numbers, dates, contributors and descriptions of changes)
Author
References/Supporting Documents
Version history, date(s) and authors are not needed for documents with masters that are kept up to date in already highly versioned environment, such as an CMS system or Wiki. However, the main or corresponding author and document date need to be visible in self-contained standalone snapshots that are as such published on the web or shared by email.
References/Supporting Documents/Literature
The list of documents with their identifiers, names, version numbers and hyperlinks to individual document should be provided.
At least the reference to the project plan should be provided in its subordinate documents. There is no need to reference other documents that represent the common background that is already listed in the project plan. In lower level documents, only the references that are crucial for its understanding need to be provided, and in order to point to the relevant external documentation that is not already referenced in higher level documentsDocument identifiers/names, version numbers and hyperlinks of individual document should be provided.
Organisational/Strategic Level
...