Restructure into separate organization and product quality management…

… systems. The idea is the organization QMS will live in its own git repository and the product QMS will live in the same git repository as the codebase.
innolitics · yujanshrestha · Dec 31, 2020 · Dec 31, 2020 · Dec 31, 2020 · Jan 13, 2021
commit f6856867e4a3fd32e82d3ecb9824745cb951cf21
diff --git a/...les/documents/quality_manual/SOPs/capa.md → ...s/documents/organization_qms/SOPs/capa.md b/...les/documents/quality_manual/SOPs/capa.md → ...s/documents/organization_qms/SOPs/capa.md
diff --git a/...cuments/quality_manual/SOPs/change_sop.md → ...ments/organization_qms/SOPs/change_sop.md b/...cuments/quality_manual/SOPs/change_sop.md → ...ments/organization_qms/SOPs/change_sop.md
diff --git a/...uments/quality_manual/SOPs/new_product.md → ...ents/organization_qms/SOPs/new_product.md b/...uments/quality_manual/SOPs/new_product.md → ...ents/organization_qms/SOPs/new_product.md
diff --git a/.../documents/quality_manual/SOPs/new_sop.md → ...ocuments/organization_qms/SOPs/new_sop.md b/.../documents/quality_manual/SOPs/new_sop.md → ...ocuments/organization_qms/SOPs/new_sop.md
diff --git a/...cuments/quality_manual/SOPs/new_vendor.md → ...ments/organization_qms/SOPs/new_vendor.md b/...cuments/quality_manual/SOPs/new_vendor.md → ...ments/organization_qms/SOPs/new_vendor.md
diff --git a/...cuments/quality_manual/SOPs/remove_sop.md → ...ments/organization_qms/SOPs/remove_sop.md b/...cuments/quality_manual/SOPs/remove_sop.md → ...ments/organization_qms/SOPs/remove_sop.md
diff --git a/...cuments/quality_manual/SOPs/review_sop.md → ...ments/organization_qms/SOPs/review_sop.md b/...cuments/quality_manual/SOPs/review_sop.md → ...ments/organization_qms/SOPs/review_sop.md
diff --git a/...ts/quality_manual/quality_manual_IMDRF.md → .../organization_qms/quality_manual_IMDRF.md b/...ts/quality_manual/quality_manual_IMDRF.md → .../organization_qms/quality_manual_IMDRF.md
diff --git a/...s/quality_manual/templates/capa_record.md → ...organization_qms/templates/capa_record.md b/...s/quality_manual/templates/capa_record.md → ...organization_qms/templates/capa_record.md
diff --git a/...y_manual/templates/new_record_template.md → ...tion_qms/templates/new_record_template.md b/...y_manual/templates/new_record_template.md → ...tion_qms/templates/new_record_template.md
diff --git a/...ments/quality_manual/templates/new_sop.md → ...nts/organization_qms/templates/new_sop.md b/...ments/quality_manual/templates/new_sop.md → ...nts/organization_qms/templates/new_sop.md
diff --git a/...ts/quality_manual/templates/new_vendor.md → .../organization_qms/templates/new_vendor.md b/...ts/quality_manual/templates/new_vendor.md → .../organization_qms/templates/new_vendor.md
diff --git a/...ts/quality_manual/templates/remove_sop.md → .../organization_qms/templates/remove_sop.md b/...ts/quality_manual/templates/remove_sop.md → .../organization_qms/templates/remove_sop.md
diff --git a/...ts/quality_manual/templates/review_sop.md → .../organization_qms/templates/review_sop.md b/...ts/quality_manual/templates/review_sop.md → .../organization_qms/templates/review_sop.md
diff --git a/rdm/init_files/documents/510k.md → ..._files/documents/samd_product_qms/510k.md b/rdm/init_files/documents/510k.md → ..._files/documents/samd_product_qms/510k.md
diff --git a/...es/documents/architecture_design_chart.md → ..._product_qms/architecture_design_chart.md b/...es/documents/architecture_design_chart.md → ..._product_qms/architecture_design_chart.md
diff --git a/rdm/init_files/documents/cyber_security.md → ...uments/samd_product_qms/cyber_security.md b/rdm/init_files/documents/cyber_security.md → ...uments/samd_product_qms/cyber_security.md
diff --git a/rdm/init_files/documents/known_anomalies.md → ...ments/samd_product_qms/known_anomalies.md b/rdm/init_files/documents/known_anomalies.md → ...ments/samd_product_qms/known_anomalies.md
diff --git a/rdm/init_files/documents/level_of_concern.md → ...ents/samd_product_qms/level_of_concern.md b/rdm/init_files/documents/level_of_concern.md → ...ents/samd_product_qms/level_of_concern.md
diff --git a/rdm/init_files/documents/release_history.md → ...ments/samd_product_qms/release_history.md b/rdm/init_files/documents/release_history.md → ...ments/samd_product_qms/release_history.md
diff --git a/rdm/init_files/documents/release_record.md → ...uments/samd_product_qms/release_record.md b/rdm/init_files/documents/release_record.md → ...uments/samd_product_qms/release_record.md
diff --git a/...ocuments/software_design_specification.md → ...duct_qms/software_design_specification.md b/...ocuments/software_design_specification.md → ...duct_qms/software_design_specification.md
@@ -103,20 +103,20 @@ Use something like: `![Screen One](../images/uimockups/example-ui-mockup-001.png
 
 Which produces:
 
-![Screen One](../images/uimockups/example-ui-mockup-001.png)
+![Screen One](../../images/uimockups/example-ui-mockup-001.png)
 
 ## Screen Two (SVG)
 
 Use something like: `![Screen Two](../images/uimockups/example-ui-mockup-002.svg)`
 
 Which produces:
 
-![Screen Two](../images/uimockups/example-ui-mockup-002.svg)
+![Screen Two](../../images/uimockups/example-ui-mockup-002.svg)
 
 ## Screen Three (JPG)
 
 Use something like: `![Screen Three](../images/uimockups/example-ui-mockup-003.jpg)`
 
 Which produces:
 
-![Screen Three](../images/uimockups/example-ui-mockup-003.jpg)
+![Screen Three](../../images/uimockups/example-ui-mockup-003.jpg)
diff --git a/rdm/init_files/documents/software_plan.md → ...cuments/samd_product_qms/software_plan.md b/rdm/init_files/documents/software_plan.md → ...cuments/samd_product_qms/software_plan.md
@@ -114,10 +114,12 @@ This section of the software plan describes the various activities involved with
 
 ## Activity Diagram
 
-![Overview of life-cycle processes](../images/lifecycle-processes.svg)
+![Overview of life-cycle processes](../../images/lifecycle-processes.svg)
 
 ## Planning
 
+The purpose of the design activity is to define the architecture, components, and interfaces of the software system based on requirements. [[IMDRF.N23:8.2]]
+
 **Input:**  System requirements and risk controls
 
 Setup a Git repository on GitHub.  All software activity outputs will be stored in this Git repository, the associated GitHub issues, or the associated GitHub pull requests, unless explicitly noted otherwise [[62304:5.1.1.b]].  The software developers working on the project are responsible for keeping all software activity outputs within version control at the times specified in the activity descriptions [[62304:5.1.9.c, 62304:5.1.9.d, and 62304:5.1.9.e]].
@@ -523,7 +525,7 @@ Writing software requirements is an art and a science; one must find balance bet
 {% if not system.is_software_only_device %}
 The distinction between system requirements and software requirements can be challenging.  System requirements describe the requirements of the entire system, including software and hardware.  Software requirements must be traceable to all of the system requirements that they help fulfill.  Software requirements are usually more detailed than the system requirements they refer to.  Many system requirements will be fulfilled using both hardware and software.
 {% endif %}
-The distinction between software requirements and the specifications is {% if not system.is_software_only_device %}also {% endif %}typically challenging.  Requirements should:
+The distinction between software requirements and the specifications is {% if not system.is_software_only_device %}also {% endif %}typically challenging.  Requirements should [[IMDRF.N23:8.1]]:
 
 - not imply solution
 - be verifiable

diff --git a/...ts/software_requirements_specification.md → ...ms/software_requirements_specification.md b/...ts/software_requirements_specification.md → ...ms/software_requirements_specification.md
diff --git a/rdm/init_files/documents/test_record.md → ...documents/samd_product_qms/test_record.md b/rdm/init_files/documents/test_record.md → ...documents/samd_product_qms/test_record.md