DESC:FIELD OF THE INVENTION
The present embodiment relates to a system and method of determining price for software generation, and more particularly relates to the computer-implemented and automated system and method for estimating the cost of software.
BACKGROUND OF THE INVENTION
In today’s world, software is needed in almost in almost every business and industry ranging from local retailers to hospitals and multi-national companies. Business enterprises rely on increasingly sophisticated software to manage their internal operation and provide goods and services to their clients and customers.
Recently, a lot of systems are available in the market for the automatic generation of the software. The available systems does not allow the automatic estimation of the cost, rather the price is calculated manually. This results in increased risk of manual errors such as underestimating or overestimating the price. The other disadvantages associated with the manual price estimation includes human bias, risk of missing any component, errors in determining the complexity of the software resulting in wrong price estimation. Also, this may require previous exposure to a similar kind of project to estimate the project case correctly.
There are a few systems that automatically inform the cost to the user, however, these systems do not take into account the size and complexity of each projects. These systems have a fixed cost and thus results in wrong price estimation.
Therefore, there is a need of the automated system and method for determining the price of the software generation based on the size and complexity of the project.
OBJECTIVES OF THE INVENTION
An object of the present embodiment is to provide general and instantaneous price estimation for any kind of software project.
Another object of the present embodiment is to provide correct price estimation based on the size and complexity of the software project.
Yet another object of the present embodiment is to provide uniform and standardized pricing across teams, departments, sites and organizations.
SUMMARY OF THE INVENTION
In an aspect, a computer-implemented method (100) for price estimation of software project is provided. The method includes the following steps: 1) inputting/uploading a document, wherein the document is in the format like Scope of Work (SOW), Request For Proposal (RFP), Business Requirements Specification (BRS), design document, engineering document and Requirements document; 2) identifying sentences and paragraphs in the readable format from the uploaded document, wherein the sentences and paragraphs are identified using Artificial Intelligence (AI) based Natural Language Processing (NLP) system; 3) identifying a plurality of features and categorizing into a plurality of classes, wherein the category of the class is the factor in determining the cost of the software project; and 4) determining the cost based on the complexity of the software project, wherein the price of different elements and software components may be listed by a third party price system.
The preceding is a simplified summary to provide an understanding of some aspects of embodiments of the present invention. This summary is neither an extensive nor exhaustive overview of the present invention and its various embodiments. The summary presents selected concepts of the embodiments of the present invention in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other embodiments of the present invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 illustrates a computer-implemented method (100) for price estimation of software project, according to an embodiment herein.
To facilitate understanding, like reference numerals have been used, where possible, to designate like elements common to the figures.
DETAILED DESCRIPTION
As used throughout this application, the word "may" is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including but not limited to.
The phrases “at least one”, “one or more”, and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C” and “A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
The term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more” and “at least one” can be used interchangeably herein. It is also to be noted that the terms “comprising”, “including”, and “having” can be used interchangeably.
The present embodiment provides the computer-implemented method (100) for price estimation of software project. In an embodiment, the computer-implemented method (100) is automated and helps in determining the cost estimation of the software based on the size and complexity of the project. The computer-implemented method (100) does not need any manual involvement from the technical team or cost estimator consultants. The computer-implemented method (100) includes the following steps:
At step 102, a user is asked to input/upload a document. In an embodiment, the user is asked to upload the input document based on his/her needs/requirements for the software development. The input document is uploaded in the format such as, but not limited to, Scope of Work (SOW), Request For Proposal (RFP), Business Requirements Specification (BRS), design document, engineering document and Requirements document.
In an embodiment, the uploaded document may be in various file formats such as, but not limited to, PDF, word, excel, RTF, html and image. In an embodiment, the uploaded document can be edited. In another embodiment, the uploaded document cannot be edited. In an embodiment, the uploaded document may also contain non-textual data such as, but not limited to, tables, drawings, diagrams, pictures and other forms of multi-media.
In an embodiment, the uploaded document is converted into a readable format. In an embodiment, the uploaded document is converted through Artificial Intelligence (AI) and other file conversion techniques into a readable format.
At step 104, sentences and paragraphs are identified in the readable format of the uploaded document. A Meaningful Sentence Identifier (MSI) unit analyses the document and converts into meaningful sentences and/or paragraphs and/or blocks. In an embodiment, MSI uses Artificial Intelligence (AI) based Natural Language Processing (NLP) system for identifying the meaningful sentences and/or paragraphs and/or blocks. In an embodiment, the meaningful sentences and/or paragraphs and/or blocks are identified to ensure that the overall meaning is not lost from the uploaded document.
At step 106, a plurality of features are identified from the MSI file and categorized into a plurality of classes. In an embodiment, the feature identification and categorization is done by a Feature Identifier and Categorizer (FIC) unit. Table 1 illustrates the plurality of classes according to the present embodiment. In an embodiment, the category of the class is the first factor in determining the cost of the software project.
FEATURE CATEGORIZATION
1. Basic Features - Add, Edit, Delete, Import, Export, Print, View
2. Workflow Features - Dynamic process features
3. Performance Features - Within 2 seconds app response, scalability to 10k concurrent connections, etc
4. Optimization Features - Adaptive features e.g. on handheld, mobile, 128kbps network, etc
5. Integration Features - Database to be Oracle, Integration with SAP, Gmail
6. Information Features - Reports, Dashboards, Website (help/public info access)
7. Privileges Features - Roles, Authority, Access Control, etc
8. Security Features - Encryption, Password protection, etc
9. Business Continuity Features - Backup, Archival, Data Storage for 5 years, etc
10. UI Features - Look, Color, Feel, Responsiveness
11. Infrastructure Features - Servers, PCs, etc Hardware to be provided along with the application
Table 1
The second factor in determining the cost of the software is the complexity of the project. In an embodiment, the complexity of the feature is identified by the type and number of domain elements. Table 2 illustrates the domain elements of the present embodiment.
NORMALIZED DOMAIN ELEMENTS
1. Attribute
2. Value Object
3. Entity
4. Aggregate
5. Relationship
6. Process
7. Event
8. Payload
9. Rule
10. Condition
11. Task
12. Input
13. Action
14. Output
15. API
16. Report
17. Form
18. Dashboard
19. Website
20. Role
21. Role-Process-Map
Table 2
The FIC unit generates feature list by category, type and number of domain elements.
At step 108, cost per category and per element is listed by a Per Unit Price Descriptor (PUPD) unit. In an embodiment, the price of different elements and software components may be listed manually. In another embodiment, the price of different elements and software components may be listed by a third party price system.
The Price Estimator unit further calculates the total cost by using simple arithmetic calculation. The PE unit calculates the total cost based on the feature category, domain elements type, domain element quantity, domain element combination and overheads, margins, currency conversions, discounts and offers.
The present method helps in accurately determining the cost of the software project.
The foregoing discussion of the present invention has been presented for purposes of illustration and description. It is not intended to limit the present invention to the form or forms disclosed herein. In the foregoing Detailed Description, for example, various features of the present invention are grouped together in one or more embodiments, configurations, or aspects for the purpose of streamlining the disclosure. The features of the embodiments, configurations, or aspects may be combined in alternate embodiments, configurations, or aspects other than those discussed above. This method of disclosure is not to be interpreted as reflecting an intention the present invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment, configuration, or aspect. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of the present invention.
Moreover, though the description of the present invention has included description of one or more embodiments, configurations, or aspects and certain variations and modifications, other variations, combinations, and modifications are within the scope of the present invention, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments, configurations, or aspects to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.

,CLAIMS:WE CLAIM:
1. A computer-implemented method (100) for price estimation of software project, the method includes:
- inputting/uploading a document, wherein the document is in the format like Scope of Work (SOW), Request For Proposal (RFP), Business Requirements Specification (BRS), design document, engineering document and Requirements document;
- identifying sentences and paragraphs in the readable format from the uploaded document, wherein the sentences and paragraphs are identified using Artificial Intelligence (AI) based Natural Language Processing (NLP) system;
- identifying a plurality of features and categorizing into a plurality of classes, wherein the category of the class is the factor in determining the cost of the software project; and
- determining the cost based on the complexity of the software project, wherein the price of different elements and software components may be listed by a third party price system.
2. The computer-implemented method (100) as claimed in claim 1, wherein the uploaded document is converted through Artificial Intelligence (AI) and other file conversion techniques into a readable format.
3. The computer-implemented method (100) as claimed in claim 1, wherein the complexity of the feature is identified by the type and number of domain elements.
4. The computer-implemented method (100) as claimed in claim 1, wherein the total cost is based on the feature category, domain elements type, domain element quantity, domain element combination and overheads, margins, currency conversions, discounts and offers.