Difference between revisions of "Portal:Glossary"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
;Acceptability | ;Acceptability | ||
: exposure to loss (financial or otherwise) from a risk that an organization is willing to tolerate [https://ieeexplore.ieee.org/document/5733835/ ISO/IEC/IEEE 24765:2010(E) - requires IEEE account] | |||
;Acceptance testing | ;Acceptance testing | ||
;Accountability | ;Accountability | ||
;Activity | ;Activity | ||
: set of tasks that describe the technical effort to accomplish a process and help generate expected outcome [https://www.nasa.gov/seh/index.html NASA Systems Engineering Handbook] | |||
;Assessment | ;Assessment | ||
;Assurance | ;Assurance | ||
| Line 25: | Line 26: | ||
;Autonomy | ;Autonomy | ||
;Automation | ;Automation | ||
: allocation of system functions to machines versus humans [https://www.nasa.gov/seh/index.html NASA Systems Engineering Handbook] | |||
;Anomaly | ;Anomaly | ||
: unexpected performance of intended function [https://www.nasa.gov/seh/index.html NASA Systems Engineering Handbook] | |||
| Line 50: | Line 51: | ||
;Failure | ;Failure | ||
: inability of a system, subsystem or component to perform its required function within specified limits [https://www.nasa.gov/seh/index.html NASA Systems Engineering Handbook] | |||
;Failure detection and recovery | ;Failure detection and recovery | ||
;Fault | ;Fault | ||
: physical or logical cause, which explains a failure [https://www.nasa.gov/seh/index.html NASA Systems Engineering Handbook] | |||
;Formal methods for autonomous systems | ;Formal methods for autonomous systems | ||
;Formal modelling | ;Formal modelling | ||
| Line 90: | Line 91: | ||
;Process | ;Process | ||
: "set of interrelated or interacting activities that use inputs to deliver an intended result" [https://bsol.bsigroup.com/Bibliographic/BibliographicInfoData/000000000030412048 ISO 9000:2015] | |||
;Qualitative assessment | ;Qualitative assessment | ||
;Quality requirement | ;Quality requirement | ||
: "requirement related to quality" [https://bsol.bsigroup.com/Bibliographic/BibliographicInfoData/000000000030412048 ISO 9000:2015] | |||
;Quality plan | ;Quality plan | ||
: "specification of the procedures and associated resources to be applied when and by whom to a specific object" [https://bsol.bsigroup.com/Bibliographic/BibliographicInfoData/000000000030412048 ISO 9000:2015] | |||
;Quantitative assessment | ;Quantitative assessment | ||
| Line 113: | Line 114: | ||
;Requirement | ;Requirement | ||
: "need or expectation that is stated, generally implied or obligatory" [https://bsol.bsigroup.com/Bibliographic/BibliographicInfoData/000000000030412048 ISO 9000:2015] | |||
;Requirements development processes | ;Requirements development processes | ||
| Line 142: | Line 143: | ||
: software testing | : software testing | ||
;Specification | ;Specification | ||
: "document stating requirements" [https://bsol.bsigroup.com/Bibliographic/BibliographicInfoData/000000000030412048 ISO 9000:2015] | |||
;Synthetic environment | ;Synthetic environment | ||
: to develop high level test scenarios, drive test case development | : to develop high level test scenarios, drive test case development | ||
| Line 159: | Line 160: | ||
;Validation: | ;Validation: | ||
: defines verification as "Confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled" [https://bsol.bsigroup.com/Bibliographic/BibliographicInfoData/000000000030412048 ISO 9000:2015] | |||
: further adds as "A system is able to accomplish its intended use, goals and objectives (i.e., meet stakeholder requirements) in the intended operational environment. The right system was built.” ISO/IEC/IEEE 15288:2015 | |||
;Verification: | ;Verification: | ||
: defines verification as "Confirmation, through the provision of objective evidence, that specified requirements have been fulfilled" [https://bsol.bsigroup.com/Bibliographic/BibliographicInfoData/000000000030412048 ISO 9000:2015] | |||
: further adds as "Verification is a set of activities that compare a system or system element against the required characteristics. This includes, but is not limited to specified requirements, design description and the system itself. The system was built right." ISO/IEC/IEEE 15288:2015 | |||
Revision as of 12:50, 14 June 2022
Offer different classifications and groupings - in main page
- Verification techniques (tree?)
- Metrics (grouping)
- Application area (e.g. ML systems, for HRI, for medical robots)
Contents of each linked page:
- definitions with links to sources
- short discussion of how topic relates to verification of autonomous systems
Template for definition pages - please copy the markup from this page into your new definition page
- Acceptability
- exposure to loss (financial or otherwise) from a risk that an organization is willing to tolerate ISO/IEC/IEEE 24765:2010(E) - requires IEEE account
- Acceptance testing
- Accountability
- Activity
- set of tasks that describe the technical effort to accomplish a process and help generate expected outcome NASA Systems Engineering Handbook
- Assessment
- Assurance
- Assurance cases
- Autonomous System
- "system which has the ability to perform intended tasks based on current state, knowledge and sensing, without human intervention" BSI 8611:2016
- Autonomous systems design
- Autonomy
- Automation
- allocation of system functions to machines versus humans NASA Systems Engineering Handbook
- Anomaly
- unexpected performance of intended function NASA Systems Engineering Handbook
- Behavior verification for autonomous systems and ML systems
- Behavioral verification
- Combining V&V Techniques
- Contextual reasoning
- Correctness verification
- Credibility
- Cross-domain / multi-domain validation
- Cyber-security
- Dependability
- Executable specifications
- Experiment design
- Explainability
- Failure
- inability of a system, subsystem or component to perform its required function within specified limits NASA Systems Engineering Handbook
- Failure detection and recovery
- Fault
- physical or logical cause, which explains a failure NASA Systems Engineering Handbook
- Formal methods for autonomous systems
- Formal modelling
- Formal software verification
- Functional assurance
- Functional requirements
- Functional verification
- HRI (Human-robot interactions)
- HRI verification
- Hybrid Logical/Dynamical Planning and Verification
- Generalizability
- Integrity of autonomous systems
- Liability
- Licensing and certification
- Model-based evaluation
- Objective evidence
- ISO 9000:2015 - "data, supporting the existence or verity of something" ISO 9000:2015
- Operational design domain
- Process
- "set of interrelated or interacting activities that use inputs to deliver an intended result" ISO 9000:2015
- Qualitative assessment
- Quality requirement
- "requirement related to quality" ISO 9000:2015
- Quality plan
- "specification of the procedures and associated resources to be applied when and by whom to a specific object" ISO 9000:2015
- Quantitative assessment
- Performance evaluation and benchmarking
- Privacy
- Redundant robots
- Reliability
- Replicability
- Reproducibility
- Requirements
- Workspace and conditions/context of operations
- Requirement
- "need or expectation that is stated, generally implied or obligatory" ISO 9000:2015
- Requirements development processes
- Resilience
- Responsibility
- Robot safety
- Robotic Systems
- Robot systems engineering
- Robustness
- Run-time verification and monitoring
- Safety
- Safety and security interaction
- Safety in HRI
- safety, system function
- verification of any function in the system including ML & non-deterministic functions
- Safety-centric HRI protocols
- Safety requirements
- Security
- Security requirements
- Simulation-based testing
- Sim-based evaluation
- Social/legal/ethical requirements
- Software testing and debugging
- Software tools for benchmarking and
- Software tools for testing
- software testing
- Specification
- "document stating requirements" ISO 9000:2015
- Synthetic environment
- to develop high level test scenarios, drive test case development
- Test cases for verification purposes
- Testing
- Transparency
- Trust
- Trustworthiness
- Use-case scenario generation
- Use Case testing
- Validation
- defines verification as "Confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled" ISO 9000:2015
- further adds as "A system is able to accomplish its intended use, goals and objectives (i.e., meet stakeholder requirements) in the intended operational environment. The right system was built.” ISO/IEC/IEEE 15288:2015
- Verification
- defines verification as "Confirmation, through the provision of objective evidence, that specified requirements have been fulfilled" ISO 9000:2015
- further adds as "Verification is a set of activities that compare a system or system element against the required characteristics. This includes, but is not limited to specified requirements, design description and the system itself. The system was built right." ISO/IEC/IEEE 15288:2015