软件中间产品质量度量

本文对软件过程中的需求分析、设计阶段所产生的需求分析说明书、设计说明书等中间产品本身进行比较分析,并对现有的各种软件度量方法进行研究,提出了一套适合于中间产品的度量体系。在此基础上设计、开发一个易于应用和计算的度量系统,能比较如实地反映中间产品的特性,提取一些有用信息,从而有效地控制软件的开发,提高软件开发的效率和质量。     

一种谓词驱动的目标求精方法

目标求精是场景和目标相结合的需求建模方法中的一个重要环节。该文基于目标和场景相结合的需求建模,提出了谓词驱动的目标求精方法,通过对目标谓词描述的分类来指导整个求精过程的进行。同传统的求精方法相比,该方法具有对需求分析员的依赖较小、自动化程度高等优点。     

The empirical investigation of Perspective-Based Reading

We consider reading techniques a fundamental means of achieving high quality software. Due to the lack of research in this area, we are experimenting with the application and comparison of various reading techniques. This paper deals with our experiences with a family of reading techniques known as Perspective-Based Reading (PBR), and its application to requirements documents. The goal of PBR is to provide operational scenarios where members of a review team read a document from a particular perspective, e.g., tester, developer, user. Our assumption is that the combination of different perspectives provides better coverage of the document, i.e., uncovers a wider range of defects, than the same number of readers using their usual technique.To test the effectiveness of PBR, we conducted a controlled experiment with professional software developers from the National Aeronautics and Space Administration/Goddard Space Flight Center (NASA/GSFC) Software Engineering Laboratory (SEL). The subjects read two types of documents, one generic in nature and the other from the NASA domain, using two reading techniques, a PBR technique and their usual technique. The results from these experiments, as well as the experimental design, are presented and analyzed. Teams applying PBR are shown to achieve significantly better coverage of documents than teams that do not apply PBR.We thoroughly discuss the threats to validity so that external replications can benefit from the lessons learned and improve the experimental design if the constraints are different from those posed by subjects borrowed from a development organization.     

模拟执行操作目标的方法研究

模拟执行的检测方法是检测需求规格说明书的一种重要手段。在目标和场景相结合的需求建模方法的基础上,提出了对操作目标集合的模拟执行方法。该方法为代理的层次划分提供了理论支持,并将操作目标集合转换成了基于规则的层次式有穷状态自动机,通过对基于规则的层次式有穷状态自动机的模拟执行,达到了对操作目标集合的模拟执行。     

软件需求工程-方法及工具评述

文中从需求工程的基本概念和研究内容出发,简单介绍了需求工程生命周期和需求规范等概念;比较全面地总结了现有的有代表笥的需求工程开发方法和工具,对其中一些重要的方法及工具作了分类和评述,并指出了需求工程方法和工具开发与实际领域相脱离等不足之处;最后探讨了需求工程研究现状中存在的一些主要问题及一些相应的解决方案。     

Prediction of Run-Time Failures Using Static Product Quality Metrics

A study is presented in which it is determined whether software product metrics gathered statically from designs or source code may be helpful in predicting the number of run-time faults that will be encountered during execution. Metrics examined include intermodule metrics such as fan-in and fan-out, as well as intramodule metrics such as cyclomatic complexity and size. Our study indicates that it may be possible, with certain classes of software products, to predict the run-time behaviour using well-known static intermodule metrics.     

ITSS运行维护服务标准综述

介绍了ITSS运行维护部分已颁布的3项标准(GB/T 28827.1、GB/T 28827.2和GB/T 28827.3)的适用范围以及运行维护服务的能力模型、交付规范和应急响应过程。这3项标准的颁布标志着"信息技术服务"将作为国家标准的一个系列,从此得以固化;同时,ITSS也将会是国内IT服务行业最重要的标准。     

A Critical Analysis of Current OO Design Metrics

Chidamber and Kemerer (C&K) outlined some initial proposals for language-independent OO design metrics in 1991. This suite is expanded on by C&K in 1994 and the metrics were tested on systems developed in C++ and Smalltalk™. The six metrics making up the C&K suite can be criticised for a number of reasons. This does not make them bad metrics; on the contrary the C&K work represents one of the most thorough treatments of the subject at the current time. However, the authors explicitly state ...there is no reason to believe that the proposed metrics will be found to be comprehensive, and further work could result in additions, changes and possible deletions from this suite. This analysis will serve to make other researchers and practitioners aware of some of the problems that may arise from using these measures. As a by-product, the axioms of E. Weyuker (1983) come under scrutiny in terms of their applicability to object-oriented metrics. This revised version was published online in August 2006 with corrections to the Cover Date.     

