To be honest, I have just graduated for more than 1 year software engineer (I hope I really have a qualification to call yourself), talk about software economics this topic, purely personal interest, and an experience report of reading books. To talk about the economy, you must first clear what is the input is, the number of parameters, and thinking about the core point of the problem. Software economics generally have five parameters, which are scale, process, personnel, environment and quality. Each of these five points is a discipline, but these five points are absolutely not to talk, this is the charm of the project, he is always a whole, if you cut it, even if you invest more It is not necessary to see its economic effect. The simplest example, the software project is a typical scale uneconomical, then a project is not an investment person, the higher the output, the faster the progress. The economic effects brought are definitely a reaction. It is not economical, and people in software engineering, the status of software economics, I personally feel the highest, of course, the premise is the process, etc. can be pulled. Usually, software companies rarely assess costs in the project level, the problem is that the office, venue, computer and other expenses are rarely reduced to the project, and of course it is not necessary to enclose the development. Then the most important thing in the project is the salary of personnel. The more natural people, the higher this cost. To be honest, the general company is not so considering, is it rare? Money is a JIN. I think the most economical place is to increase the cost of communication. A software company is mature, and CMM is not low, not to mention the 10-level communication cost, not to mention the general company, the development is not standardized, all said analysis design, in fact A code begins to be in the sky. Especially in the later stage of the project, what is the problem, the project is postponed, and the person should be hop, and the performance is not too close. . . The focus is burned, and this time is the first reaction, but it is over. The new people have two eyes and black. I don't know, I don't know if I don't understand, the analysis can't find the direction, the design does not know how to unify, the code does not know the standard, find someone? Others don't care, and the results are written. As a result, Polymophism is Runtime. So humanity is the biggest risk in the project. The stability of the personnel, the high-grade of the personnel is to make every manager's headache, everyone has their own ideas to deal with this. I personally observe, I feel most of the personal feelings to make up for work. thing. No one wants to quantify the project, and indeed hard work in this direction, but most of them are doing from the project itself, because they know that the resources are too complicated, they will not be judged, even if they are not good. Let him reduce the efficiency, so manage the good people tightly.
