Processing

Please wait...

Settings

Settings

Goto Application

1. WO2020111930 - SYSTEM FOR ANALYSING USER REQUIREMENTS TO DETERMINE REQUIREMENT VOLATILITY AND METHOD THEREOF

Note: Text based on automatic Optical Character Recognition processes. Please use the PDF version for legal matters

[ EN ]

CLAIMS:

1. A system comprising an enforcement engine (102) that is operatively coupled with a computing device, characterized in that, the enforcement engine (102) determines requirement volatility by analysing one or more user requirements for a product further comprising of:

i. a document matching and data manager (1 12) for reading, extracting and restructuring one or more tagged requirements from any or a combination of a requirement document and a change request document and storing said one or more tagged requirements in a structured repository;

ii. a baselined document matching and categorizer (114) for retrieving a set of baselined documents using any or a combination of the requirement document and the change request document and categorizing each of the set of baselined documents based on an associated time-stamp to determine initial number of requirements from a first baselined document;

iii. a categorizer and matching component (1 16) for associating each of the one or more tagged requirement with a volatility category based on matching of a current baselined document and a previous baselined document to compute total number of requirements and determining one or more attributes of each of the one or more tagged requirements using a knowledge data (122); and

iv. a volatility impact factor analyzer (1 18) for analyzing at least one of a requirement volatility, RV, a requirement volatility and impact function, V and requirement volatility and impact factor, RVIF based on any or a combination of a development lifecycle phase, time period for work performed for the development lifecycle phase and number of each volatility type associated with the one or more tagged requirements to generate an alert when at least one of RV, V and RVIF is greater than a pre-defined threshold.

2. The system of claim 1 , wherein said document matching and data manager (1 12) receives the one or more tagged requirements from a user computing device

(124) that enables tagging of each of the one or more user requirements from any or a combination of the requirement document and the change request document and associates each tagged requirement with a running tagged identifier obtained using last running identifier stored in a data repository (168).

3. The system of claim 2, wherein the tagged requirements include any or a combination of Business Requirement, BR, System Requirement, SR, Functional Requirement, FR, Non-Functional Requirement, NF or Use Case, UC for associating the last running identifier based on the tag type.

4. The system of claim 1 , wherein when the one or more tagged requirements are obtained from the requirement document, the document matching and data manager (112) validates the one or more tagged requirements by matching each of the one or more user requirements with existing requirement data in the data repository (168) to avoid duplication of the one or more tagged requirements.

5. The system of claim 1 , wherein when the one or more tagged requirements are obtained from the change request document, the document matching and data manager (1 12) verifies the one or more tagged requirements by matching each of the one or more user requirements with existing requirement data in the data repository (168) and associates a difficulty level into matched data.

6. The system of claim 1 , wherein the volatility category is selected from any of added requirement, deleted requirement or modified requirement.

7. The system of claim 1 , wherein the one or more attributes include a difficulty level and a weightage of difficulty level associated with each requirement.

8. The system of claim 1 , wherein the volatility impact factor analyzer (1 18) determines the development lifecycle phase of the product based on time stamp of the current baselined document and first baselined document.

9. The system of claim 1 , wherein the volatility impact factor analyzer (1 18) determines the development lifecycle phase using a project schedule.

10. A method (800) for determining requirement volatility by analysing one or more user requirements for a product, characterized in that the method comprises the

step of configuring an enforcement engine that is operatively coupled with a computing device, wherein the enforcement engine performs the steps of:

i. reading, extracting and restructuring (802), one or more tagged requirements from any or a combination of a requirement document and a change request document and storing said one or more tagged requirements in a structured repository;

ii. retrieving (804), a set of baselined documents using any or a combination of the requirement document and the change request document and categorizing each of the set of baselined documents based on an associated time-stamp to determine initial number of requirements from a first based lined document;

iii. associating (806), each of the one or more tagged requirement with a volatility category based on matching of a current baselined document and a previous baselined document to compute total number of requirements and determining one or more attributes of each of the one or more tagged requirement using knowledge data; and

iv. analyzing (808), at least one of a requirement volatility, RV, a requirement volatility and impact function, V and requirement volatility and impact factor, RVIF based on any or a combination of a development lifecycle phase, time period for work performed for the development phase cycle phase and number of each volatility type associated with the one or more tagged requirements to generate an alert when at least one of RV, V and RVIF is greater than a pre-defined threshold.