度量与分析域在同行评审中的实践

度量与分析域是CMMI中一个非常重要的过程域,但要在软件项目中有效实施却是困难的。同行评审是软件行业一致公认的最佳实践,软件企业越来越重视同行评审。本文探讨如何将度量运用于同行评审中,以促进同行评审的有效开展,最终达到保证软件质量的目的。     

开源社区评审过程度量体系及其实证研究

在开源社区中,不同开发人员提交的代码水平参差不齐,需要代码评审检查提交代码质量.决策者是代码评审的关键人物,审核提交代码,发现软件缺陷.代码评审情况会对开源软件质量产生影响,因此需要建立评审过程度量体系,了解代码评审情况,促进提高开源软件项目质量.现有的软件过程度量方法主要考虑提交代码和评审评论活动,缺乏考虑决策活动,难以充分度量人员的评审行为.引入决策者因素,提出了一个开源社区评审过程度量体系,包括评审活动指标和人员分布指标.评审活动指标包含评审次数、评审信息长度、评审代码改动行数以及评审时间.人员分布指标主要考虑改动者、评论者和决策者的比例和数量.然后,收集了3个热门开源项目数据,分析评审过程度量指标与软件缺陷数量的关系.通过实证研究分析发现：决策者数量,少改动、少评论、少决策者的比例等决策者相关指标和软件缺陷数量中等正相关.同时,与不考虑决策者的度量体系进行对比分析,发现含有决策者的度量体系与软件缺陷的相关性更高.实证研究结果验证了评审过程度量体系的有效性,说明增加决策者相关指标的必要性.     

基于正交设计的软件过程度量分析方法

软件过程度量的一项工作是分析、确定影响过程能力的显著因素,并将其结果作为建立过程改进决策的基础,即在软件过程度量中找出影响某一指标的主要因素,针对这些因素对软件过程加以控制和改进.这一过程对建立过程改进的有效决策是至关重要的.将数理统计学中的正交设计方法引入到软件过程度量中,提出了一种基于正交设计的软件过程度量分析方法,量化标识软件过程的主要因素,协助决策者找出需要进行重点监控的关键因素,为过程改进提供了基础.     

软件项目的同行评审

软件评审是软件项目中重要的环节,与软件测试共同构建了软件开发的保障体系.列出了发现错误的时间与软件成本和开发风险的关系,分析了同行评审的种类和对象,指出了可行的评审过程,并总结了项目开发过程中评审容易出现的错误.通过同行评审,能够及早识别并消除缺陷,让软件交得更易维护,通过对这些错误的分类和统计,发现共同的缺陷类型和修...     

基于CMMI的软件过程度量

软件度量已经逐渐成为了软件工程领域中极其重要的一部分。该文提出了一种软件过程的度量模型。在该模型中定义了与实施软件过程度量有关的活动。并在此基础上,重点阐述和说明了数据收集、认证和分析的目标、任务以及方法。文中还给出了一个把该模型应用于大型软件公司的实例,以说明该模型能够有效地评估并改进软件过程。该文的研究结果对改进软件过程、增加组织的过程能力成熟度是很有帮助的。     

基于CMMI的软件过程度量

软件度量已经逐渐成为了软件工程领域中极其重要的一部分。该文提出了一种软件过程的度量模型。在该模型中定义了与实施软件过程度量有关的活动。并在此基础上,重点阐述和说明了数据收集、认证和分析的目标、任务以及方法。文中还给出了一个把该模型应用于大型软件公司的实例,以说明该模型能够有效地评估并改进软件过程。该文的研究结果对改进软件过程、增加组织的过程能力成熟度是很有帮助的。     

软件度量的概念模型

度量面临的重要问题是建立引入和运用度量的一个有效的方法和框架.使用统一的术语、明确的语义对组 .织的过程模型进行定义;创建具体的度量模型参考框架的度量元模型,建立组织整体的度量管理.为解决上述问题,本文建立了软件度量的概念模型CMMP(Conceptual Model of Measurement Process),它是基于软件过程工程元模型(sPEM)的,从而可与现有的过程模型有效地集成.     

基于CMMI的软件度量研究

CMMI为软件产品及软件过程提供了一套定量的表示和分析,即软件度量的模型.有效的软件度量过程能促进组织的软件过程能力的改进.文章结合国内应用特点,介绍了基于CMMI的多层架构软件产品的度量模型,并着重讨论了基于CMMI的软件过程度量,总结了软件过程度量的工作方法和思路,提出了解决国内软件度量的一般性方法,为软件过程改进提供了可行的方法和实践.     

CMM/CMMI中同行评审子过程的定量控制

