Impact Analysis Documents from Contextual Specification Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing impact analysis techniques for change requests are manual and error-prone, primarily focusing on source code level analysis, failing to provide value to requirement experts and not addressing the impact at the requirement specification level.
Innovation Solution
A system and method for generating an impact analysis specification document using a contextual specification model, keyphrase extraction, and fine-grained impact analysis to identify and document the impact of change requests on features, processes, and specification elements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual impact analysis is performed by requirement experts, then the analysis can be tailored to specific business needs, but the process becomes cumbersome and error-prone
Solution Approach 1:
The system enables self-service by automatically performing impact analysis without requiring manual intervention from requirement experts. The automated system processes change requests, analyzes dependencies, and generates impact analysis documents independently, eliminating the time-consuming manual review process while maintaining accuracy through structured analysis frameworks.
Solution Approach 2:
The patent replaces the mechanical manual analysis process with an automated computer-based system. The system uses software algorithms to process change requests, analyze dependencies across requirements and designs, and generate impact analysis documents, substituting the manual mechanical process with an automated information processing system.
2Measurement precision
If source code level analysis is performed, then detailed technical impact can be identified, but it does not provide value to requirement experts and fails to address requirement specification level impact
Solution Approach 1:
The patent transitions the impact analysis from the source code level (technical dimension) to the requirement specification level (business dimension). By operating at multiple levels of abstraction including requirements, designs, and source code, the system provides comprehensive impact detection that serves both requirement experts and technical teams, enabling cross-level traceability and analysis.
3Productivity
If automated impact analysis system is implemented, then manual effort is reduced and productivity increases, but system complexity increases
Solution Approach 1:
The system segments the impact analysis process into distinct modular components: change request intake, dependency analysis module, impact identification module, and document generation module. This segmentation allows each component to function independently, simplifying the overall system architecture while enabling automated high-throughput processing of change requests through coordinated operation of modular units.
Data Source
AI summary
This disclosure relates generally to impact analysis and, more particularly, to generation of impact analysis specification document for a change request. The existing state-of-art techniques for impact analysis for a change request are mostly manual, and further most of the research on impact analysis is based on source code analysis and does not address the impact of the CR at multi-granular levels. The disclosed techniques perform a fine-grained impact analysis of the CR at multi-granular levels. The fine-grained impact analysis at multi-granular includes identifying a set of impacted specification elements, a set of impacted processes, and a set of impacted features based on several steps including generating a contextual specification model and extracting a plurality of key-phrases.