Node A mainly defines what customers need to do;
Node B splits the requirements into demand points according to modules;
Node C is to judge how many people and how many days each function point needs to be completed according to the development strength and past experience of the enterprise (this point needs to be evaluated by senior sales manager or project manager);
Node D summarizes the owner's man-days and price of the project, which is not a simple addition, because the man-days obtained in the previous steps are only the workload of the development part, but software development also includes demand research, system design, system testing, UAT, online and operation and maintenance. , generally calculated according to a certain coefficient;
Node E corrects the final price by considering commercial rather than technical factors. For example, if Party A is a large enterprise, the first cooperation loss may be advanced. For example, if Party A is not short of money, it can moderately increase the quotation to prevent subsequent demand changes.
In order to let you have a clear understanding, I copied a copy of the evaluation template that I came into contact with at work (only at node D) for your reference:
Software development cost estimation model
The above is one of the software development cost estimation methods that I borrowed from Zhihu. There are other methods, such as finding quotations from different manufacturers with the same demand, and knowing the approximate cost by looking at the distribution range of quotations. In addition, for senior project managers or developers, it can also be estimated by feeling ... and others welcome other colleagues to express their opinions actively. After all, it is very necessary to estimate the cost of a software project with the help of scientific evaluation processes, tools and experience, so as to better ensure the profitability of the project.