Test Support Device for Comprehensive System Configuration Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for testing software systems, such as those using the Web3Tier model, fail to comprehensively test all configurations related to specific system components, leading to potential issues when these configurations are not thoroughly validated, especially as dependencies increase and modifications become difficult due to forgotten component details.
Innovation Solution
A test support device and method that store and utilize relation information about system components, functionalities, and programs, allowing for the extraction and output of all relevant system configurations when a specific functionality or program is specified, enabling comprehensive and quick testing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If test cases are prepared for each component and presented collectively, then test coverage is improved, but the ability to test all configurations related to a specific system component is lost
Solution Approach 1:
The patent segments the system configuration into multiple dimensions: system components, functionalities, and programs. By creating a multi-dimensional relation information structure that stores these segmented elements and their relationships, the system can selectively extract and test only the configurations related to a specific component, rather than testing all components collectively or none at all.
Solution Approach 2:
The patent introduces an intermediary extraction means that acts as a mediator between the stored relation information and the test execution. This extraction means processes the relation information to identify and extract only the relevant system configurations associated with a specified component, functionality, or program, enabling precise configuration-specific testing while maintaining comprehensive test coverage.
2Reliability
If comprehensive testing of all system configurations is performed, then reliability is improved, but testing time and complexity increase
Solution Approach 1:
The patent extracts only the necessary subset of system configurations related to a specific component, functionality, or program from the complete set of all possible configurations. By taking out and isolating only the relevant configurations for testing, the system achieves comprehensive validation of affected areas without the time cost of testing every possible system configuration.
Solution Approach 2:
The patent performs preliminary action by pre-storing the relation information between system components, functionalities, and programs in a structured format before testing begins. This preliminary organization of data enables rapid extraction and identification of relevant configurations during testing, significantly reducing the time required for comprehensive configuration validation.
3Adaptability or versatility
If relation information for all system configurations is stored and analyzed, then comprehensive testing capability is improved, but device complexity increases
Solution Approach 1:
The patent creates a universal relation information storage structure that can handle multiple types of queries and extractions. The same stored relation information serves multiple functions: extracting configurations by component, by functionality, by program, and by various combinations thereof. This multi-functional approach reduces device complexity compared to maintaining separate data structures for each extraction scenario.
Data Source
AI summary
A test support device which can test all configurations of a system including a specific system component, comprehensively and quickly, is provided. A test support device (100) includes a storage unit (102) and an extraction processing unit (101). A configuration of a system is defined with a plurality of functionalities to be maintained by the system and a set of programs implementing the functionalities respectively. The storage unit (102) stores component-relation information (201) which indicates an identifier of each of one or more systems, an identifier of each of a plurality of functionalities to be maintained by each of the systems, and an identifier of each of one or more programs being capable of implementing each of the functionalities. The extraction processing unit (101) extracts, when a functionality or a program is specified, a configuration of a system including the specified functionality or the specified program on the basis of the component-relation information (201), and outputs the extracted configuration of a system.