CLIAMS:WE CLAIM
1. A method for determining a risk associated with a release of a software product, the method comprising:
gathering, via a processor, a plurality of parameters related to the software product;
determining , via the processor, a plurality of complexity levels based on the plurality of parameters;
determining, via the processor, a stability of the software product based on a stability of a baseline software product;
determining, via the processor, 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, via the processor, the risk associated with the release of the software product based on the overall complexity level.
2. The method of claim 1, wherein the software product comprises one or more projects and each of the one or more projects comprises one or more modules.
3. The method of claim 1, wherein gathering comprises gathering, for each project, the plurality of parameters required for determining the risk from at least one of a test management system, a software lifecycle management system, a requirement system, and a user.
4. The method of claim 1, wherein the plurality of parameters comprises a plurality of parameters for each project, and wherein the plurality of parameters for each project comprises a requirement, a complexity value associated with the requirement, and at least one of a module, a complexity value associated with the module, a test case, a complexity value associated with the test case, a complexity value associated with the project, and a defect.
5. The method of claim 1, wherein gathering comprises gathering a plurality of parameters related to the stability of the baseline software product.
6. The method of claim 1, wherein determining the plurality of complexity level comprises determining, for each project, a complexity level for at least one of the plurality of parameters based on one or more complexities associated with the corresponding parameter.
7. The method of claim 1, wherein determining the stability comprises determining, for each project, a stability based on a logic of a plurality of previous releases to a current release.
8. The method of claim 1, wherein determining the overall complexity level comprises determining, for each project, an overall complexity by correlating the plurality of complexity levels and the stability of the software product.
9. The method of claim 1, wherein determining the risk comprises determining the risk associated with the release based on the overall complexity and a total number of project within the software product.
10. The method of claim 1, further comprising presenting the risk associated with the release to a user.
11. A system for determining a risk associated with a release of a software product, 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:
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.
12. The system of claim 1, wherein the software product comprises one or more projects, wherein the plurality of parameters comprises a plurality of parameters for each of the one or more projects, and wherein the plurality of parameters for each project comprises a requirement, a complexity value associated with the requirement, and at least one of a module, a complexity value associated with the module, a test case, a complexity value associated with the test case, a complexity value associated with the project, and a defect..
13. The system of claim 11, wherein gathering comprises gathering, for each project, the plurality of parameters required for determining the risk from at least one of a test management system, a software lifecycle management system, a requirement system, and a user.
14. The system of claim 11, wherein gathering comprises gathering a plurality of parameters related to the baseline software product.
15. The system of claim 11, wherein determining the plurality of complexity level comprises determining, for each project, a complexity level for at least one of the plurality of parameters based on one or more complexities associated with the corresponding parameter.
16. The system of claim 11, wherein determining the stability comprises determining, for each project, a stability based on a logic of a plurality of previous releases to a current release.
17. The system of claim 11, wherein determining the overall complexity level comprises determining, for each project, an overall complexity by correlating the plurality of complexity levels and the stability of the software product.
18. The system of claim 11, wherein determining the risk comprises determining the risk associated with the release based on the overall complexity and a total number of project within the software product.
19. The system of claim 11, wherein the operations further comprise presenting the risk associated with the release to a user.
20. A non-transitory computer-readable medium storing computer-executable instructions for:
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.

Dated this 22nd day of April, 2015
Swetha S.N
Of K&S Partners
Agent for the Applicant
,TagSPECI:TECHNICAL FIELD
This disclosure relates generally to software release management, and more particularly to a system and method for optimizing risk during a software release.