add document lifecylce model

Extend documentation guideline
Add new process requirements

Resolves: #435

Author: masc2023

process/process_areas/documentation_management/guidance/documentation_guideline.rst

@@ -30,3 +30,56 @@ For manual review of the formal elements the
 
 The review of each document is done as defined for this type of work product in the respective
 process description.
+
+
+Document life cycle models
+--------------------------
+
+Each official document shall have the status: “VALID”.
+
+Depending on the document type (report, checklist, plan, etc.) the document can
+either reach this state directly, or some prior states are required.
+
+Thus different document life cycle models exists:
+
+* Model1: "VALID"
+* Model2: "DRAFT" -> "VALID"
+* Model3: "DRAFT" -> "VALID" -> "VALID(INSPECTED)"
+
+**The document types below require life cycle model 1:**
+
+Report
+
+Guidance:
+
+The document has the state “VALID”, if the
+Author has successfully done a self verification for the three aspects of content,
+valid structure and formal aspects.
+
+**The document types below require life cycle model 2:**
+
+Compare :need:`gd_req__process_management_build_blocks`, except their are part of the
+life cycle model 3, thus the need inspection.
+
+Guidance:
+
+The document has the state “DRAFT”, if the
+Document is created, may have no mature structure, content or formal aspects considered.
+Author writes the document, creates content, creates a valid structure and considers
+formal aspects.
+
+The document has the state “VALID”, if the
+Document is reviewed. In this state the reviewer has successfully checked the document
+for content, structure and formal aspects.
+
+Due to updates, findings, other issues or change request, the document status may set
+back from "VALID" to "DRAFT". This triggers a new review cycle.
+
+**The document types below require life cycle model 3:**
+
+Compare :ref:`review_concept`.
+
+Guidance:
+
+In principle same as life cycle model 2, but an additional inspection step is required,
+as described here: :ref:`review_concept`.

process/process_areas/documentation_management/guidance/documentation_process_reqs.rst

@@ -68,6 +68,21 @@ Document Management Process Requirements
 
    Compare also  :need:`gd_temp__documentation`
 
+.. gd_req:: Document attribute: status
+   :id: gd_req__doc_attr_status
+   :status: valid
+   :tags: manual_prio_1, attribute, mandatory
+   :satisfies: wf__platform_cr_mt_platform_mgmt_plan
+   :complies: std_req__iso26262__support_1043
+
+   Each document, shall have a status depending on the document life cycle models below:
+
+      * Model 1: VALID (e.g. for simple reports)
+      * Model 2: DRAFT -> VALID (e.g. for plans)
+      * Model 3: DRAFT-> VALID -> VALID(inspected) (e.g. for stakeholder requirements)
+
+   Compare :need:`gd_guidl__documentation`
+
 .. gd_req:: Document Author
    :id: gd_req__doc_reviewer
    :status: valid