Terms related to Foundation Extension - Automotive Software Tester 2018

One of four levels that specify the item's or element's necessary requirements of ISO 26262 and safety measures to avoid an unreasonable residual risk.
A process reference model and an associated process assessment model in the automotive industry that conforms with the requirements of ISO/IEC 33002:2015.
Testing to compare two or more variants of a test item or a simulation model of the same test item by executing the same test cases on all variants and comparing the results.
A logical expression that can be evaluated as True or False.
A white-box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).
The coverage of condition outcomes that have been exercised by a test suite.
A system in which the controlling action or input is dependent on the output or changes in output.
A standard that describes the characteristics of a design or a design description of data or program components.
A logical expression that can be evaluated as True or False.
A white-box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).
The coverage of condition outcomes that have been exercised by a test suite.
A white-box test design technique in which test cases are designed to execute condition outcomes.
An abstraction of the real environment of a component or system including other components, processes, and environment conditions, in a real-time simulation.
The process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect. Fault injection is intended to mimic failures that might occur in the field.
A distinguishing characteristic of a component or system.
The absence of unreasonable risk due to hazards caused by malfunctioning behavior of Electric/Electronic(E/E) - Systems.
Dynamic testing performed using real hardware with integrated software in a simulated environment.
The tracing of requirements for a test level through the layers of test documentation (e.g., test plan, test design specification, test case specification and test procedure specification or test script).
The process of assigning a number or category to an entity to describe an attribute of that entity.
A memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing the program and/or other concurrent processes to fail due to lack of memory.
A table containing different test approaches, testing techniques and test types that are required depending on the Automotive Safety Integrity Level (ASIL) and on the context of the test object.
Dynamic testing performed using a simulation model of the system in a simulated environment.
A white-box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).
A system in which controlling action or input is independent of the output or changes in output.
The ease with which the software product can be transferred from one hardware or software environment to another.
A program of activities designed to improve the performance and maturity of the organization's processes, and the result of such a program.
A framework in which processes of the same nature are classified into an overall model.
A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources.
The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.
Part of quality management focused on providing confidence that quality requirements will be fulfilled.
A category of product attributes that bears on quality.
Coordinated activities to direct and control an organization with regard to quality that include establishing a quality policy and quality objectives, quality planning, quality control, quality assurance, and quality improvement.
An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements, e.g., tests that exercise specific functions or probe non-functional attributes such as reliability or usability.
The absence of unreasonable risk due to hazards caused by malfunctioning behavior of Electric/Electronic(E/E) - Systems.
The representation of selected behavioral characteristics of one physical or abstract system by another system.
Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.
A distinguishing characteristic of a component or system.
Dynamic testing performed using real software in a simulated environment or with experimental hardware.
Testing performed on completed, integrated software to provide evidence for compliance with software requirements.
Documentation that provides a detailed description of a component or system for the purpose of developing and testing it.
Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of working or to provide guidelines (e.g., ISO/IEC standards, IEEE standards, and organizational standards).
The capability of the software product to provide an appropriate set of functions for specified tasks and user objectives.
Testing performed on the completed, integrated system of software components, hardware components, and mechanics to provide evidence for compliance with system requirements and that the complete system is ready for delivery.
The process of running a test on the component or system under test, producing actual result(s).
The person responsible for project management of testing activities and resources, and evaluation of a test object. The individual who directs, controls, administers, plans and regulates the evaluation of a test object.
A reason or purpose for designing and executing a test.
The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
A generalized term for dynamic testing in different virtual test environments.