一种面向多目标的适应性设计规约方法

自适应软件越来越多地被应用于不同的领域,如各种分布式信息系统、安全攸关的抗毁系统、防病毒防入侵系统等.正确理解系统的适应性需求,是正确开发自适应系统的前提.将面向目标的规约语言(KAOS)进行扩展,增加了策略模型,建立支持面向多目标的基于动态策略的适应性需求规约方法.     

冶金规范及工艺卡技术在钢管企业中的应用

首先介绍冶金规范及工艺卡技术的产生与含义,然后从系统需求分析出发,介绍其整体结构、具体内容以及在钢管冶金企业中的地位与应用及其应用效果等。     

产品可视化需求建模系统下的交互式产品开发

在公理化设计理论的基础上,建立了需求产品的需求商机模型、需求参考模型与需求定义模型。建立产品知识库,应用九象限法对敏捷获取的需求商机的市场吸引力和企业实力多因素模型进行综合评估决策;对产品需求进行功能分解与整合,集成为需求产品,对其进行一致性检查;通过VRML完成需求产品的可视化表达。并以电冰箱的设计过程为例,讨论并验证了产品可视化需求建模环境下交互式需求创新产品开发系统RADAR的有效性。     

嵌入式实时系统的软件需求检测

以需求描述模型HRFSM(hierarchical finite state machines based on rules)为基础,提出了一个嵌入式实时系统软件的动态执行模型(dynamic execution model,简称DEM)和基于该模型的检测方法.由于DEM能将控制流、数据流和时间有效地集成为一体,故提出的检测方法能检测嵌入式实时系统的软件需求的一致性和完全性.该检测方法由3种侧重点不同的检测形式组成,并能在检测过程中提供一些重要的检测信息.分析员可以利用基于该检测方法的工具灵活地对嵌入式实时系统的软件需求进行检测,以提高分析和检测软件需求的效率.     

Using multiple metrics for analysis of improvement

To make global decisions about a project or group of projects, it is necessary to analyse several metrics in concert, as well as changes in individual metrics. This paper discusses several approaches to collective metrics analysis. First, classification tree analysis is described as a technique for evaluating both process and metrics characteristics. Next, the notion of a multiple metrics graph is introduced. Developed initially as a way to evaluate software switch quality, a multiple metrics graph allows collections of metrics to be viewed in terms of overall product or process improvement.This work was done while the authors were affiliated with Contel Technology Center, Chantilly, Virginia, USA.     

基于领域知识的需求信息获取

本文提出一种基于领域知识的需求信息获取方法．相应的ＭＩＳ开发环境ＰＲＯＭＩＳ已成功地应用于多个领域．     

产品线可变性的需求方法研究

软件产品线领域需求记录了不同软件产品的共性和可变性。在现有需求过程框架下,对产品线需求获取方法与需求分析方法进行了研究,完善了产品线需求可变性的管控机制。以原子需求为视点,提出了利用需求场景获取产品线领域需求的方法;通过原子需求构建的产品需求矩阵与用例需求矩阵,分析得出需求资源的可变性关系;通过可变性关系的形式化描述,建立产品线可变性用例模型。     

利用XML实现业务规则和信息系统分离的方法研究

企业信息系统常因业务规则的改变而导致信息系统无法使用,提出了将业务规则与信息系统分离的观点,探讨了利用XML作为描述软件需求文档的可行性.藉由XML的机器可读性,让信息系统直接读取包含业务规则的软件需求文档,以实现业务规则和程序代码分离,进而实现需求文档的重用.     

基于SPC的软件需求度量方法

软件需求管理是软件生产与质量管理的重要内容．面对今天以需求变化难以控制为主要特点的软件危机,我们一方面必须采用更加合适的软件工程和需求工程方法,去适应需求的不断变化和增长;同时还必须采用合适的度量方法和手段,去分析需求变化的趋势和原因,并控制和管理需求的变化．该文提出了一种以统计过程控制原理对软件项目的需求变化进行统计控制,并对异常波动进行度量分析的软件需求度量方法．