# Quality Properties of Execution Tracing, an Empirical Study
## 5 Conclusions
### ISO/IEC Standard Families
#### a.2.1 Similarities or Overlaps  
1. ISO/IEC 25010 Standard Family, Characteristic Security, Accountability measures, Section 8.7.4. in [38]: \"Accountability measures are used to assess the degree to which the actions of an entity can be traced uniquely to the entity.\" 1. User audit trail completeness (ID: SAC-1-G): 2. Definition: \"How complete is the audit trail concerning the user access to the system or data?\" Measurement Function: \(X=A/B\) 3. Number of access recorded in all logs. 4. Number of access to system or data actually tested. 2. System log retention (ID: SAC-2-S): 3. Definition: \"For what percent of the required system retention period is the system log retained in a stable storage?\" Measurement function: \(X=A/B\) 5. Duration for which the system log is actually retained in stable storage. 6. Retention period specified for keeping the system log in a stable storage. 7. Stable storage: \"A stable storage is a classification of computer data storage technology that guarantees atomicity for any given write operation and allows software to be written that is robust against some hardware and power failures. Most often, stable storage functionality is achieved by mirroring data on separate disks via RAID technology.\"ISO/IEC 25010 Standard Family, Characteristic Maintainability, Analysability Measures, Section 8.8.3. in [38]:  
\"Analysability measures are used to assess the degree of effectiveness and efficiency with which it is possible to assess the impact on a product or system of an intended change to one or more of its parts, or to diagnose a product for deficiencies or cause of failure or to identify parts to be modified.\"  
1. System log completeness (ID: MAn-1-G):  
Definition: To what extent does the system record its operations in logs so that they are to be traceable? Measurement function: \(X=A/B\)  
**A:**: Number of logs that are actually recorded in the system. **B:**: Number of logs for which audit trails are required during operation. 2. Diagnosis function effectiveness (ID: MAn-2-S):  
Definition: What proportion of diagnosis functions meets the requirements of casual analysis? Measurement function: \(X=A/B\)  
**A:**: Number of diagnostic functions used for casual analysis. **B:**: Number of diagnostic functions implemented. 3. Diagnosis function sufficiency (ID: MAn-3-S):  
Definition: What proportion of the required diagnosis functions has been implemented? Measurement function: \(X=A/B\)  
**A:**: Number of diagnostic functions implemented. **B:**: Number of diagnostic functions required. 3. ISO/IEC 9126 Standard Family, Characteristic Maintainability, Analysability Metrics, in [39,40]:  
1. Audit trail capability Purpose: Can the user identify specific operations which caused failure? Can the maintainer easily find specific operations which caused failure? Measurement function: \(X=A/B\)  
**A:**: Number of data actually recorded during operation;
**B:**: Number of data planned to be recorded, which is enough to monitor status of the software in operation Method of application: Observe behaviour of users or maintainers who are trying to resolve failures. 2. Diagnostic function support Purpose: How capable are the diagnostic functions to support causal analysis? Can the user identify the specific operation which caused failure? (The user may be able to avoid encountering the same failure with alternative operations.) Can the maintainer easily find the cause of failure? Measurement function: \(X=A/B\)  
**A:**: Number of failures which maintainers can diagnose using diagnostic functions to understand cause-effect relationship
**B:**: Total number of registered failures Method of application: Observe behaviour of users or maintainers who are trying to resolve failures using diagnostic functions. 3. Failure analysis capability Purpose: Can the user identify specific operations which caused the failures? Can the maintainer easily find the cause of failure?