Abstract: The present disclosure relates to a method for enhancing quality of requirements for an application development. The method comprises retrieving expertise information of each user of groups involved in identifying requirements, domain knowledge of each user, information on number of defects associated with requirements and information of requirements for application development from sources. Then, skill score of the groups is computed using expertise information and domain knowledge of each user of corresponding groups. Solidity score of each of requirements is determined using information of requirements and predetermined threshold solidity score. Weightage score of each of requirements is computed based on information of requirements and information on number of defects. The, using skill score of groups, solidity score of each of requirements and weightage score, strength score of each of requirements is computed for enhancing quality of requirements.

Abstract: This disclosure relates generally to software release management, and more particularly to a system and method for optimizing risk during a software release. In one embodiment, a method is provided for determining a risk associated with a release of a software product. The method comprises gathering a plurality of parameters related to the software product, determining a plurality of complexity levels based on the plurality of parameters, determining a stability of the software product based on a stability of a baseline software product, determining an overall complexity level of the release of the software product based on the plurality of complexity levels and the stability of the software product, and determining the risk associated with the release of the software product based on the overall complexity level.

Abstract: A system and method for optimizing risk during software production release are disclosed. The method may involve receiving, one or more project requirements associated with the software project and one or more project defects associated with the software project; identifying, one or more critical project requirements and one or more critical project defects from the one or more project requirements and the one or more project defects; ascertaining, a requirement density for the software project based on the one or more critical project requirements and the one or more project requirements; ascertaining, a defect density based on the one or more critical project defects and the one or more project defects; and determining a cumulative risk score for the software project using the requirement density and the defect density.