glossary: Add term explanations from SWEBOOKv4

Signed-off-by: Simone Weiss <[email protected]>

Author: Simone Weiss

docs/glossary/index.md

@@ -11,16 +11,16 @@ Please note:
 | :---- | :---- |
 | Assumptions of Use (AoU) | |
 | ASIL (Automotive Safety Integrity Level) | |
-| Bug | |
+| Bug | An observable difference between what the software isintended to do and what it does. Other name is defect. Reference SWEBOOK.v4 p.44 |
 | Code centric | |
-| Component | |
+| Component |  An independent unit with well defined interfaces and dependencies that can be composed and deployed independently. Reference SEWBOOKv4 p. 94 |
 | Decomposition | |
 | Development processes | |
 | DAL | |
 | DO-178C | |
 | Element | |
-| Failure | |
-| Fault | |
+| Failure | Ttermination of the ability of a system to perform a required function or its inability to perform within previously specified limits; an externally visible deviation from the system’s specification. Reference SWEBOOKv4 p. 248|
+| Fault | An “imperfection or deficiency in a work product where that work product does not meet its requirements or specifications and needs o be either repaired or replaced. Reference SWEBOOKv4 p. 248 |
 | Functional safety | |
 | Functional safety assessment | |
 | Hazard | |
@@ -34,8 +34,8 @@ Please note:
 | MISRA | |
 | Mixed-criticality | |
 | Proven in use | |
-| Quality Management |  |
-| Reliability | |
+| Quality Management | Performing processes and activities that determine quality policies, objectives and responsibilities so the project will satisfy the needs for which it was undertaken. Reference SWEBOOKv4 p. 210 |
+| Reliability | Degree to which a system or software performs specific functions under specified conditions for a specified period.  Reference SWEBOOKv4 p. 176 |
 | Reproducible | |
 | Requirement | |
 | Risk | |
@@ -60,8 +60,9 @@ Please note:
 | SPDX | |
 | SW-Element | |
 | System | |
-| System Design | |
+| System Design | Is the overall system architecture, hardware architec
+ture, software architecture, modules, interfaces, data management, and communication among modules. Reference SWEBOOKv4 p.316 |
 | Test |  besides generic test definition this shall mention that there are many different types of tests: Unit Tests, Integration tests, Acceptance Tests etc. |
 | V-Model | |
-| Validation | |
-| Verification | |
+| Validation | Ensures the product fulfills its specific intended purpose. It is defined as "the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements." Reference SWEBOOKv4 p.257 |
+| Verification | ensures that the product is built correctly in that the output products of a life cycle phase meet the specifications imposed on them in previous phases. Verification is defined as “the process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase". Reference SWEBOOKv4 p.257 |