Sign In to Follow Application
View All Documents & Correspondence

System And Method For Validating Software Development Requirements

Abstract: System and method for validating software development requirements are disclosed. The method comprises accessing a software development requirement, extracting a plurality of tokens from the software development requirement, tagging each of the plurality of tokens to a corresponding part of speech, and deriving a pattern based on the plurality of tokens and the plurality of corresponding parts of speech. The method further comprises determining at least one of a context and a business domain of the software development requirement and identifying pre-defined rules for the plurality of tokens and pre-defined patterns for the pattern. In response to a positive identification, the software development requirement are validated by analyzing the plurality of tokens against the pre-defined rules and by analyzing the pattern against the pre-defined patterns. In response to a negative identification, a learning process is initiated based on intelligence gathered from a manual validation of the software development requirement. Figure 3

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
28 December 2015
Publication Number
03/2016
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
Parent Application
Patent Number
Legal Status
Grant Date
2023-09-20
Renewal Date

Applicants

WIPRO LIMITED
Doddakannelli, Sarjapur Road, Bangalore 560035, Karnataka, India.

Inventors

1. AMAN CHANDRA
RB-511, Purva Rivera, Marathahalli, Bangalore-560037, Karnataka, India
2. VARUN ANANT
Flat No, 310, GR Shri Nivas, Manipal County Road, Singasandra, Bangalore, Karnataka, India

Specification

Claims:We Claim:
1. A method for validating software development requirements, the method comprising:
accessing, via a processor, a software development requirement;
extracting, via the processor, a plurality of tokens from the software development requirement;
tagging, via the processor, each of the plurality of tokens to a corresponding part of speech;
deriving, via the processor, a pattern based on the plurality of tokens and the plurality of corresponding parts of speech;
determining, via the processor, at least one of a context and a business domain of the software development requirement;
identifying, via the processor, pre-defined rules for the plurality of tokens and pre-defined patterns for the pattern from an intelligence repository based on at least one of the context and the business domain;
in response to a positive identification, validating, via the processor, the software development requirement by analyzing the plurality of tokens against the pre-defined rules and by analyzing the pattern against the pre-defined patterns; and
in response to a negative identification, initiating, via the processor, a learning process based on intelligence gathered from a manual validation of the software development requirement.

2. The method of claim 1, further comprising classifying the software development requirement into at least one of a functional requirement, a non-functional requirement, and a constraint based requirement, wherein identifying the pre-defined rules and the pre-defined patterns is based on classifying the software development requirement.

3. The method of claim 1, further comprising classifying the software development requirement into at least one of an action based requirement and a feature based requirement, wherein identifying the pre-defined rules and the pre-defined patterns is based on classifying the software development requirement.

4. The method of claim 1, wherein identifying the pre-defined rules and the pre-defined patterns comprises:
building one or more queries based on the plurality of tokens and the pattern; and
executing the one or more queries against the intelligence repository.

5. The method of claim 1, wherein the intelligence repository comprises pre-defined patterns, tokens, pre-defined rules for each of the tokens, and at least one of context rules and business domain rules.

6. The method of claim 1, wherein validating further comprises:
determining one or more violations in the software development requirement; and
classifying each of the one or more violations into a violation type.

7. The method of claim 6, wherein the violation type comprises at least one of an ambiguous violation, a non-specific violation, a non-atomic violation, an incomplete violation, a duplicate violation, an un-verifiable violation, and a contradiction violation.

8. The method of claim 1, wherein validating further comprises determining one or more omissions in a set of requirements based on a historical pattern derived from a set of past similar requirements.

9. The method of claim 1, wherein initiating the learning process further comprises updating the intelligence repository with the plurality of tokens, the pattern, an outcome of manual validation, and one or more rules.

10. The method of claim 1, further comprising generating a report indicating a result of validation and including at least one of a number of software development requirements validated, a number of violations, types of violations, a number of each of the types of violations, and a reason for each of the violations.

11. A system for validating software development requirements, the system comprising:
at least one processor; and
a computer-readable medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
accessing a software development requirement;
extracting a plurality of tokens from the software development requirement;
tagging each of the plurality of tokens to a corresponding part of speech;
deriving a pattern based on the plurality of tokens and the plurality of corresponding parts of speech;
determining at least one of a context and a business domain of the software development requirement;
identifying pre-defined rules for the plurality of tokens and pre-defined patterns for the pattern from an intelligence repository based on at least one of the context and the business domain;
in response to a positive identification, validating the software development requirement by analyzing the plurality of tokens against the pre-defined rules and by analyzing the pattern against the pre-defined patterns; and
in response to a negative identification, initiating a learning process based on intelligence gathered from a manual validation of the software development requirement.

