The impact of development mode on testing

The influence of several modes of software development on software testing:

● Big stick development mode

1. The biggest advantage of the big stick development model is that the idea is simple, and it may often be the programmer's "whimsical idea".

2. The software testing of the big stick development mode is usually carried out after the development task is completed. The testing work is sometimes easy and sometimes very difficult. This is because after the software has been formed into a product, it has beenExisting problems can no longer be fixed.

● Change mode while writing

1. The development mode of writing and changing is an improvement to the big stick development mode;

2. Software testers who are in the project team that is writing and developing should be clear that they will be caught in a development process that may be repeated for a long time with the programmer.Usually, new software versions are continuously produced, while the work of the old software version may not be completed, and the new version may also contain new or modified software functions.

● Waterfall development mode

1. The missing requirements or the constantly changing requirements of customers will make the model at a loss, it is suitable for those projects that are relatively stable and easy to understand;

2. Advantages of waterfall development model: 1) Easy to understand 2) Phased research and development 3) Emphasize early planning and requirement investigation 4) Determine when and when products can be deliveredReview and test;

3. Disadvantages of the waterfall development model: 1) Requirement investigation and analysis is only carried out once, which cannot adapt to changes in requirements 2) The sequential development process makes the development experience and lessons can not be fed back to theproject in development.3) Does not reflect the iterative and iterative nature of the software development process 4) Does not include any type of risk assessment 5) Problems that arise during development are not revealed until late in development, thus missing the opportunity for early correction;

● Rapid Prototyping

1. The purpose of applying the rapid model development mode is to determine the real needs of users, so that users can be more clear about their needs in front of the prototype.Prototypes will be discarded after getting clear needs from users.

● Spiral development mode

1. Spiral development mode is a combination of waterfall development mode and rapid prototyping development mode;

2. The main idea of ​​the spiral development model is that it is not necessary to define all the details at the beginning, but start from a small scale, define important functions, implement them as much as possible, and then detect risks and formulate risksControl the plan, accept customer feedback, go to the next stage and repeat the above process, and then repeat the next spiral to determine whether to continue in the next step until the final software product is obtained.

3. Due to the introduction of a very high level of risk identification, risk analysis and risk control in the spiral development model, it puts forward high requirements for the skill level of risk management, and requires moreInvestment of people, money and time.

● RUP model

1. RUP brings together various management experiences in modern software development, and provides a flexible form to meet the needs of various projects and organizations.As a business model, it has very detailed process guidance and templates.

2. Due to the complexity of the model, it will cost a lot to master the model.In particular, the project managers put forward relatively high requirements.

● IPD process development mode

1. The IPD process is a staged model with the shadow of the waterfall model,

2. The model is to improve the overall product quality and gain market share through process costs.Since the process does not define a mechanism for how to perform process rollback, this process is not suitable for projects with frequently changing requirements; for some small projects, it is not very suitable to use this process.

● Agile development mode

1. Agile methods integrate development and testing processes.

2. In agile methods, testing plays the same role in many different ways, and different types of testing play different roles.

3. According to the principles of agile, it is necessary to ensure that the things that can be tested by automation must never be tested manually, and at the same time, the content suitable for manual testing must not be automated at a high cost.test.

4. Don't do the test because the automated test cannot be realized in some aspect.

5. How to use manual testing and automated testing? How to design test cases? These are the challenges faced by agile testing.

In a word, different process models are suitable for different types of software projects.The different process models chosen have a direct impact on software testing.

For more information on testing technology, please pay attention to: Shenzhen Multi-Tester Software and Technical Service Co., Ltd.