Abstract: A method(s) and system(s) of identifying quality requirements for a software product to be developed is disclosed. The method includes receiving input data from a user. The input data is indicative of objectives to be met by the software product being developed. The method further includes mapping the input data with a pre-defined product quality requirement model (PQRM) (100). The PQRM (100) is retrieved from a database (208) and includes a taxonomy tree configured to define a plurality of quality characteristics (QCs), a plurality of sub-QCs, a plurality of quality objectives (QOs), and a plurality of quality requirements (QRs) for the software product. Further, the method includes identifying at least one QR from the plurality of QRs applicable for the software product. The identification is based on the input data. The method also includes generating a product requirement report (PRR) for the software product based on the identification.
CLIAMS:1. A method of identifying quality requirements of a software product to be developed, the method comprising: receiving input data from a user, wherein the input data is indicative of objectives to be met by the software product being developed; mapping the input data with a pre-defined product quality requirement model (PQRM) (100), wherein the PQRM (100) is retrieved from a database (208) and comprises of a taxonomy tree configured to define a plurality of quality characteristics (QCs), a plurality of sub-QCs, a plurality of quality objectives (QOs), and a plurality of quality requirements (QRs) for the software product; identifying at least one QR from the plurality of QRs applicable for the software product, wherein the identification is based on the input data; and
generating a product requirement report (PRR) for the software product based on the identification.
2. The method as claimed in claim 1, wherein the taxonomy tree of the PQRM (100) comprises: a primary level (102) containing the plurality of QCs configured to define attributes in the software product to be developed; a secondary level (104) configured to define the plurality of sub-QCs for each QC of the primary level (102); and
a tertiary level (106) configured to identify the plurality of QOs based on each of the sub-QC of the secondary level (104).
3. The method as claimed in claim 1, wherein the identifying comprises: selecting at least one QC from the plurality of QCs for the software product, wherein the selection is based on the input data; determining at least one sub-QC from the plurality of sub-QCs for the at least one selected QC; and
identifying at least one QO from the plurality of QOs, wherein the identification is based on the determination of the at least one sub-QC.
4. The method as claimed in claim 1 further comprising modifying the at least one identified QR based on the input data specific to the software product.
5. The method as claimed in claim 1 further comprising identifying the quality requirements defined for an existing software product.
6. The method as claimed in claim 5 further comprising comparing the identified quality requirements of the existing software product with the quality requirements in the pre-defined PQRM (100).
7. The method as claimed in claim 6 further comprising identifying gaps in the quality requirements of the existing software product based on the comparison.
8. The method as claimed in claim 7 further comprising generating a gap analysis report for the existing software product based on the identification.
9. A requirement identification system (202) comprising:
a processor (212); an analysis module (220) coupled to the processor (212), the analysis module (220) configured to,
receive input data from a user, wherein the input data is associated with development of a software product; retrieve a pre-defined product quality requirement model (PQRM) (100) from a database (208), wherein the PQRM (100) comprises of a taxonomy tree configured to define a plurality of quality characteristics (QCs), a plurality of sub-QCs, a plurality of quality objectives (QOs), and a plurality of quality requirements (QRs) for the software product; map the input data with the pre-defined PQRM (100); and
identify at least one QR from the plurality of QRs applicable for the software product; and
a generation module (222) coupled to the processor (212), the generation module (222) configured to generate a product requirement report (PRR) for the software product based on the at least one determined QR.
10. The requirement identification system (202) as claimed in claim 9, wherein the analysis module (220) is further configured to,
select at least one QC from the plurality of QCs for the software product, wherein the selection is based on the input data; determine at least one sub-QC from the plurality of sub-QCs for the at least one selected QC; identify at least one QO from the plurality of QOs for eliciting the QRs of the software product, wherein the identification is based on the at least one determined sub-QC.
11. The requirement identification system (202) as claimed in claim 9, wherein the analysis module (220) is further configured to compare the quality requirements of an existing software product with the quality requirements of the pre-defined PQRM (100).
12. The requirement identification system (202) as claimed in claim 9, wherein the analysis module (220) is further configured to modify the at least one identified QR based on the input data specific to the software product.
13. A non-transitory computer-readable medium having embodied thereon a computer program for executing a method for identifying quality requirements of a software product, the method comprising: receiving input data from a user, wherein the input data is indicative of objectives to be met by the software product being developed; mapping the input data with a pre-defined product quality requirement model (PQRM) (100), wherein the PQRM (100) is retrieved from a database (208) and comprises of a taxonomy tree configured to define a plurality of quality characteristics (QCs), a plurality of sub-QCs, and a plurality of quality objectives (QOs) for the software product; identifying at least one QO from the plurality of QOs applicable for the software product, wherein the identification is based on the input data; and
generating a product requirement report (PRR) for the software product based on the identification.
,TagSPECI:As Attached
| # | Name | Date |
|---|---|---|
| 1 | 2242-MUM-2013-FORM 3(20-12-2013).pdf | 2013-12-20 |
| 2 | 2242-MUM-2013-CORRESPONDENCE(20-12-2013).pdf | 2013-12-20 |
| 3 | SPEC IN.pdf | 2018-08-11 |
| 4 | FORM 5.pdf | 2018-08-11 |
| 5 | FORM 3.pdf | 2018-08-11 |
| 6 | FIGURES IN.pdf | 2018-08-11 |
| 7 | ABSTRACT.jpg | 2018-08-11 |
| 8 | 2242-MUM-2013-FORM 26(27-9-2013).pdf | 2018-08-11 |
| 9 | 2242-MUM-2013-FORM 18.pdf | 2018-08-11 |
| 10 | 2242-MUM-2013-FORM 1(11-7-2013).pdf | 2018-08-11 |
| 11 | 2242-MUM-2013-CORRESPONDENCE(27-9-2013).pdf | 2018-08-11 |
| 12 | 2242-MUM-2013-CORRESPONDENCE(22-8-2013).pdf | 2018-08-11 |
| 13 | 2242-MUM-2013-CORRESPONDENCE(11-7-2013).pdf | 2018-08-11 |
| 14 | 2242-MUM-2013-FER.pdf | 2019-05-31 |
| 15 | 2242-MUM-2013-FORM 3 [06-11-2019(online)].pdf | 2019-11-06 |
| 16 | 2242-MUM-2013-Information under section 8(2) (MANDATORY) [11-11-2019(online)].pdf | 2019-11-11 |
| 17 | 2242-MUM-2013-OTHERS [29-11-2019(online)].pdf | 2019-11-29 |
| 18 | 2242-MUM-2013-FER_SER_REPLY [29-11-2019(online)].pdf | 2019-11-29 |
| 19 | 2242-MUM-2013-COMPLETE SPECIFICATION [29-11-2019(online)].pdf | 2019-11-29 |
| 20 | 2242-MUM-2013-CLAIMS [29-11-2019(online)].pdf | 2019-11-29 |
| 21 | 2242-MUM-2013-US(14)-HearingNotice-(HearingDate-17-11-2023).pdf | 2023-10-20 |
| 22 | 2242-MUM-2013-Correspondence to notify the Controller [08-11-2023(online)].pdf | 2023-11-08 |
| 23 | 2242-MUM-2013-FORM-26 [16-11-2023(online)].pdf | 2023-11-16 |
| 24 | 2242-MUM-2013-FORM 3 [30-11-2023(online)].pdf | 2023-11-30 |
| 25 | 2242-MUM-2013-Written submissions and relevant documents [01-12-2023(online)].pdf | 2023-12-01 |
| 26 | 2242-MUM-2013-PatentCertificate15-03-2024.pdf | 2024-03-15 |
| 27 | 2242-MUM-2013-IntimationOfGrant15-03-2024.pdf | 2024-03-15 |
| 1 | Searchstrategy_2242MUM_2013_30-05-2019.pdf |