12. The system of claim 11, wherein the operations further comprise classifying the software development requirement into at least one of a functional requirement, a non-functional requirement, and a constraint based requirement, and wherein identifying the pre-defined rules and the pre-defined patterns is based on classifying the software development requirement.

13. The system of claim 11, wherein the operations further comprise classifying the software development requirement into at least one of an action based requirement and a feature based requirement, and wherein identifying the pre-defined rules and the pre-defined patterns is based on classifying the software development requirement.

14. The system of claim 11, wherein identifying the pre-defined rules and the pre-defined patterns comprises:
building one or more queries based on the plurality of tokens and the pattern; and
executing the one or more queries against the intelligence repository.

15. The system of claim 11, wherein validating further comprises:
determining one or more violations in the software development requirement; and
classifying each of the one or more violations into a violation type, the violation type comprising at least one of an ambiguous violation, a non-specific violation, a non-atomic violation, an incomplete violation, a duplicate violation, an un-verifiable violation, and a contradiction violation.

16. The system of claim 11, wherein validating further comprises determining one or more omissions in a set of requirements based on a historical pattern derived from a set of past similar requirements.

17. The system of claim 11, wherein initiating the learning process further comprises updating the intelligence repository with the plurality of tokens, the pattern, an outcome of manual validation, and one or more rules.

18. The system of claim 11, wherein the operations further comprise generating a report indicating a result of validation and including at least one of a number of software development requirements validated, a number of violations, types of violations, a number of each of the types of violations, and a reason for each of the violations.

