目 录
1. 绪论 1
1.1 研究背景 1
1.2 选题的目的和意义 1
1.3 相关领域研究概况 2
1.3.1 敏捷开发的现状及在中国的发展2
1.3.2 质量管理的研究现状3
1.4 研究内容和方法 4
1.4.1 研究内容 4
1.4.2 研究方法 5
2. 敏捷开发与软件质量管理理论基础7
2.1 敏捷开发的相关知识 7
2.1.1 敏捷开发思想 7
2.1.2 敏捷开发与传统开发模式比较8
2.2 质量管理的相关知识 9
2.2.1 质量管理的发展 9
2.2.2 质量管理的特点 10
2.2.3 现代质量管理的方法12
2.2.4 现代软件质量管理思想13
2.2.5 软件质量的评价标准13
2.2.6 软件测试 15
3. YL 公司协会助手项目的质量管理现状及问题17
3.1 项目概述 17
3.1.1 公司简介 17
3.1.2 项目简介 18
3.2 YL 公司协会助手项目的质量管理介绍 20
3.2.1 需求分析阶段 21
3.2.2 软件设计阶段 22
3.2.3 软件编码阶段 24
3.2.4 软件测试阶段 27
3.3 存在的问题及原因 28
3.3.1 需求分析阶段 28
3.3.2 软件设计阶段 28II
3.3.3 软件编码阶段 29
3.3.4 软件测试阶段 29
4. YL 公司协会助手项目质量管理改进对策 30
4.1 需求分析阶段 30
4.2 软件设计阶段 31
4.3 软件编码阶段 31
4.4 软件测试阶段 32
4.4.1 单元测试评审 32
4.4.2 自动化回归测试 33
4.4.3 使敏捷团队整体参与33
4.4.4 缺陷预防 34
5. 总结与展望 35
5.1 总结 35
5.1.1 需求分析阶段 35
5.1.2 软件设计阶段 35
5.1.3 软件编码阶段 35
5.1.4 软件测试阶段 35
5.2 展望36
参考文献37
致 谢39III
Contents
1. Introduction1
1.1 Background1
1.2Purpose and significance of topics1
1.3 related areas of research before2
1.3.1 Current Situation and Development of agile development in China of1.3.2 Current Situation Quality Management3
1.4 Contents and Methods 4
1.4.1 research 4
1.4.2 Methods 4
2. Agile development and software quality management theory 7
2.1Knowledge of agile development 7
2.1.1 Agile Thought7
2.1.2 Agile development compared with the conventional development model2.2Knowledge of quality management9
2.2.1 Development of quality management 9
2.2.2 Quality management features 10
2.2.3 modern quality management approach11
2.2.4Software Quality Management Modern Thought 12
2.2.5 software quality evaluation criteria13
2.2.6 Software Testing15
3. Quality management status and problems YL Companies Association assistant
project 17
3.1 Project Overview 17
3.1.1 Introduction 17
3.1.2 Project 18
3.2 Quality Management YL Company Institute project assistant Introduction 20
3.2.1 requirements analysis phase 21
3.2.2 software design phase 23
3.2.3 software coding stage 24IV
3.2.4 software testing stage 27
3.3 Problems and Causes 29
3.3.1 requirements analysis phase 29
3.3.2 software design phase 29
3.3.3 software coding stage 29
3.3.4 software testing stage 29
4. YL Companies Association Assistant Project Quality Management Improvement
Measures 30
4.1 Requirements analysis stage 30
4.2 Software Design phase 31
4.3 software coding stage 31
4.4 software testing stage 32
4.4.1 Test evaluation unit 32
4.4.2 Automated Regression Testing 33
4.4.3 make the whole team involved in agile 33
4.4.4 Defect Prevention 34
5. Summary and Outlook 35
5.1 summary 35
5.1.1 requirements analysis phase 35
5.1.2 software design phase 35
5.1.3 software coding stage35
5.1.4 software testing stage 35
5.2 Outlook 36
References 37
Acknowledgements 391
摘 要
随着软件行业的快速发展，客户的软件意识也随之提升，这也让他们对软件
提出了更高的要求，在产品需求上要求多样性和个性化。这样带来的变化就是需
求的频繁变更，软件的开发和管理难度加大。如何应对变更的需求，提高软件产
品的质量。经过这样的反思和总结，敏捷开发出现了，这顺应了时下的趋势

“以人为本、拥抱变化”是敏捷开发倡导的，它是采用迭代的思想进行项目
的开发。把项目分解成一个个的周期，每个周期是一次完全软件开发过程，产出
的是可交付的软件。这样敏捷开发的质量管理过程就是对一个个迭代过程的质量
管理过程的集合

本文首先对论文框架和理论知识进行介绍，接着从敏捷开发的过程入手，提
出了敏捷开发过程及质量管理图解，然后分别从四个敏捷开发阶段对质量管理进
行了梳理和研究：①从需求阶段出发，对需求管理、需求描述、需求分配进行了
质量管理梳理和研究；②从软件设计阶段出发，对需求宣讲、文档质量进行了质
量管理的梳理和研究；③从软件编码阶段出发，对编码规范、代码检查、测试前
移、面对面代码复查进行了质量管理的梳理和研究；④从软件测试阶段出发，对
持续集成、小型发布进行了质量管理的梳理和研究