为了解决实施CMM／CMMI过程中对软件过程的定量控制问题，进而实现对软件质量、成本和进度的定量管理，引进计算数学中的“线拟合”方法。该方法描述了互相牵制的定量指标之间的数学关系，弥补了经典的SPC技术只能分析单个度量的不足。将“曲线拟合”法用于对“同行评审”子过程的定量控制，实践证明，它较好地刻画了该子过程两个定量指标之间的关系，使得“同行评审”的结果在任何时候都是精确受控的。     

建立和改进软件过程能力的一个解决方案

建立和改进软件过程能力是CMM或CMMI高成熟度等级的要求,也是软件度量的一大难点。该文探讨了与软件过程能力相关的一些概念和问题,定义了软件过程能力指数,采用统计过程控制的XmR控制图技术给出了建立和改进软件过程能力的一个定量化解决方案,并使用一个软件项目模块编码和单元测试的软件过程能力建立和改进的实例演示和说明了该解决方案的使用过程和方法。     

Comparative case studies of open source software peer review practices

ContextThe power of open source software peer review lies in the involvement of virtual communities, especially users who typically do not have a formal role in the development process. As communities grow to a certain extent, how to organize and support the peer review process becomes increasingly challenging. A universal solution is likely to fail for communities with varying characteristics.ObjectiveThis paper investigates differences of peer review practices across different open source software communities, especially the ones engage distinct types of users, in order to offer contextualized guidance for developing open source software projects.MethodComparative case studies were conducted in two well-established large open source communities, Mozilla and Python, which engage extremely different types of users. Bug reports from their bug tracking systems were examined primarily, complemented by secondary sources such as meeting notes, blog posts, messages from mailing lists, and online documentations.ResultsThe two communities differ in the key activities of peer review processes, including different characteristics with respect to bug reporting, design decision making, to patch development and review. Their variances also involve the designs of supporting technology. The results highlight the emerging role of triagers, who bridge the core and peripheral contributors and facilitate the peer review process. The two communities demonstrate alternative designs of open source software peer review and their tradeoffs were discussed.ConclusionIt is concluded that contextualized designs of social and technological solutions to open source software peer review practices are important. The two cases can serve as learning resources for open source software projects, or other types of large software projects in general, to cope with challenges of leveraging enormous contributions and coordinating core developers. It is also important to improve support for triagers, who have not received much research effort yet.     

Revisiting Linus’s law: Benefits and challenges of open source software peer review

Open source projects leverage a large number of people to review products and improve code quality. Differences among participants are inevitable and important to this collaborative review process—participants with different expertise, experience, resources, and values approach the problems differently, increasing the likelihood of finding more bugs and fixing the particularly difficult ones. To understand the impacts of member differences on the open source software peer review process, we examined bug reports of Mozilla Firefox. These analyses show that the various types of member differences increase workload as well as frustration and conflicts. However, they facilitate situated learning, problem characterization, design review, and boundary spanning. We discuss implications for work performance and community engagement, and suggest several ways to leverage member differences in the open source software peer review process.     

CMM中各类评审的综合研究

对CMM中各种评审进行综述、分类和比较，重点对软件评审进行研究，比较了同行评审与里程碑评审之间以及软件评审与软件测试之间的差异，描述了标准的软件评审过程。     

软件过程改进方法的研究与设计

成熟度模型(CMM)是当前国内外研究的热点。给出了如何理解CMM的基本概念，提出了两种软件过程改进方法，即基于同行评审和测试的软件过程改进方法和基于CASE工具和文档的软件过程改进方法。这两种方法是分别针对现有软件开发机构实施过程改进时遇到的实际问题，结合CMM的关键实践而设计的。最后对现有软件过程活动中存在的问题进行了相关总结。     

SCRUB: a tool for code reviews

This paper describes a tool called Source Code Review User Browser (SCRUB) that was developed to support a more effective and tool-based code review process. The tool was designed to support a large team-based software development effort of mission critical software at JPL, but can also be used for individual software development on small projects. The tool combines classic peer code review with machine-generated analyses from a customizable range of source code analyzers. All reports, whether generated by humans or by background tools, are accessed through a single uniform interface provided by SCRUB.     

Using peer tutoring in evaluating the usability of a physically interactive computer game with children

This paper presents a novel approach to usability evaluation with children called peer tutoring. Peer tutoring means that children teach other children to use the software that is evaluated. The basic philosophy behind this is to view software as a part of child's play, so that the teaching process is analogous to explaining the rules of a game such as hide and seek. If the software is easy to teach and learn, it is more likely that the amount of users increases in a social setting such as a school. The peer tutoring approach provides information about teachability and learnability of software and it also promotes communication in the test situation, compared to a test person communicating with an adult instructor. The approach has been applied to the development of a perceptually interactive user interface in QuiQui's Giant Bounce, a physically and vocally interactive computer game for 4–9 year old children. The results and experiences of using peer tutoring are promising and it has proved to be effective in detecting usability flaws and in improving the design of the game.