JIT originated in the early 20th century, prosperous in Japan. In the mechanical age of industrial production, it is widely used in manufacturing industries in the industrialized machinery. Undoubtedly, at this stage, JIT management is in the production industry, especially the contribution of manufacturing, and does not move; it enables mechanical production to jump from experienced square management to the quantitative level management phase. The management method undoubtedly occupies a place in the history of human evolution.
Now, in the information age, the production method of the software industry is amazingly similar in the production method of the early 1920s, and is still in the stage of experience. Although, in the process of software development, various methods are endless, but the true quantitative management, the method of systematic design has not appeared yet. Maybe, some people question, now there is CMM, UML and other standards, don't you do it? From the level of quantitative and systematic management, they are indeed standard, but only the standards of software industrial sprouting stages, rather than the management method of software production age.
So, can JIT management can be used in the software development industry? It is also like the role of the mechanical era, is it possible to advance the software industry to a big production era?
According to the inference of the soul historians, we are now in a key crisis, in the stage of the software industry needs quantitative management, JIT management. I have extended the meaning of JIT here, called a comprehensive quantified process management process.
The soul historian stems from a novel, which is quoted and proposed here. I want to remind everyone that my mind has not yet been produced, and its job is the possible evolutionary crisis in each link in the history of human evolution. Prediction and analysis, the calculation speculates the next crisis and provides the corresponding resolution. No country or institution is still working on this aspect, even if there is a simple trial. The reason why these work cannot be performed, only because the information of various resources cannot be quantified, and lack of systematic approach, can only be said, the current human evolution is still in the natural evolutionary stage.
Now let's go back to the topic of the software industry, what is the JIT method in the software industry?
Over the years, software workers have been confused in this fact, why can we help other industries to quantify management, but they still stay in the experience workshop state? Although the software engineering is now initially divided into a series of stages of research, demand analysis, design, implementation, testing, implementation, etc., because there are too many variables, there are always cases of failure or difficulty, or can put budget and progress Controlling successful cases within 50% of the range is difficult. Why is this industry so tolerant?
In the stage of production experience of mechanical chemical industries, the software industry also has to experience: from the stage of the workshop, to the germination stage, to the big production era, enter the life-generating era, and finally enter the next level. The current software industry is in the middle of the germination stage, and there is a power to accelerate its process and promote it. I think it may be a JIT method for the software industry, perhaps other management methods.
First, I introduce two basic principles of software JIT methods: The first principle is that software projects can quantify into multiple stages, that is, multi-channel details; the second principle is that the pre-process must provide the desired to provide the desired. .
In mechanized large production, the pre-step is to provide resources in the form of semi-finished products, and in the software industry, the resource is shown in a variety of information resources provided by: the information resource provided by the pre-process; human resources; front step arrangement New tools or resource allocation; public repository;
The division of the step is a problem that is more difficult to handle. It is recommended to use the reverse push method to determine the resources, resource allocation, and resources required by each process.
Different types of software products require different JIT models, software industry practitioners can construct and evolve the JIT models and examples of them according to the above two basic principles. It should be indicated that the process arrangement of software production is not a pipeline. There is no software JIT model and instance to give the software JIT model and instance, and the evolution of the evolution is to wait for the joint efforts of all software practitioners. In the current era of software industry, software JIT methods can integrate into all aspects of software production. According to software JIT methods, there may be various methods and models in adaptive software production era. However, it is important to indicate that the logo from the Software Production Age is: a large number of software blue-collar workers, like the era of mechanical production.
