Formal Requirements Analysis for Early Error Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Errors in software and hardware component requirements often go undetected until late in the development process, leading to increased costs due to the distance between error introduction and discovery.
Innovation Solution
A formal requirements analysis module is used to verify and validate requirements through a series of modules, including type-safety, contingency, independence, and completeness checks, generating counter-examples for errors and allowing for iterative editing and validation, enabling early detection of errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If requirements are analyzed using traditional methods, then the development process can proceed, but errors are discovered late leading to increased costs
Solution Approach 1:
The patent applies preliminary action by performing formal requirements analysis at the very beginning of the development process, before design and implementation. Multiple analysis modules (type-safety, contingency, independence, completeness, surjectivity) are executed on requirements early to detect errors beforehand, preventing them from propagating to later stages where fixes would be more costly and time-consuming.
2Reliability
If formal requirements analysis with multiple modules is applied, then error detection capability is improved, but the complexity of the analysis system increases
Solution Approach 1:
The patent segments the requirements analysis system into multiple specialized modules, each responsible for a specific aspect: type-safety module for type checking, contingency module for contingency analysis, independence module for independence verification, completeness module for completeness checking, and surjectivity module for surjectivity verification. This segmentation allows complex analysis to be broken down into manageable, focused components that can be applied systematically.
Data Source
AI summary
According to some embodiments, a system and method are provided for analyzing formal system requirements for software and hardware components in a software and hardware component specification model comprising receiving at least one requirement defined using a formal notation; determining if each of the requirements is self-conflicting via execution of a self-conflicting module; determining if two or more requirements conflict with each other via execution of a set-conflicting module after execution of the self-conflicting module; identifying each requirement involved in a conflict and how the one or more requirements conflicts via execution of an error localization module; receiving an updated requirement; repetitively analyzing each updated requirement with the self-conflicting module and the set-conflicting module; and generating an indication that requirements analysis is complete for the one or more requirements and the one or more requirements is validated for use in software design. Numerous other aspects are provided.