GB/T 38639-2020 in English
VALIDSystems and software engineering—Software combinatorial testing method
- Issued on:2020-04-28
- Implemented on:2020-11-01
- File Format:PDF
- Delivery:Via email within 5 business days
$534.00
《GB/T 38639-2020系统与软件工程 软件组合测试方法》由TC28（全国信息技术标准化技术委员会）归口，主管部门为国家标准化管理委员会。
Introduction
Interpretation of the core content of the standard
This standard defines a complete methodological framework for software combination testing, which mainly includes three technical modules:
- Input preprocessing: Discretize continuous parameters. In the example, the age parameter of the airline booking system is divided into equivalence classes
- Combination strength system: Establish a five-level strength model from single choice to full combination
- Constraint processing mechanism: Support conditional/unconditional constraint expressions, including 12 relational operators and logical operators
Combination strength grading system
| Strength level | Coverage requirements | Applicable scenarios | Comparison of the number of use cases |
|---|---|---|---|
| Single Choice | Each parameter value appears at least once | Basic function verification | Minimum |
| Pairwise combination | Coverage of any two parameter value combinations | Regular test (default) | Medium |
| K intensity combination | Specify the complete combination of K parameters | Key parameter interaction | Exponential growth with K value |
Implementation points
Airline booking system example
Appendix B of the standard shows a typical application scenario:
- Parameter discretization: Divide the continuous age parameter into intervals such as [12-25][55-70]
- Variable strength setting: Use a 3-strength combination for key parameters such as the number of CPU cores and memory
- Constraint processing: The ia64 platform is limited to using only OS3/OS4 systems
Engineering application suggestions
Test design process optimization
- Parameter analysis phase: Use equivalence class partitioning to process continuous parameters
- Strength setting phase: Refer to the software integrity level requirements in Appendix A of the standard
- Constraint declaration phase: Use the XML/JSON format specifications defined in the standard
Solutions to Common Problems
| Problem Type | Standard Clauses | Solutions |
|---|---|---|
| Too many parameter values | Chapter 3 | Use boundary value + equivalence class combination strategy |
| Combinatorial Explosion | Chapter 5 | Use variable strength + constraint condition filtering |
Technology Evolution Analysis
Innovations of this standard compared with international mainstream methods (such as ACTS, PICT):
- For the first time, a standardized definition of variable strength combination is proposed
- A mapping relationship between software integrity level and combination strength is established
- Normalized XML/JSON input and output format
Loading PDF document...
Error loading PDF. Please make sure the file is valid and try again.
We also recommend
-
GB/T 44601-2024 in English
Information technology service—Service life cycle processes
2024-09-29 -
GB/T 8566-2022 in English
Systems and software engineering—Software life cycle processes
2022-10-12 -
GB/T 46900-2025 in English
Systems and software engineering—General technical requirements for low-code development platform
2025-12-31 -
GB/T 43208.2-2025 in English
Information technology service—Intelligent operation and maintenance—Part 2：Data governance
2025-12-02 -
GB/T 38634.5-2024 in English
Systems and software engineering—Software testing—Part 5：Keyword-driven testing
2024-10-26 -
GB/T 9385-2008 in English
Norm of computer software requirements specification
2008-04-11 -
GB/T 15532-2008 in English
Specification of computer software testing
2008-04-11 -
GB/T 25000.1-2021 in English
Systems and software engineering-Systems and software quality requirements and evaluation (SQuaRE)-Part 1:Guide to SQuaRE
2021-04-30
