Software Requirements Chaining for Test Coverage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods are inefficient in determining and applying software requirements chaining, particularly in complex software applications like aviation software, where internal requirements without external input/output information cannot be independently tested, leading to incomplete test generation.
Innovation Solution
A system and method that analyze and visualize software requirements dependencies, including horizontal and vertical chaining, to generate executable test procedures by combining internal and external requirements, and identify test boundaries for optimized test steps.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional test generation methods are used without requirements chaining analysis, then the test generation process is simpler, but test coverage is incomplete because internal requirements cannot be independently tested
Solution Approach 1:
The patent segments requirements into different types (internal requirements without external I/O, external requirements with I/O, chained requirements) and processes them through different pathways. Internal requirements are identified and chained with external requirements to form testable requirement sets, while external requirements are processed independently. This segmentation allows complete test coverage without requiring complex interdependent testing of all requirements.
Solution Approach 2:
The patent introduces a requirements chaining analysis system that acts as an intermediary between requirement specification and test generation. This intermediary analyzes requirements, identifies chaining relationships, and produces structured test cases that incorporate both internal and external requirements. The intermediary transforms the complex problem of testing interdependent requirements into a systematic process that maintains completeness while managing complexity.
2Reliability
If requirements chaining analysis is performed to achieve complete test coverage, then test coverage improves, but the time required for test generation increases
Solution Approach 1:
The patent performs requirements chaining analysis as a preliminary step before test execution. By pre-identifying chained requirements and their relationships, the system prepares structured test cases in advance. This preliminary analysis of requirement dependencies allows the testing phase to proceed more efficiently, as the complex chaining logic has already been resolved during test case generation rather than during test execution.
Solution Approach 2:
The requirements chaining analysis system automatically analyzes requirement relationships and generates test cases without manual intervention. The system self-services by identifying internal requirements, tracing their dependencies to external requirements, and automatically constructing chained test cases. This automation eliminates time-consuming manual analysis while maintaining complete test coverage.
3Productivity
If internal requirements are tested independently without chaining, then test execution is faster, but test validity is reduced because internal requirements lack external input/output context
Solution Approach 1:
The patent merges internal requirements with external requirements through requirements chaining to form composite test cases. Internal requirements that lack standalone testability are combined with external requirements that provide necessary input/output context. The merged test cases execute efficiently while maintaining validity, as they incorporate both the internal logic being tested and the external interface context required for meaningful validation.
4Reliability
If all requirements are tested individually, then test completeness is achieved, but resource utilization is inefficient due to redundant testing of shared external input/output settings
Solution Approach 1:
The patent creates universal test cases through requirements chaining that can validate multiple internal requirements simultaneously using shared external input/output settings. A single externally-chained test case may exercise multiple internally-chained requirements, making the test case multi-functional. This universality maintains test completeness while improving resource utilization by eliminating redundant execution of identical external test setups.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method(100) and system(1100), the method(1100) including receiving a set of requirements for a software application, the set of requirements comprising a plurality of software requirements identified for the software application(1105); analyzing the set of requirements to determine dependencies between the plurality of software requirements in the set of requirements(1110); generating a visualization of the determined dependencies and test boundaries between the plurality of software requirements in the set of requirements(1115); storing the generated visualization of the determined dependencies and test boundaries between the plurality of software requirements in the set of requirements in a record(1120); and applying the determined dependencies in the record to at least one of (i) optimize test steps in a test procedure and (ii) generate an executable test procedure that exercises external inputs and outputs for the software application.