当前位置:网站首页>【 notes 】 the beauty of the software engineering - column 31 | software testing are responsible for the quality of products?
【 notes 】 the beauty of the software engineering - column 31 | software testing are responsible for the quality of products?
2022-07-30 04:29:00 【if...else...】
Article table of contents
Column information
Columnist: Baoyu
Column Publishing Platform: Geek Time

Main content
Because software development is composed of multiple links, from the initial requirements to the subsequent design and development, each link may lead to quality problems. Testing can only be used for software products that have been developed.The detection does not interfere with the whole process.
Who is responsible for product quality?Before answering this question, you might as well think about a more essential question: what is software product quality?
I. What is software product quality?
Functional quality, code quality, and process quality combine to provide a good overview of software quality.
Functional quality
End users get the software and experience the functions of the software, and the quality of the functions directly determines the quality of the product.
Code Quality
The most important part of software is the code, and code quality refers to the quality of the architecture and code that implement the software's functions.
Process quality
Software development is inseparable from software engineering and project management.The quality of the software development process determines whether your project can be completed on schedule and within budget.
2. Who is responsible for product quality?
Since product quality is jointly determined by functional quality, code quality and process quality, being responsible for product quality means being jointly responsible for these three aspects.
Responsibility and power need to be equal. For example, if you make the developer responsible for the software development process, the premise is that he must have the power to influence and control the development process, otherwise he will talk about responsibility without powerIt's just hooliganism.
I think if you want to sort it out, the first person responsible for software quality is the project leader, then the developers, and then the software testing.
Although from the perspective of rights and responsibilities, the project leader should be most responsible for the quality of the project, but in terms of effect, it is the developers who are most responsible for the quality of the project.
Third, how to achieve "everyone is responsible for product quality"?
Only when a culture that values product quality is truly established within the team will everyone be truly accountable for quality.
What are some ways to help your team build this "everyone cares about product quality" culture?
- First of all, you can refer to flat management in agile development.
- Secondly, there is an option to split the team down.
- Alternatively, integration between trades can also be encouraged.
- The last thing is to formulate a corresponding system to encourage everyone to pay attention to quality.
To achieve "everyone is responsible for product quality", as mentioned above, It should fall on actions rather than slogans, and the organization should be flat and miniaturized, and the division of labor should be carried out.Breaking the post wall and encouraging everyone to pay attention to quality in the system can truly establish a culture that values product quality and improve product quality together.
IV. Other excerpts
- Testing cannot directly test the code written by development. It can only be tested based on software functions. That is to say, for the quality of the code, testers have nothing to do.
- Meeting user needs is the most basic requirement for functional quality.
- Although the process quality cannot be directly perceived by the user, the process quality will directly affect the code quality and functional quality, and even the success or failure of the product.
- Developers can more easily find bugs in the code, and it is easier to ensure good code quality and improve test efficiency by means of architecture design and automated testing of code.
- What is emphasized in agile development is that everyone in the project is responsible for product quality, and everyone is responsible for product quality.
Summary
Ensuring high quality software is not just the tester's responsibility.Software quality is reflected in three aspects: functional quality, code quality and process quality. Being responsible for product quality also means being jointly responsible for these three aspects.
边栏推荐
- Thinkphp 5.0.24变量覆盖漏洞导致RCE分析
- Database Design of Commodity Management System--SQL Server
- Azure 开发者新闻快讯丨开发者7月大事记一览
- What is the data directory?Why do you need it?
- labelme的使用技巧
- 2.6归并排序
- JQ source code analysis (environment)
- WEB penetration of information collection
- [Driver] udev aliases each serial port of USB to 4 serial ports
- Flink学习第一天——什么是批量、流式计算?
猜你喜欢

骁龙7系芯片表现如何?Reno8 Pro佐证新一代神U

2.4希尔排序

Install MySQL Database on Kylin V10 Operating System

【软件工程之美 - 专栏笔记】31 | 软件测试要为产品质量负责吗?

Is the end of the universe a bank?Talk about those things about doing software testing in the bank

图像视角矫正之透视变换矩阵(单应矩阵)/findHomography 与 getPerspectiveTransformd的区别

Why is the Kirin 9000 5G version suddenly back in stock?

sql语句-如何以一个表中的数据为条件据查询另一个表中的数据

BGP的简单实验

海外多家权威媒体热议波场TRON:为互联网去中心化奠定基础
随机推荐
Eureka Registry
图像视角矫正之透视变换矩阵(单应矩阵)/findHomography 与 getPerspectiveTransformd的区别
[Driver] udev sets the owner, group and permissions after GPIO is loaded
Unity3D Application模拟进入前后台及暂停
新型LaaS协议Elephant Swap给ePLATO提供可持续溢价空间
2021山东省网络搭建与应用赛项试题
Pytorch framework learning record 3 - the use of Transform
2.6基数排序(桶排序)
MySQL installation error solution
2022.7.29-----leetcode.593
Thymeleaf简介
逆向分析实战2
使用EFR32作为Zigbee/Thread的sniffer的用法
cnpm installation steps
逆向理论知识3【UI修改篇】
The underlying mechanism of the function
我的Go+语言初体验——祝福留言小系统,让她也可以感受到你的祝福
phpoffice edit excel document
【Untitled】
How does the Snapdragon 7 series chip perform?Reno8 Pro proves a new generation of God U