Home Food Production Machines Other typical software life cycle models of the software life cycle model

Other typical software life cycle models of the software life cycle model

by admin

Other typical life cycle models include iteration model, rapid prototyping model, V model and W model. The iterative model is a cycle model recommended by RUP (Rational Unified Process). In RUP, iteration is defined as: iteration includes all development activities that produce a product release (stable and executable product version) and all other peripheral elements necessary to use the release. Therefore, to some extent, the development iteration is a complete process that goes through all work processes: (at least) requirements workflow, analysis and design workflow, implementation workflow and testing workflow. In essence, it is similar to a small waterfall project. RUP believes that all phases (requirements and others) can be subdivided into iterations. Each iteration will produce a releasable product, which is a subset of the final product. The idea of iteration is shown in the figure. The biggest difference between iteration and waterfall is the exposure time of risk. “Any project will involve certain risks. If you can ensure that risks are avoided as early as possible in the life cycle, your plan will be more accurate. There are many risks that will not be discovered until you are ready to integrate the system. No matter how experienced the development team is, it is impossible to predict all risks.” Because of the characteristics of the waterfall model (the document is the main body), many problems will be exposed in the end, To solve these problems, the risks are enormous. In the iterative lifecycle, you need to select new incremental content to be developed in the iteration according to the main risk list. At the end of each iteration, a tested executable file will be generated to verify whether the target risk has been reduced. Rapid Prototype model is functionally equivalent to a subset of products. Note that this is about function. The disadvantage of waterfall model is that it is not intuitive enough. Rapid prototyping solves this problem. Generally speaking, according to the needs of customers, we can solve the most urgent needs of users in a short time and complete a product that can be demonstrated. This product only implements some functions (the most important). Its most important purpose is to determine the real needs of users. In my experience, this method is very effective. Users who have no concept of computers before often speak eloquently in front of your prototype, and some views surprise you. After getting the user’s requirements, the prototype will be abandoned. Because the prototype development is very fast, the design aspect is hardly considered. If the prototype is retained, it will pay a great price in the subsequent development. As for the retention of prototypes, there is also an incremental model that does this, but this model is not accepted by everyone and is beyond our discussion. The above models all have their own unique ideas. In fact, few software organizations use a standard model. There is a big difference between model and utility. The development of software life cycle model actually reflects the development of software engineering theory. At the earliest time, the life cycle of software was in disorder. In order to control the software development process, some people strictly divide the software development into several different stages, and add strict review between stages. This is the origin of the waterfall model. The waterfall model reflects a hope for software process: strict control and quality assurance. Unfortunately, reality is often cruel. The waterfall model can not meet this high requirement at all, because the software process is often difficult to predict. Instead, it leads to other negative effects, such as a large number of documents and cumbersome approval. Therefore, people began to try to use other methods to improve or replace the waterfall method. For example, subdivide the process to increase the predictability of the process.

related posts

Leave a Comment