Communication Metrics for Software Development
Communication Metrics for Software Development
复制标题
软件开发的沟通指标
DOI：
10.1145/253228.253286
复制
发表时间：
1997
期刊：
影响因子：
--
通讯作者：
B. Brügge
中科院分区：
文献类型：
--
作者：
A.H. Dutoit;B. Brügge
我们提出的经验证据表明，群件工具所产生的通信工件的指标，可以用来获得显着的洞察力，产生它们的开发过程。我们描述了一个测试平台，开发和测试通信指标，高级软件工程项目课程在卡内基梅隆大学，在其中我们进行了几项研究和实验，从1991年至1996年超过400名参与者。这样的测试平台是经验软件工程的理想环境，提供了足够的真实性，同时允许对重要项目参数进行受控观察。我们描述了三个概念验证实验来说明通信度量在软件开发项目中的价值。最后，我们提出了一个统计框架的基础上验证这些通信指标的结构方程。指数术语经验软件工程，通信，统计，结构方程。应用于软件工件的1 I NTRODUCTION ETRICS已被证明在度量软件项目环境中的工具或方法的影响方面是有用的。在某些情况下，它们能够识别工程过程中的特定问题，从而证明度量和其他过程改进工具的价值。然而，软件代码只是软件开发过程中产生的众多工件之一。此外，它往往是在这一进程的后期才可获得的。收集代码指标所需的基础设施和资源也是不可忽视的，并且经常阻止它们用于识别发生的问题。通信构件，如电子邮件、memo- randa或群件工具生成的记录，代表了开发过程的不同视角。它们在整个项目中都可用，它们捕获关于更全面的工件集的信息（例如，代码、过程、组织、政治、士气），并且它们的形式独立于实现技术、开发基础设施、甚至产品的存在。因此，应用于这些通信工件的分析可以提供对产生它们的开发过程的重要洞察。在本文中，我们讨论了一套软件开发的通信度量的设计和评估。我们的目标是开发能够在项目背景下评估工具或方法的度量标准。我们的长期目标是提供度量标准，帮助在问题发生时识别问题。在第2节中，我们用一个例子说明了这些指标的可能用途。
We present empirical evidence that metrics on communication artifacts generated by groupware tools can be used to gain significant insight into the development process that produced them. We describe a test-bed for developing and testing communication metrics, a senior level software engineering project course at Carnegie Mellon University, in which we conducted several studies and experiments from 1991-1996 with more than 400 participants. Such a test-bed is an ideal environment for empirical software engineering, providing sufficient realism while allowing for controlled observation of important project parameters. We describe three proof-of-concept experiments to illustrate the value of communication metrics in software development projects. Finally, we propose a statistical framework based on structural equations for validating these communication metrics. Index Terms—Empirical software engineering, communication, statistics, structural equations. ——————————F—————————— 1I NTRODUCTION ETRICS applied to software artifacts have proven to be useful in measuring the impact of a tool or method in the context of a software project. In some cases, they enabled specific problems in the engineering processes to be identi- fied, thus demonstrating the value of metrics and other in- strumentation for process improvement. However, software code is only one of the many artifacts produced during soft- ware development. Moreover, it is often available only late in the process. The infrastructure and the resources needed to collect metrics on code are also non-negligible, and often prevents their use for identifying problems as they occur. Communication artifacts, such as electronic mail, memo- randa, or records generated by groupware tools, represent a different perspective on the development process. They are available throughout the project, they capture information about a more comprehensive set of artifacts (e.g., code, pro- cess, organization, politics, morale), and their form is inde- pendent of implementation technology, development infra- structure, or even the existence of a product. Metrics ap- plied to such communication artifacts can, therefore, pro- vide significant insight into the development process that produced them. In this paper, we discuss the design and evaluation of a set of communication metrics for software development. Our goal is to develop metrics that enable the assessment of a tool or a method in the context of a project. Our long-term goal is to provide metrics that help identifying problems as they occur. In Section 2, we illustrate possible uses of these metrics with an example.
SR-A（其配体是修饰的低密度脂蛋白）对 1 型糖尿病发病的影响。
DOI：
--
发表时间：
2012
期刊：
影响因子：
--
作者：
清水まみ;安田尚史;中村晃;勝田敦美;佐々木弘智;荒井隆志;永田正男;原賢太;横野浩一
通讯作者：
横野浩一