Test increases the confidence in the quality of the software. A well-designed test to detect the defects, if any, and so all stakeholders have increasingly rely on software and can not claim that the overall level of risk, the use of the system is reduced.
Quality: The extent to which a component, system or process meets the requirements and / or user needs client / and expectations.
It 's very important that the project team, customers and other project stakeholders to create and accept the expectations of the software. Ensuring the quality of the software is very important to understand what the client understands, and what are their expectations. Typically, software developers and testers to see him - that the software meets the description, it is technically excellent, and there are some errors in it - can not offer the quality of the solution for affected customers and end users of the software.
Quality Score:
1. It is often measured by the analysis of product attributes.
2. Quality is also measured by fitness for use. The quality also has subjective aspects, not only quantitative aspects.
3. It is based on well-defined processes, and also meet the specified requirements. It is measured by the test control and analysis of faults and failures.
4. This is also considered in terms of average value for money, affordability, and a value based on a compromise between time, effort and cost. 5. It is also measured by what we call "transcendent feelings" - it is about the feelings of a person or group of people for a product or supplier.
Apart from understanding what quality feels and looks like customers, users and other stakeholders, it is useful to have some quality to measure the quality of the contras.
No comments:
Post a Comment