1. The significance of the process is from the long-term development of a software enterprise. To improve the product quality, we should first start with the process and standardize the development process of software products. This is the only way for a software enterprise to move from a small workshop production method to an integrated and standardized company. It is also a key means to fundamentally solve quality problems and improve work efficiency.
The development of software products shares the same characteristics with the production of other products (such as automobiles), that is, production needs to be carried out according to a certain process. In the industry, pipeline production has proved to be an efficient and stable way to ensure product quality. In this way, different personnel are arranged in different positions of the process, and ultimately work together for a single goal, which can prevent the internal friction between personnel and greatly improve work efficiency. Because the process comes from a successful instance, its final product quality can meet the scope set by the process. Software Engineering draws on this experience in the process of software development and applies it to software development. This forms the software engineering process. Simply put, it is the development process.
No matter what we do, there is a gradual process, from planning to strategy to implementation. The software process defines our development process according to this kind of thinking. It defines a complete set of processes from demand to final product delivery based on different product features and previous successful experiences. The process tells us how to implement the product step by step, which risks may occur and how to avoid risks. Because the process comes from successful experience, developing based on the process can reduce our detours, effectively improve product quality and improve user satisfaction.
There are many popular process methods, such as Waterfall Model, spiral model, RUP model, and IPD Process. Different process models are suitable for different types of projects.
2. Test Workflow
2.1 Overall flowchart of testing work
Note: Feedback from integration testing and system testing may lead to modifications to design documents (requirements or databases.
2.2 requirement stage Flowchart
Unit 5/integration testing Flowchart
2.4 system test phase Flowchart
2.5 pressure test Flowchart
Note: stress testing simulates the minimum time for normal system operation when a user is in normal use.
2.6 Performance Testing Flowchart
Note: test the system crash limit (maximum number of users and maximum database capacity ).
