Software Development Method Zoo

Here we summarize the software development methods since 1970. Some Characteristics of these development methods are similar to some animals in the zoo !, Some of these development methods are similar to some animals in the zoo!

Waterfall-1970

Waterfall Model is a continuous software development process ......, It enables development to gradually develop from the demand analysis, design, implementation (verification), integration, integration and maintenance stages, just like waterfall flow.

You cannot stop the waterfall model. If your project needs to change ...... It means you will be in trouble.
There is no doubt that the waterfall model is the favorite method of scuffia.

V-model-post-1980s

The V model is a software development process that extends the waterfall model. It does not adopt a linear downward movement, but changes the process after the completion of the encoding phase, forming a typical V-shaped shape. The V-model indicates the relationship between each stage of the software development lifecycle and related test stages.

This is a rigid "zombie" model, but many ISO and CMM enthusiasts still think that the V-type model is cool. The V-type model provides a false security solution in terms of management. This is tarelli's favorite.

Cowboy encoding-Wild West

Cowboy encoding is a development process that describes software development. It includes project progress control, algorithms, tools, and coding style.

Ideally, it is my favorite model. When I create my own company, I believe I will officially use cowboy coding.

Scrum-Early 1990s

Scrum is an iterative and incremental process, applicable to any product development and work management. Scrum is a process framework that includes a set of practices and predefined roles. The main role is scrummaster, which maintains processes and other jobs, similar to the project manager, as well as the developer team.

It was born in the early 1990s s and has been widely used since the 10th. This is just like demonstrating the use of scrummaster on Agile Software Development farms to coordinate the relationship between chickens and pigs. So you need to know all the work done by pig.

Iconix

Iconix is a software development method, which is early in Rational Unified Process (RUP), eXtreme Programming (XP) and agile software development. For example, the iconix process is case-driven by UML, but it is lighter than the RUP process. Unlike XP and agile approaches, iconix provides sufficient requirements and design documents, but does not analyze fault documents. This iconix process only uses four UML-based charts in four steps, and uses case text work code in turn. It is designed for the use of low-end analysis. The whole process makes the design, testing and evaluation of user cases easier. The iconix process is a practical, efficient, case-driven UML object modeling method.

Iconix basically combines agile methods with low-end designs. I am currently using this method.

XP eXtreme Programming

Extreme Programming is a software engineering method that develops a set of daily practice methods to reflect and encourage Special XP values.
Supporters believe that these traditional software engineering practices adopt the so-called "extreme" level, making it easier than traditional development methods, XP can better adapt to customer needs ("agile"), while creating better software quality.

Extreme programmers and agile methods generally regard changing needs as a natural, inevitable, and ideal aspect of software development projects. They believe that, adapting to changing needs at any time in a project is a more realistic and better way, rather than trying to determine all the needs at the beginning of a project and make efforts to control the changes.

XP is important to speed, and we like speed if there is no documentation. The biggest drawback of this approach is the change in functionality and scope, which is mainly caused by the lack of sustainability references. XP is light
A method that affects the development of data. The lightweight development method is relative to the traditional weight development method. Simply put, the importance of "volume" refers to the amount of programs used for software process management and control.
The number of documents.