当前位置:网站首页>【 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.
边栏推荐
- 宇宙的尽头是银行?聊聊在银行做软件测试的那些事
- 2.5快速排序
- DAY17、CSRF 漏洞
- C. Qualification Rounds(思维,特情)
- Thinkphp 5.0.24变量覆盖漏洞导致RCE分析
- Taobao H5 interface to obtain app data 6.0 format
- What are Redis server startup after the operation?
- Pytorch framework learning record 3 - the use of Transform
- 2.6基数排序(桶排序)
- 05全局配置文件application.properties详解
猜你喜欢
随机推荐
Many overseas authoritative media hotly discuss TRON: laying the foundation for the decentralization of the Internet
MySQL 安装报错的解决方法
error: The following untracked working tree files would be overwritten by
Eureka Registry
(题目练习)条件概率+权值线段树+FWT+后缀数组
弘玑再度入围Gartner 2022 RPA魔力象限并实现位置大幅跃升
机器学习:知道通过低方差过滤实现降维过程
Pytorch framework learning record 3 - the use of Transform
小程序 wx.miniProgram.navigateTo 跳转地址不能是tabbar地址
【驱动】udev设置GPIO加载后所有者、所属组和权限
forward与redirect的区别
【C语言】程序环境和预处理
How to extract year, month and day data in date type in SQL Server
mysql structure, index details
@WebServlet注解(Servlet注解)
Pytorch框架学习记录6——torch.nn.Module和torch.nn.functional.conv2d的使用
逆向理论知识3【UI修改篇】
DAY17:弱口令的探测与测试
GCC Rust获批将被纳入主线代码库,或将于GCC 13中与大家见面
Azure 开发者新闻快讯丨开发者7月大事记一览









