Key terms used in determining software reliability

1. Failure - an event consisting in the termination of the software to perform the required functions subject to the specified restrictions. The cause of failures is the manifestation of defects that remain undetected.
2. A defect is a software anomaly, an incorrect definition of an operation, process and data in software or software specification that can lead to failure.
3. A fault is a match in which the software is unable to perform the required functions. A fault condition occurs after a fault occurs.
4. Error is the action of a person (designer or programmer), as a result of which a defect is introduced into the software.
5. Measurement - the process of determining the quantitative and qualitative values ​​of the attributes of the subject property.
6. Indicator - the absolute value of the At attribute or the development process. Those. quantifying the extent to which a software product or process has desired properties.
7. Metrics - the qualitative or quantitative characteristics of the software or its development process. In determining the metrics, the scale used and the method of measurement play an important role. Metrics allow you to assess the level of quality and reliability of software products and processes and to identify existing problems. The need to calculate and analyze a variety of metrics arises during verification and certification of a software product.