接着通过分析和综合，整理出四个阶段质量管理中出现的问题及原因，分别
为：①在需求阶段，还是存在对客户的需求把握不够精准，开发人员对需求的理
解存在偏差等问题；②在软件设计阶段，对需求宣讲、文档质量进行了质量管理，
但还是存在编码人员对设计方案理解有误和存在偏差的问题；③在编码阶段，编
码人员没有留下关键文档，导致后面的测试人员无从下手；软件的代码质量不高
等问题；④在测试阶段，返工和漏测试问题较为严重；测试团队得不到开发团队
的认可，离职率非常高等问题。之后也针对这些问题提出了相应的对策及改进措
施

最后，对全文进行了总结，对自己的观点进行了回顾，并紧扣主题，进行了
敏捷开发模式下的质量管理研究

本文是通过 YL 公司协会助手项目的具体实践，在协会助手项目中的四个阶
段：需求分析阶段、软件设计阶段、软件编码阶段、软件测试阶段，梳理出这些
阶段分别是如何进行质量管理的，并结合理论知识，把实际项目实践与理论研究
融合起来，研究分析后，提出的一些原则、方法和建议，希望对实施敏捷开发的
项目管理者和开发人员有所借鉴。也希望对新旧软件开发模式的比较，为更多实
施敏捷开发的企业提供参考。最重要的是提出了质量管理的合理化措施和建议，2
希望能有助于敏捷开发模式下的质量管理的提高，为我国的软件及信息产业的发
展作出贡献

关键词:质量管理；敏捷开发；Scrum3
Abstract
With the rapid development of the software industry, customers are increasing
awareness of software, the software which allow them to put forward higher
requirements on the product demand requires diversity and personalization. Such
frequent changes brought about change is the demand, development and management
software to increase the difficulty. How to deal with changing requirements, improve
the quality of software products. After such review and summary, agile development
appeared, which conforms to the trend nowadays.
People-oriented, embrace change advocated by agile development, it is the idea
of an iterative development projects. Break the project down into one of the cycles, each
cycle is a complete software development process, the output of the software can be
delivered. Quality management process so agile development is set on a quality
management process of the iterative process.
Firstly, the thesis introduces the framework and theoretical knowledge, and then
start from the agile development process, proposed agile development process and
quality management diagram, and then were four agile development stage of the sort of
quality management and research: ① from the requirements phase starting on demand
management, requirements specification, demand assignment of a quality management
combing and research; ② from the software design phase of view, the demand for
lectures, quality of documentation of the sort and quality of research management; ③
from software coding stage starting coding specification, code inspection, testing
forward, face to face the code review of the sort of quality management and research;
④ departure from the software testing phase, continuous integration, smaller publishers
of the sort of quality management and research.
Followed by analysis and synthesis, sorting out the four stages of quality
management problems and the reasons are: ① in the requirements phase, there is still
not enough to grasp customer needs accurately, developers need to understand there is a
deviation and other issues; ② in the software design stage, the demand for lectures,
documentation quality quality management, but there is still coders design had
misunderstood and there is a deviation of the problem; ③ in the coding phase, the
coders did not leave key documents, resulting in subsequent tests staff not start; the
software code quality is not high; ④ in the testing phase, leak testing and rework the
problem is more serious; the test team are not recognized by the development team, the4
turnover rate is very advanced problem. After also address these issues the
corresponding countermeasures and improvement measures.
Finally, the full text of the summary of their views were reviewed, and concentrate
on the theme, carried out quality management in agile development mode.
This article is by practice YL Association assistant project company, in association
with the project assistant in four phases: requirements analysis phase, the software
design phase, software coding phase, the software testing phase, to tease out how these
stages are quality management, and theoretical knowledge to actual practice and
theoretical research projects integrate some principles, methods and recommendations
from the study analysis, in the hope that the project managers and developers to
implement agile development has reference. Also we want to compare the old and new
software development model, in order to implement more agile enterprise reference.
The most important is to propose a quality management rationalization measures and
proposals, hoping to help improve Agile development mode of quality management for
the development of software and information industry to contribute to our country.
Key words: quality management; agile; Scrum1. 绪论1. 绪论
1.1 研究背景
目前，我国软件行业正处于行业的成长期，软件行业发展非常迅猛，软件市
场增长率也不低，软件业务的需求在高速增长，软件产业正在以一个新兴的产业
部门角色，频繁地出现在大众的视野中。机遇和挑战并存，随着市场的成熟，软
件行业也带了全新的挑战

首先，软件市场的繁荣发展，让客户的软件意识极大地得到了培养和发展，
同时也让他们对软件提出了更高的要求，在产品需求上要求能够做到多样性和个
性化。“客户至上、拥抱变化”已经成为软件企业经营发展的常态。在复杂多变
的市场环境中，如何实现项目目标、准确地把握需求、交互高质量的产品，这是
软件单位面临的一个难题

其次，软件产品要求能快速上线，生命周期逐渐被缩短。传统的软件开发过
程有一套完整的
。。。。。。以上简介无排版格式，详细内容请下载查看