Requirement Feature Modeling With Dependency Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for requirement specification in large-scale software development lack a holistic view of system evolution with interconnections, leading to inconsistencies and manual, document-centric processes that are time-consuming and SME-dependent.

Innovation Solution

A method and system for feature specification and dependency extraction from requirement specification documents using a feature model generation technique, specification extraction technique, and dependency extraction technique, employing Natural Language Processing (NLP) to generate hierarchical product feature models and update dependency associations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional methods (UML, BPMN, Feature Modeling) are used for requirement specification, then a specific view of the system can be addressed, but a holistic view of system evolution with interconnections cannot be achieved

Engineering Contradiction:
Improvespecific view addressingVSAvoidholistic view capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent merges multiple conventional modeling approaches (UML, BPMN, Feature Modeling) into a unified feature model that captures both specific views and holistic system evolution. The feature model integrates structural, behavioral, and evolutionary aspects into a single comprehensive representation that maintains interconnections across different system views.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The feature model serves multiple functions simultaneously: it represents system structure, captures behavioral sequences, tracks evolutionary changes, and maintains interconnections between different views. This multi-functional model replaces the need for separate specialized models for each view.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If modeling-based approaches (UML, BPMN, Feature Modeling) are specified for large-scale product development, then system views can be represented, but the process becomes tedious and time-consuming

Engineering Contradiction:
Improvemodel representation accuracyVSAvoidspecification speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system automatically extracts feature models from existing requirement documentation without requiring manual modeling by specialists. The automated extraction process analyzes natural language requirements and generates structured feature models, eliminating the tedious manual specification process while maintaining model accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical modeling processes with automated computational extraction. Instead of specialists manually creating models through tedious processes, an automated system processes requirement documents and generates feature models algorithmically, significantly improving productivity.

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

3Adaptability or versatility

If manual document-centric processes are used for requirement specification, then flexibility in documentation is maintained, but the process becomes SME-dependent and inconsistent

Engineering Contradiction:
Improvedocumentation flexibilityVSAvoidconsistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system transforms unstructured natural language requirement documents into structured feature models with standardized parameters and relationships. This transformation maintains the flexibility of natural language documentation while imposing consistent structural parameters that enable automated processing and reduce SME-dependency.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The feature model acts as an intermediary between diverse requirement documents and the development process. It provides a standardized intermediate representation that captures requirements consistently while allowing the original flexible documentation formats to be preserved as input sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4202642B1Method and system for feature specification and dependency information extraction from requirement specification documents
Publication Date: 2025.11.12 TATA CONSULTANCY SERVICES LTD
  • EP4202642B1 patent drawingFigure 1
  • EP4202642B1 patent drawingFigure 2
  • EP4202642B1 patent drawingFigure 3

AI summary

The present disclosure provides a holistic model for feature specification and dependency representation for requirement specification documents where the conventional models fail to provide. The present disclosure receives a plurality of requirement specification documents and a related data. A product feature model is generated based on the plurality of requirement specification documents and the related data using a feature model generation technique. The product feature model includes a plurality of product feature elements. The plurality of product feature elements includes a feature area, a major feature and a plurality of features. A specification model is generated further for each of the plurality of features using a specification extraction technique. Post generating the specification model, a plurality of dependency associations are generated for each of a plurality of specification elements of the specification model using a dependency extraction technique. Finally, the plurality of dependency associations are updated in the specification model.