Automated System Requirements Analysis Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual review of system requirements is a slow, expensive, and error-prone process that becomes increasingly difficult as system complexity grows, often leading to undetected deficiencies that result in costly vulnerabilities and system failures, especially in early stages of software development.

Innovation Solution

An automated system requirements analysis service that ingests natural-language representations of system requirements, generates a system model, and performs analysis against codified rules to identify violations and suggest remedial actions, relieving human analysts of the need for language and ontology learning and facilitating iterative refinement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual review of system requirements is performed, then analysis can be conducted with human judgment and adaptability, but the process becomes slow, expensive, and error-prone as system complexity increases

Engineering Contradiction:
Improveaccuracy of requirement analysisVSAvoidtime required for requirement analysis
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces the manual mechanical review process with an automated computer-based system that uses natural language processing, semantic analysis, and rule-based validation to analyze system requirements. This substitution eliminates human analysts from the direct review process, dramatically reducing time and cost while maintaining or improving accuracy through consistent application of validation rules.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service automated analysis where the computer-operated system independently performs requirement validation without human intervention. The automated system generates analysis reports, identifies deficiencies, and provides recommendations, allowing organizations to conduct thorough requirement analysis without relying on external or internal manual review resources.

Inventive Principle:
Principle #25Self-service

2Measurement precision

If manual review of system requirements is performed, then human analysts can identify complex issues, but the thoroughness, accuracy, and consistency decrease as system complexity increases

Engineering Contradiction:
Improveaccuracy of requirement analysisVSAvoidcomplexity of system requirements
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the complex requirement analysis process into distinct automated components: natural language processing to extract requirements, semantic analysis to understand meaning, rule-based validation to check consistency, and report generation to document findings. This segmentation allows the system to handle increasing complexity by processing different aspects of requirements through specialized automated modules rather than relying on human analysts to manage all complexities simultaneously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the parameters of analysis by transforming unstructured natural language requirements into structured data representations that can be systematically validated against predefined rules. This parameter transformation enables consistent and accurate analysis of complex requirements by converting them into a format suitable for automated processing and validation.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If system requirements are validated manually, then human analysts can provide expert judgment, but the process is expensive and produces work of inconsistent quality

Engineering Contradiction:
Improveconsistency of analysis qualityVSAvoidcost of requirement analysis
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent replaces expensive manual human analysis with automated computer-based processing that consistently applies validation rules without variation. This substitution eliminates the variability in human analyst quality while reducing costs through automation, providing consistent analysis results regardless of the complexity or volume of requirements being reviewed.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Ease of manufacture

If system requirements are analyzed early in the development lifecycle, then downstream costs are reduced, but manual analysis at this stage is particularly slow and expensive

Engineering Contradiction:
Improvedownstream cost of deficienciesVSAvoidtime for early requirement analysis
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent enables preliminary automated analysis of system requirements early in the development lifecycle, identifying deficiencies before system design and implementation begin. By performing this analysis preliminarily and automatically, the system reduces downstream costs of fixing issues later while avoiding the time delays associated with manual early-stage review.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11971997B2Systems and methods for automated system requirement analysis
Publication Date: 2024.04.30 RTX BBN TECH INC
  • US11971997B2 patent drawing
  • US11971997B2 patent drawing
  • US11971997B2 patent drawing

AI summary

Techniques for automated system requirements analysis are disclosed. A system requirements analysis (SRA) service generates a system model that includes system requirements, at least by performing natural-language processing on a natural-language representation of the system requirements. Based at least on the system model, the SRA service performs an analysis of the system requirements against codified system requirements rules. The SRA service determines, based at least on the analysis of the system requirements against the codified system requirements rules, that the system requirements include a violation of a system requirements rule. The SRA service generates a report that identifies at least (a) the violation of the system requirements rule and (b) a suggested action to remediate the violation of the system requirements rule.