Describes several modes of software development and describes the impact of each mode on software testing.

• Great Development Mode

1. The biggest advantage of the great development model is that the idea is simple and often it isProgramEmployee's "Sudden whimsy ".
2. Software testing in the great development mode is usually carried out after the development task is completed. Testing is sometimes easier and sometimes very difficult, because after the software has formed a product, it is no longer possible to fix the problem.

 

• Change Mode while writing

1. The development mode of writing and modifying is an improvement of the great development mode;
2. Software testers In the write-and-Modify-development project team should be clear that they will join the programmers in a development process that may be cyclical for a long time. Generally, new software versions are constantly being generated, and the old software version may not be completed yet. The new version may also contain new or modified software features.

 

• Waterfall Development Model

1. This model is applicable to projects that are relatively stable and easy to understand;
2. Advantages of the waterfall development model: 1) easy to understand 2) Research and development phases 3) emphasize early planning and demand surveys 4) determine when products can be delivered and when to conduct reviews and tests;
3. Disadvantages of the waterfall development model: 1) the demand investigation and analysis are conducted only once and cannot adapt to the changes in the demand. 2) the sequential development process, so that the development experience and lessons cannot be fed back to the development of the project. 3) it cannot reflect the repeatability and iteration of the software development process. 4) it does not include any types of risk assessment. 5) problems in development can only be revealed after development, therefore, the opportunity for early correction is lost;

 

• Quick prototyping

1. The purpose of the Application rapid model development model is to determine the real needs of users, so that users can be more specific to their needs in front of the prototype. The prototype will be discarded after the user's explicit requirements are obtained.

 

• Spiral Development Mode

1. The spiral development mode is a combination of waterfall development mode and rapid prototype development mode;
2. The main idea of the spiral development model is that you do not need to define all the details at the beginning, but start from a small scale, define important functions, implement as much as possible, then detect risks, and develop risk control plans, accept the customer feedback, go to the next stage, repeat the above process, and then repeat the next spiral to determine whether the next step will continue and determine the final software product acquisition.
3. Due to the introduction of very high-level risk identification, risk analysis and risk control, the spiral development model puts forward high requirements on the skill level of risk management, it also requires a large amount of personnel, capital, and time investment.

 

• RUP Model

1. It brings together multiple management experiences in modern software development and provides flexible forms to meet the needs of various projects and organizations. As a business model, it has very detailed process guidance and templates.
2. Because the model is complex, it takes a lot of money to master the model. Especially for project managers.

 

• IPD Process Development Mode

1. The IPD Process is a staged model with the Shadow of the waterfall model,
2. This model increases the overall product quality and obtains market share through process costs. Because the process does not define a mechanism to roll back the process, this process is not suitable for projects with frequent changes in requirements. It is not very suitable for small projects.

 

• Agile Development Mode

1. Agile Methods integrate the development and testing processes.
2. In Agile Methods, testing plays the same role in many different methods, while different test types play different roles.
3. According to the agile principle, make sure that you do not use manual testing for automated testing. At the same time, make sure that the content suitable for manual testing is not costly for automated testing.
4. It is not because automation testing cannot be implemented in some aspects.
5. How can we use manual and automated testing? How to design test cases? Challenges for agile testing.

 

In short, different process models are suitable for different types of software projects. Different process models have a direct impact on software testing.