Dated this 28th day of December, 2015
Swetha SN
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
This disclosure relates generally to software development, and more particularly to a system and method for validating software development requirements.

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 7002-CHE-2015-IntimationOfGrant20-09-2023.pdf 2023-09-20
1 Form 9 [28-12-2015(online)].pdf 2015-12-28
2 7002-CHE-2015-PatentCertificate20-09-2023.pdf 2023-09-20
2 Form 5 [28-12-2015(online)].pdf 2015-12-28
3 Form 3 [28-12-2015(online)].pdf 2015-12-28
3 7002-CHE-2015-FORM-26 [06-09-2023(online)].pdf 2023-09-06
4 Form 18 [28-12-2015(online)].pdf 2015-12-28
4 7002-CHE-2015-Written submissions and relevant documents [06-09-2023(online)].pdf 2023-09-06
5 Drawing [28-12-2015(online)].pdf 2015-12-28
5 7002-CHE-2015-AMENDED DOCUMENTS [10-08-2023(online)].pdf 2023-08-10
6 Description(Complete) [28-12-2015(online)].pdf 2015-12-28
6 7002-CHE-2015-Correspondence to notify the Controller [10-08-2023(online)].pdf 2023-08-10
7 REQUEST FOR CERTIFIED COPY [30-12-2015(online)].pdf 2015-12-30
7 7002-CHE-2015-FORM 13 [10-08-2023(online)].pdf 2023-08-10
8 abstract 7002-CHE-2015.jpg 2016-01-07
8 7002-CHE-2015-POA [10-08-2023(online)].pdf 2023-08-10
9 7002-CHE-2015-Power of Attorney-100516.pdf 2016-07-15
9 7002-CHE-2015-US(14)-HearingNotice-(HearingDate-22-08-2023).pdf 2023-08-01
10 7002-CHE-2015-ABSTRACT [31-07-2020(online)].pdf 2020-07-31
10 7002-CHE-2015-Form 1-100516.pdf 2016-07-15
11 7002-CHE-2015-CLAIMS [31-07-2020(online)].pdf 2020-07-31
11 7002-CHE-2015-Correspondence-F1-PA-100516.pdf 2016-07-15
12 7002-CHE-2015-COMPLETE SPECIFICATION [31-07-2020(online)].pdf 2020-07-31
12 7002-CHE-2015-FER.pdf 2020-01-31
13 7002-CHE-2015-CORRESPONDENCE [31-07-2020(online)].pdf 2020-07-31
13 7002-CHE-2015-RELEVANT DOCUMENTS [31-07-2020(online)].pdf 2020-07-31
14 7002-CHE-2015-FER_SER_REPLY [31-07-2020(online)].pdf 2020-07-31
14 7002-CHE-2015-PETITION UNDER RULE 137 [31-07-2020(online)].pdf 2020-07-31
15 7002-CHE-2015-FORM 3 [31-07-2020(online)].pdf 2020-07-31
15 7002-CHE-2015-OTHERS [31-07-2020(online)].pdf 2020-07-31
16 7002-CHE-2015-Information under section 8(2) [31-07-2020(online)].pdf 2020-07-31
17 7002-CHE-2015-OTHERS [31-07-2020(online)].pdf 2020-07-31
17 7002-CHE-2015-FORM 3 [31-07-2020(online)].pdf 2020-07-31
18 7002-CHE-2015-PETITION UNDER RULE 137 [31-07-2020(online)].pdf 2020-07-31
18 7002-CHE-2015-FER_SER_REPLY [31-07-2020(online)].pdf 2020-07-31
19 7002-CHE-2015-CORRESPONDENCE [31-07-2020(online)].pdf 2020-07-31
19 7002-CHE-2015-RELEVANT DOCUMENTS [31-07-2020(online)].pdf 2020-07-31
20 7002-CHE-2015-COMPLETE SPECIFICATION [31-07-2020(online)].pdf 2020-07-31
20 7002-CHE-2015-FER.pdf 2020-01-31
21 7002-CHE-2015-CLAIMS [31-07-2020(online)].pdf 2020-07-31
21 7002-CHE-2015-Correspondence-F1-PA-100516.pdf 2016-07-15
22 7002-CHE-2015-ABSTRACT [31-07-2020(online)].pdf 2020-07-31
22 7002-CHE-2015-Form 1-100516.pdf 2016-07-15
23 7002-CHE-2015-Power of Attorney-100516.pdf 2016-07-15
23 7002-CHE-2015-US(14)-HearingNotice-(HearingDate-22-08-2023).pdf 2023-08-01
24 abstract 7002-CHE-2015.jpg 2016-01-07
24 7002-CHE-2015-POA [10-08-2023(online)].pdf 2023-08-10
25 REQUEST FOR CERTIFIED COPY [30-12-2015(online)].pdf 2015-12-30
25 7002-CHE-2015-FORM 13 [10-08-2023(online)].pdf 2023-08-10
26 Description(Complete) [28-12-2015(online)].pdf 2015-12-28
26 7002-CHE-2015-Correspondence to notify the Controller [10-08-2023(online)].pdf 2023-08-10
27 Drawing [28-12-2015(online)].pdf 2015-12-28
27 7002-CHE-2015-AMENDED DOCUMENTS [10-08-2023(online)].pdf 2023-08-10
28 Form 18 [28-12-2015(online)].pdf 2015-12-28
28 7002-CHE-2015-Written submissions and relevant documents [06-09-2023(online)].pdf 2023-09-06
29 Form 3 [28-12-2015(online)].pdf 2015-12-28
29 7002-CHE-2015-FORM-26 [06-09-2023(online)].pdf 2023-09-06
30 Form 5 [28-12-2015(online)].pdf 2015-12-28
30 7002-CHE-2015-PatentCertificate20-09-2023.pdf 2023-09-20
31 7002-CHE-2015-IntimationOfGrant20-09-2023.pdf 2023-09-20
31 Form 9 [28-12-2015(online)].pdf 2015-12-28

Search Strategy

1 Search58_28-01-2020.pdf

ERegister / Renewals

3rd: 14 Dec 2023

From 28/12/2017 - To 28/12/2018

4th: 14 Dec 2023

From 28/12/2018 - To 28/12/2019

5th: 14 Dec 2023

From 28/12/2019 - To 28/12/2020

6th: 14 Dec 2023

From 28/12/2020 - To 28/12/2021

7th: 14 Dec 2023

From 28/12/2021 - To 28/12/2022

8th: 14 Dec 2023

From 28/12/2022 - To 28/12/2023

9th: 14 Dec 2023

From 28/12/2023 - To 28/12/2024

10th: 18 Dec 2024

From 28/12/2024 - To 28/12/2025