Skip to content

Requirements Analysis Agent ​

Identifies spec change points and auto-generates diff lists, evidence chains and impact analysis.

Core Pain Points ​

  1. Scattered change information: Inputs typically include the pre-change specification, post-change specification, and a new change table — with information spread across multiple documents. Manual comparison of version differences item by item is time-consuming and prone to omissions.
  2. Difficult association between evidence and impact scope: Each change point must trace back to evidence in the design specification or the change table; the impact scope involves modules, interfaces, and downstream work products, which depend heavily on the analyst's experience.
  3. Inconsistent deliverable formats: Change-point summary tables, evidence lists, and impact analysis reports are often maintained separately by hand; the lack of a unified structure increases review and communication overhead.

Solution & Technical Implementation ​

  1. Input parsing and diff identification: Accepts pre-change and post-change specifications along with new change tables, performs structured document parsing, and builds comparable content units organized by chapter, item, and key field.
  2. Change points bound to evidence: Identifies additions, deletions, and modifications; generates a change-point list and preserves the source document, chapter, or table evidence for each change point.
  3. Impact scope analysis: Based on the change points and design specification context, produces an impact analysis report that clearly identifies affected functions, modules, and downstream work products that need concurrent verification.
  4. Standardized output: Consistently generates a change-point summary table, evidence list, and impact analysis report, producing reusable, structured results.

Highlights ​

  • Automatic change-point extraction: Converts multi-document comparison into a structured diff list, reducing the risk of manual omissions.
  • Traceable evidence chain: Each change point is tied back to its source evidence, simplifying review and verification.
  • Downstream reusability: Outputs can be consumed further by the Code Review Agent, test case generation, and change-tracking workflows.

Business Value ​

  • Reduces manual comparison, consolidation, and report-writing effort, shortening the review-preparation cycle for requirement changes.
  • Unified templates and evidence binding lower the risk of missed detections, false judgments, and inconsistent output styles across different contributors.
  • The same diff-identification and impact-analysis pipeline can be rolled out horizontally across product lines, projects, and specification types.
  • Change points, evidence, and impact reports form a traceable record that feeds subsequent testing, release, and compliance audits.

SDW AIKO Product Documentation