Abstract: A consistency assessment system (102) for assessment of consistency of a software product includes a mapping module (118) to obtain a plurality of configuration elements associated with the software product being developed, where each of the plurality of configuration elements influence software product development. Each of the plurality of configuration elements pertains to one of a plurality of element categories influencing software product development. The mapping module (118) further identifies based on one or more identifiers, association of at least one configuration element from among the plurality of configuration elements with at least one other configuration element from among the plurality of configuration elements. Upon identification, an assessing module (122) determines a requirement consistency index (RCI) for assessment of consistency of the software product based on the identified association. The RCI indicates an overall consistency of the software product.
CLIAMS:1. A consistency assessment system (102) for assessment of consistency of a software product comprising:
a processor (110);
a mapping module (118), coupled to the processor (110), to,
obtain a plurality of configuration elements associated with the software product being developed, wherein each of the plurality of configuration elements influence software product development, and wherein each of the plurality of configuration elements pertain to one of a plurality of element categories influencing software product development; and
identify, based on one or more identifiers, association of at least one configuration element from among the plurality of configuration elements with at least one other configuration element from among the plurality of configuration elements; and
an assessing module (122), coupled to the processor (110), to,
determine a requirement consistency index (RCI) for assessment of consistency of the software product based on the identified association, the RCI being indicative of an overall consistency of the software product.
2. The consistency assessment system (102) as claimed in claim 1, wherein the mapping module (118) identifies an association of at least one configuration element with the at least one other configuration element belonging to same element category.
3. The consistency assessment system (102) as claimed in claim 1, wherein the mapping module (118) identifies an association of at least one configuration element with the at least one other configuration element belonging to different element categories.
4. The consistency assessment system (102) as claimed in claim 1, wherein the mapping module (118) further generates a configuration structure based on the association.
5. The consistency assessment system (102) as claimed in claim 1 further comprising an analyzing module (120) to analyze a configuration structure to obtain a requirement inconsistency matrix (RIM) and a consistency value for each of the plurality of configuration elements for determining the RCI, wherein the RIM is indicative of inconsistencies in the configuration structure.
6. The consistency assessment system (102) as claimed in claim 5, wherein the consistency value of 1 is indicative of a consistent configuration element and the consistency value of 0 is indicative of an inconsistent configuration element.
7. The consistency assessment system (102) as claimed in claim 1, wherein the assessing module (122) determines the RCI based on a traceability analysis, wherein the traceability analysis comprises determining whether a configuration element is mapped to other configuration element in a forward direction and a backward direction.
8. The consistency assessment system (102) as claimed in claim 1, wherein the assessing module (122) determines the RCI based on a conservation analysis, wherein the conservation analysis comprises ascertaining whether a configuration element connected in a forward direction, to other configuration element, achieves a purpose of other configuration element.
9. The consistency assessment system (102) as claimed in claim 1, wherein the plurality of element categories include a Goals and Objectives category, a Process and Sub-Process category, a Requirement category, and a Use Case category.
10. A method for assessment of consistency of a software product, the method comprising:
obtaining a plurality of configuration elements associated with the software product being developed, wherein each of the plurality of configuration elements influence software product development, and wherein each of the plurality of configuration elements pertain to one of a plurality of element categories influencing software product development;
generating a configuration structure by identifying an association of at least one configuration element from among the plurality of configuration elements with at least one other configuration element from among the plurality of configuration elements, based on one or more identifiers; and
determining a requirement consistency index (RCI) for assessment of consistency of the software product based on the mapping, the RCI being indicative of an overall consistency of the software product.
11. The method as claimed in claim 10, wherein the generating comprises identifying the association of at least one configuration element to the at least one other configuration element belonging to same element category.
12. The method as claimed in claim 10, wherein the generating comprises identifying the association of at least one configuration element with the at least one other configuration element belonging to different element categories.
13. The method as claimed in claim 10 further comprising analyzing the configuration structure to obtain a requirement inconsistency matrix (RIM) and a consistency value of each of the plurality of configuration elements for determining the RCI, wherein the RIM is indicative of inconsistencies in the configuration structure.
14. The method as claimed in claim 10, wherein the RCI is determined based on at least one of a traceability analysis and a conservation analysis, wherein the traceability analysis comprises determining whether a configuration element is mapped to other configuration element in a forward direction and a backward direction, and wherein the conservation analysis comprises ascertaining whether a configuration element is connected in a forward direction, to other configuration element, achieves a purpose of other configuration element.
15. The method as claimed in claim 10, wherein the plurality of element categories comprises a Goals and Objectives category, a Process and Sub-Process category, a Requirement category, and a Use Case category.
16. A non-transitory computer-readable medium having embodied thereon a computer program for executing a method comprising:
obtaining a plurality of configuration elements associated with a software product being developed, wherein each of the plurality of configuration elements influence software product development, and wherein each of the plurality of configuration elements pertain to one of a plurality of element categories influencing software product development;
generating a configuration structure by identifying an association of at least one configuration element from among the plurality of configuration elements with at least one other configuration element from among the plurality of configuration elements, based on one or more identifiers; and
determining a requirement consistency index (RCI) for assessment of consistency of the software product based on the mapping, the RCI being indicative of an overall consistency of the software product.. ,TagSPECI:As Attached
| # | Name | Date |
|---|---|---|
| 1 | 2051-MUM-2013-IntimationOfGrant04-04-2022.pdf | 2022-04-04 |
| 1 | SPEC in.pdf | 2018-08-11 |
| 2 | 2051-MUM-2013-PatentCertificate04-04-2022.pdf | 2022-04-04 |
| 2 | FORM 5.pdf | 2018-08-11 |
| 3 | 2051-MUM-2013-Written submissions and relevant documents [11-10-2021(online)].pdf | 2021-10-11 |
| 3 | 2051-MUM-2013-PETITION UNDER RULE-138(3-1-2014).pdf | 2018-08-11 |
| 4 | 2051-MUM-2013-US(14)-HearingNotice-(HearingDate-28-09-2021).pdf | 2021-10-03 |
| 4 | 2051-MUM-2013-FORM 5(8-1-2014).pdf | 2018-08-11 |
| 5 | 2051-MUM-2013-FORM-26 [27-09-2021(online)].pdf | 2021-09-27 |
| 5 | 2051-MUM-2013-FORM 3(1-11-2013).pdf | 2018-08-11 |
| 6 | 2051-MUM-2013-FORM 26(27-9-2013).pdf | 2018-08-11 |
| 6 | 2051-MUM-2013-Correspondence to notify the Controller [23-09-2021(online)].pdf | 2021-09-23 |
| 7 | 2051-MUM-2013-form 18.pdf | 2018-08-11 |
| 7 | 2051-MUM-2013-CLAIMS [24-12-2019(online)].pdf | 2019-12-24 |
| 8 | 2051-MUM-2013-FORM 13(8-1-2014).pdf | 2018-08-11 |
| 8 | 2051-MUM-2013-COMPLETE SPECIFICATION [24-12-2019(online)].pdf | 2019-12-24 |
| 9 | 2051-MUM-2013-DRAWING [24-12-2019(online)].pdf | 2019-12-24 |
| 9 | 2051-MUM-2013-FORM 1(8-1-2014).pdf | 2018-08-11 |
| 10 | 2051-MUM-2013-FER_SER_REPLY [24-12-2019(online)].pdf | 2019-12-24 |
| 10 | 2051-MUM-2013-FORM 1(3-1-2014).pdf | 2018-08-11 |
| 11 | 2051-MUM-2013-CORRESPONDENCE(8-1-2014).pdf | 2018-08-11 |
| 11 | 2051-MUM-2013-OTHERS [24-12-2019(online)].pdf | 2019-12-24 |
| 12 | 2051-MUM-2013-CORRESPONDENCE(3-1-2014).pdf | 2018-08-11 |
| 12 | 2051-MUM-2013-FORM 3 [05-12-2019(online)].pdf | 2019-12-05 |
| 13 | 2051-MUM-2013-CORRESPONDENCE(27-9-2013).pdf | 2018-08-11 |
| 13 | 2051-MUM-2013-Information under section 8(2) (MANDATORY) [05-12-2019(online)].pdf | 2019-12-05 |
| 14 | 2051-MUM-2013-CORRESPONDENCE(11-7-2013).pdf | 2018-08-11 |
| 14 | 2051-MUM-2013-FER.pdf | 2019-06-26 |
| 15 | 2051-MUM-2013-CORRESPONDENCE(1-11-2013).pdf | 2018-08-11 |
| 15 | 2051-MUM-2013-DRAWINGS.pdf | 2019-06-14 |
| 16 | 2051-MUM-2013-Response to office action (Mandatory) [14-06-2019(online)].pdf | 2019-06-14 |
| 17 | 2051-MUM-2013-DRAWINGS.pdf | 2019-06-14 |
| 17 | 2051-MUM-2013-CORRESPONDENCE(1-11-2013).pdf | 2018-08-11 |
| 18 | 2051-MUM-2013-FER.pdf | 2019-06-26 |
| 18 | 2051-MUM-2013-CORRESPONDENCE(11-7-2013).pdf | 2018-08-11 |
| 19 | 2051-MUM-2013-CORRESPONDENCE(27-9-2013).pdf | 2018-08-11 |
| 19 | 2051-MUM-2013-Information under section 8(2) (MANDATORY) [05-12-2019(online)].pdf | 2019-12-05 |
| 20 | 2051-MUM-2013-CORRESPONDENCE(3-1-2014).pdf | 2018-08-11 |
| 20 | 2051-MUM-2013-FORM 3 [05-12-2019(online)].pdf | 2019-12-05 |
| 21 | 2051-MUM-2013-CORRESPONDENCE(8-1-2014).pdf | 2018-08-11 |
| 21 | 2051-MUM-2013-OTHERS [24-12-2019(online)].pdf | 2019-12-24 |
| 22 | 2051-MUM-2013-FER_SER_REPLY [24-12-2019(online)].pdf | 2019-12-24 |
| 22 | 2051-MUM-2013-FORM 1(3-1-2014).pdf | 2018-08-11 |
| 23 | 2051-MUM-2013-DRAWING [24-12-2019(online)].pdf | 2019-12-24 |
| 23 | 2051-MUM-2013-FORM 1(8-1-2014).pdf | 2018-08-11 |
| 24 | 2051-MUM-2013-FORM 13(8-1-2014).pdf | 2018-08-11 |
| 24 | 2051-MUM-2013-COMPLETE SPECIFICATION [24-12-2019(online)].pdf | 2019-12-24 |
| 25 | 2051-MUM-2013-form 18.pdf | 2018-08-11 |
| 25 | 2051-MUM-2013-CLAIMS [24-12-2019(online)].pdf | 2019-12-24 |
| 26 | 2051-MUM-2013-FORM 26(27-9-2013).pdf | 2018-08-11 |
| 26 | 2051-MUM-2013-Correspondence to notify the Controller [23-09-2021(online)].pdf | 2021-09-23 |
| 27 | 2051-MUM-2013-FORM-26 [27-09-2021(online)].pdf | 2021-09-27 |
| 27 | 2051-MUM-2013-FORM 3(1-11-2013).pdf | 2018-08-11 |
| 28 | 2051-MUM-2013-US(14)-HearingNotice-(HearingDate-28-09-2021).pdf | 2021-10-03 |
| 28 | 2051-MUM-2013-FORM 5(8-1-2014).pdf | 2018-08-11 |
| 29 | 2051-MUM-2013-Written submissions and relevant documents [11-10-2021(online)].pdf | 2021-10-11 |
| 29 | 2051-MUM-2013-PETITION UNDER RULE-138(3-1-2014).pdf | 2018-08-11 |
| 30 | FORM 5.pdf | 2018-08-11 |
| 30 | 2051-MUM-2013-PatentCertificate04-04-2022.pdf | 2022-04-04 |
| 31 | 2051-MUM-2013-IntimationOfGrant04-04-2022.pdf | 2022-04-04 |
| 31 | SPEC in.pdf | 2018-08-11 |
| 1 | 2051MUM2013_25-06-2019.pdf |