English
Français
Español| Name | Summary | Categories | Buy |
|---|---|---|---|
| Artificial Intelligence Machine Learning Deep Learning. How much can it learn? | Description: F1-score Mean Value Method: | IT & Software | |
| COMMON CRITERIA for Information Technology Security Evaluation determination | Description: Evaluation of a software TOE for EAL2 Method: Common Criteria (CC), Common Methodology for Information Technology Security Evaluation (CEM), ISO 18045, ISO 15408-3 | IT & Software | |
| ECG Ventricular beat detection software verification (Black box testing) | Description: Sensitivity (Se) = TP / (TP + FN) Positive Predictivity (P+) = TP / (TP + FP) TP: number of true detection FN: number of undetected beats FP: number of false detections Method: IEC 62304 | IT & Software | |
| Random Number Generator verification | Description: Software implementation RNG (Random number generators) Method: Remote gambling and software technical standards, RTS 7 | IT & Software | |
| Software safety validation of software module for an Adaptative Cruise Control System (ACC) | Description: Numerical Equivalence Testing in order to demonstrate numerical equivalence between the model provided and the generated code which has been programed in a Compute Module. Method: IEC 61508-3, ISO 26262 | IT & Software | |
| Software static test: Code verification to ensure safety requirements | Description: Evaluation of Software static test: Code verification to ensure safety requirements, according to IEC 62443-4-1:2018 (Clause 8.3 SI-1: Security implementation review). Method: IEC 62443-4-1 | IT & Software | |
| Software static test: Code verification to ensure safety requirements. 02 | Description: The Laboratory must verify the code through a static test in order to verify all the design principles that shall applied according to IEC 60880:2006, section 8.2.3 for general purpose-language Method: IEC 61508-3, IEC 60880 | IT & Software | |
| Software static test: Code verification to ensure safety requirements. 03 | Description: The Laboratory must verify the code through a static test in order to verify all the design principles that shall applied according to ISO 26262, section 8.4.4 Table 10. Source code shall be verified in accordance with ISO 26262-8:2011 Clause 9, and by applying the verification methods listed in section 8.4.5, Table 9 Method: IEC 61508-3, ISO 26262 | IT & Software | |
| Software test technique using Risk Based testing. | Description: It is assumed that the risk analysis and categorization is well done. So, based on this input, it is expected validate de Test Design provided Method: ISO 29119 | IT & Software | |
| Testing of Requirements for quality of Ready to Use Software Product (RUSP) / COTS Software | Description: Product description conformity evaluation. User documentation conformity evaluation. Software conformity evaluation. Method: GB/T 25000.51, ISO/IEC 25051 | IT & Software | |
| USB Type-C Chargers. 1A | Description: Initial Voltage Test, and USB Type-C Current Adv Test Method: USB Type C Functional Test Specification, IEC 62680-1-3 | IT & Software | |
| USB Type-C Chargers. 1B | Description: Low level contact resistance, Dielectric strength, Insulation resistance, Resistance between contacts under high current conditions Method: IEC 62680-1-3 | IT & Software | |
close
