CLIAMS:1. A method for software project estimation, the method comprising:
receiving, a value corresponding to at least one decision parameter related to a software project from a user, wherein the at least one decision parameter is one of a project type, a technology, a software development life cycle (SDLC) type and a stage of the software project;
mapping a value corresponding to a decision parameter from amongst the at least one decision parameter with one or more techniques of estimating the software project in a decision matrix, wherein the decision matrix comprises a plurality of techniques associated with each of a plurality of estimation parameters comprising a size parameter indicative of size of the software project, an effort parameter indicative of efforts involved in the software project, a cost parameter indicative of cost of the software project, and a schedule parameter indicative of schedule of the software project;
shortlisting one or more techniques amongst the plurality of techniques for each of the estimation parameters based on tha mapping;
evaluating a success rating factor corresponding to each of the shortlisted techniques based on historical data (112) to identify a primary set of techniques; and
determining, based on an interoperability factor, compatibility of the primary set of techniques to identify at least one secondary set of techniques from the primary set of techniques for the software project, wherein the secondary set of techniques provides an optimum estimate of the software project.
2. The method as claimed in claim 1, wherein the method further comprises determining the interoperability factor based on determining a valid combination of the primary set of techniques at least related to the size parameter and the effort parameter from a validation table.
3. The method as claimed in claim 1, wherein evaluating the success rating factor comprises determining weightages associated with each of a plurality of attributes of the success rating factor, the plurality of attributes comprises at least a project effort variance, a project size variance, number of data points, a user feedback, and a client acceptability factor.
4. The method as claimed in claim 1, wherein the historical data (112) comprises at least an actual effort data and an estimated effort data related to the software project.
5. The method as claimed in claim 1, wherein the method further comprises:
receiving feedback of the software project from the user, wherein the feedback comprises at least actual project data related to the software project; and
updating the historical data (112) stored in a database (110) with the feedback.
6. A software estimation system (102) comprising:
a processor (202);
a mapping module (212) coupled to the processor (202), to:
receive values corresponding to decision parameters related to a software project from a user, wherein the decision parameters include at least a project type, a technology, a software development life cycle (SDLC) type and a stage of the software project;
map the values with a plurality of techniques of estimating the software project, wherein the plurality of techniques include techniques for estimating size of the software project, techniques for estimating efforts involved in the software project, techniques for estimating cost of the software project, and techniques for estimating schedule of the software project; and
shortlist, based on the mapping, one or more techniques amongst the plurality of techniques for estimating size, estimating efforts, estimating cost and estimating schedule of the software project;
an analysis module (108) coupled to the processor (202), to:
evaluate a success rating factor corresponding to each of the shortlisted techniques based on historical data (112) stored in a database (110) coupled to the software estimation system (102) to identify a primary set of techniques; and
determine, based on an interoperability factor, compatibility of the primary set of techniques to identify at least one secondary set of techniques from the primary set of techniques for the software project, wherein the secondary set of techniques provides an optimum estimate of the software project.
7. The software estimation system (102) as claimed in claim 6, wherein the analysis module (108) evaluates the success rating factor based on determining weight ages associated with each of a plurality of attributes of the success rating factor, the plurality of attributes comprises at least a project effort variance, a project size variance, number of data points, a user feedback, and a client acceptability factor.
8. The software estimation system (102) as claimed in claim 6, wherein the analysis module (108) determines the interoperability factor based on determining a valid combination of the primary set of techniques at least related to the size parameter and the effort parameter from a validation table.
9. The software estimation system (102) as claimed in claim 6, wherein the software estimation system (102) further comprises a feedback module (214) to:
receive feedback of the software project from the user, wherein the feedback comprises at least actual project data related to the software project and
update the historical data (112) stored in the database (110) with the feedback.
10. The software estimation system (102) as claimed in claim 9, wherein the feedback module (214) receives the feedback from a project management system.
11. A non-transitory computer-readable medium having embodied thereon a computer program for executing a method comprising:
receiving, a value corresponding to at least one decision parameter related to a software project from a user, wherein the at least one decision parameter is one of a project type, a technology, a software development life cycle (SDLC) type and a stage of the software project;
mapping a value corresponding to a decision parameter from amongst the at least one decision parameter with one or more techniques of estimating the software project in a decision matrix, wherein the decision matrix comprises a plurality of techniques associated with each of a plurality of estimation parameters comprising a size parameter indicative of size of the software project, an effort indicative of efforts involved in the software project, a cost parameter indicative of cost of the software project, and a schedule parameter indicative of schedule of the software project;
shortlisting one or more techniques amongst the plurality of techniques for each of the estimation parameters based on the mapping;
evaluating a success rating factor corresponding to each of the shortlisted techniques based on historical data (112) to identify a primary set of techniques; and
determining, based on an interoperability factor, compatibility of the primary set of techniques to identify at least one secondary set of techniques from the primary set of techniques for the software project, wherein the secondary set of techniques provides an optimum estimate of the software project. ,TagSPECI:As Attached