, which is what we often call the performance verification protocol. This thing is used in many places where product testing and engineering acceptance is used. Regarding its performance verification protocols, how to do it? Maybe many people, like me, are all lawsuits! Simply put, it is a set of rules and steps that are set in advance and written in black and white to check whether something is in compliance with its performance or not. Don't think it's as simple as just a look.
1. Basic component modules of the protocol : First of all, there must be _test, which means what you want to test, and you must clearly define the basic situations of model and specifications; then, what do you use as a standard to judge whether it is good or not, and there must be a basis for it? For example, a certain standard stipulated by the state, a certain specification agreed by the industry, etc.; and the other is _test. Which performance points are measured, whether they are speed, accuracy, or stability, must be clearly listed one by one; finally, to put it bluntly, where is the passing line, how much is reached, how much is reached, it is not possible to calculate how much is reached, it must be as clear as black and white!
Provide global procurement services for weak current intelligent products!
2. Disassembly of the verification process steps : The first step is to prepare the temperature and humidity, power supply voltage, and whether there is any interference around. These will affect the results. How to test if you don’t do it well? Then, follow the protocol and operate step by step, such as how long to warm up on the computer, how to set parameters, and how many times the data is sampled, you cannot change it at will; after the measurement is completed, you can record the original data, and this data cannot be filled in blindly, it must be measured in real way; finally, compare the data and see if it is qualified, and give a conclusion – the whole process must be the same as the process, and no step can be missing!
3. Common precautions and guide to avoid pits : Remember, the agreement itself must be first by all! Everyone has to nod and agree with the buyer, seller, or tester, otherwise everyone will talk about their own words at that time, so why don’t they make a big noise? Also, the instruments and equipment used for testing must be checked in advance. If the test is not within the validity period, the accuracy is inaccurate. If the instrument is not accurate, what is the use of the measured results! – By the way, you have to write the steps when writing them. Don’t write some ambiguous words. If you don’t know how to do it after reading them, then it will be useless!
Q: After the agreement is written, can it be modified casually?
A: You can change it, but you must not change it secretly by yourself! All relevant parties must discuss it together, write a change record, and everyone signs and confirms it. Otherwise, if there is a problem in the future, who will admit it? You can't be careless!
Q: Compared with _test plan_, are they the same?
A: Of course it’s different! Test plan is more inclined to the general direction and framework of the entire test, such as why you need to test, who will test, and time schedule; and it focuses more on the details of how to do it, what to test, and how to judge the passing of the test, and the focus is completely different – don't mess it up!
I personally think that if you do this carefully, it will be no harm in controlling the product quality or the successful acceptance of the project. Taking the time to do this is much better than reworking if there is a problem in the future!
Leave a Reply