Compatibility
It mainly includes coexistence, interoperability, and compatibility compliance. Verify the extent to which a product, system, or component is able to exchange information with other products, systems, or components and perform its required functions while sharing the same hardware or software environment.
The original text of the standard is as follows:
1 Coexistence.
Coexistence refers to the extent to which a product is able to perform its desired function effectively and without negatively impacting other products, while sharing a common environment and resources with other products.
Analysis] Software needs to interact with other software in the process of operation and installation, and coexistence mainly examines the coexistence constraints between the software product installation and operation and the running software. When two software are running at the same time, whether the system resources such as CPU and process of the system are abnormal, or cause other software to run incorrectly or cannot implement the function correctly, or the system error or the software user interface display is unfriendly.
2 Interoperability.
Interoperability refers to the degree to which two or more systems, products, or components are able to exchange information and use the information that has been exchanged.
Analysis] Interchangeability of data formats: Software interoperability is the ability of software to share and exchange information between them so that they can work together to accomplish a function, such as whether the software supports it. Import and export of xls and doc files, etc.
Switching interface for data transmission: Whether the function of the switching interface can be correctly implemented for the specified data transmission when communicating with other software. It should be noted that the protocols between different models of printers and Word may be inconsistent, resulting in errors during messaging (see Figure 2-5).
3 Compliance with compatibility.
Compliance with compatibility refers to the extent to which a product or system adheres to standards, conventions, or regulations related to compatibility, as well as similar provisions.
Analysis] Whether the relevant standards, conventions or regulations and similar requirements for product compatibility are mentioned in the product manual, and if they are mentioned and supporting materials are provided, they are recognizedOtherwise, verify that the software matches the requirements of the mentioned documentation (requirements document).
Reliability
Reliability mainly includes maturity, availability, fault tolerance, ease of recovery, and compliance with reliability, which is used to verify the degree to which a system, product, or component performs a specified function under specified conditions and within a specified time.
The original text of the reliability criteria is as follows:
1 Maturity.
Maturity refers to the extent to which a system, product, or component performs a specified function under specified conditions and for a specified period of time.
Note: The concept of maturity can be applied to other quality characteristics to indicate the extent to which they meet requirements during normal operation.
Analysis] Maturity generally refers to the ability of a software product to provide users with corresponding services when it is used in a software and hardware environment that meets its requirements or other special conditions (such as a certain load pressure). The number of software failures, the average time between failures, the proportion of failures, and the integrity level of the system can be used as evaluation indicators, and the corresponding test cases can be written for each function in the user documentation set and the function list in the product description within a certain test time according to the operating environment of the product or system described in the requirements specification and product description, and all test cases can be executed, and the test results can be collected and analyzed. Based on the test results, determine the number of faults detected, the severity of the defects found, and judge the integrity level of the system.
2 Availability.
Availability refers to the extent to which a system, product, or component can be operated and accessed when it is needed.
Note: Availability can be measured externally by the percentage of a system, product, or component that is available in a state out of the total time.
Analysis] Availability is an evaluation of the degree of usability of the product, such as the proportion of the actual available time in the predetermined system operation time, and the mean time between failures. Write test cases according to the system operation time specified by the product or system described in the requirements specification or product description, and record the system operation time actually provided by the system, for example, write the test case in the document to support 72 hours of service, write the test case accordingly, execute the test case, and record the actual operation time provided by the system. During the test, when a product or system fails, the time from downtime to software availability is recorded, as well as the total number of downtimes, to calculate the average downtime.
3 Fault tolerance.
Fault tolerance refers to the degree to which a system, product, or component performs as expected despite hardware or software failures.
Fault tolerance is related to the ability of a product or system to maintain a specified level of performance in the event of an operational failure or violation of a specified interface. In the event that an error or abnormality occurs in a product or system due to the user's operation of a function, the function related to the handling of the error shall be consistent with the statement in the user documentation set such as the requirements document, design document, operation manual, etc., or in the product description. No data shall be lost when operating on the product or system within the limits stated in the user's documentation set. When information is entered in violation of syntax conditions, the product or system gives a prompt and cannot be processed as input for permission.
4 Recoverability.
Recoverability refers to the extent to which a product or system is able to recover directly affected data and rebuild the desired system state in the event of an outage or failure.
Note: After a failure, a computer system may sometimes be down for a period of time, the length of which is determined by its recoverability.
Analysis] In the event of an interruption or failure of a product or system, the length of time required to restore the system and the degree of recovery of the business system reflect the recovery capability of the system, which can be restored through data backup to minimize losses. You can learn about the data backup and recovery mechanism and the data information of specific backups through the data backup and recovery methods described in the requirements specification and product description.
Software failure can manifest itself in the following scenarios.
1) Freeze: The software stops output.
2) Mismatch of running speed: The speed of data input or output does not match the needs of the system.
3) Insufficient calculation accuracy: The calculation accuracy of one or some output parameter values does not meet the requirements due to insufficient data collection or algorithm problems.
4) Defective output items: Some necessary output values are missing.
5) Redundant output: The software outputs data instructions that are not expected by the system.
When an failure occurs, what measures should be taken to rebuild the corresponding services and restore the directly affected data to users, and the measures to avoid software failure can be as follows:
1) Restart the software.
2) Restore the backed up data.
3) Restore data in one click.
4) Error operation prompt.
5) Contact the service provider.
5 Compliance with reliability.
Reliability compliance refers to the degree to which a product or system adheres to standards, conventions, or regulations related to reliability, as well as similar provisions.
Analysis] Whether the product description mentions the standards, conventions or regulations related to the reliability of the product and similar requirements, if it is mentioned and provides supporting materials, it is recognized;Otherwise, verify that the software matches the requirements of the mentioned documentation (requirements document).
About Suzhou Huax Information Technology***
Professional testing and safety product service provider.
loadrunner | fortify | sonarqube | appscan | webinspect
Fosseye Open Source Security and Compliance Governance Platform |JiHu GitLab is an all-in-one DevOps platform.
CMA CNAS Software Evaluation Lab Solution |Source**Security Audit Service.
OpenText (Microfocus) China Platinum ** Merchant |Sonarqube China General Distributor.
Appscan China Core Business |JiHu GitLab Platinum Partner.