基于非功能需求的软件体系结构演化

对非功能需求NFRs进行了描述,根据功能需求、NFRs与SA的关系,定义了基于NFRs的SA演化,使用构件组合运算和结构工作链对软件体系结构的非功能特性进行了评估,根据评估结果,给出了基于NFRs的SA演化模型。     

非功能需求跟踪

文中介绍了面向过程的非功能需求跟踪方法的原理，在一个雷达系统的设计过程中进行了该方法的应用分析，并实现了相应的支持工具的原型。     

支持需求追踪的版本控制机制

版本控制是增强软件可维护性的重要方法,但目前常用的版本控制机制缺乏对需求的可追踪性支持。该文提出一种支持需求追踪的版本控制机制,能够有效追踪功能需求、功能设计、代码间的版本关联关系,确保开发人员可以正确获取所需程度的需求追踪信息,有利于软件产品的一致性维护。基于该机制,设计并实现了一个支持需求追踪的版本控制工具VCFQ,并对该工具实现中的一些关键技术进行了论述。     

软件非功能需求的面向方面建模

软件系统的非功能需求通常横切整个系统,采用面向对象的软件开发方法会导致代码缠结和分散.提出一种面向方面的非功能需求建模方法,通过扩展UML表达面向方面的概念,识别系统的功能需求和非功能需求,根据相应的需求得出系统的功能模型和非功能模型,然后将系统的非功能需求用方面实现,功能需求用组件实现,最后将组件和方面编织在一起形成最终的系统.这种方法降低了软件系统的开发难度,提高了系统的模块性、可重用性和可维护性.最后给出了应用实例.     

软件架构中的非功能需求

软件系统架构设计中,非功能需求不仅是架构师知识结构中的重要组成部分之一,也扮演了重要的角色,甚至会直接决定架构的组成。非功能需求主要分为质量属性与约束,且来自于多方。质量属性、约束和功能需求之间能相互作用,并最终在架构设计中体现。     

基于信息检索和本体的动态需求追踪方法

在对现有追踪方法的研究和分析的基础上,提出了一个新的基于信息检索和本体的动态需求追踪模型,由概率相似度计算公式和本体推理相互补充来建立需求追踪关系。通过对模型实现系统的验证,实验结果表明该模型是有效的,并且与常规概率模型相比,需求追踪的精度和效率都得到了一定的提高。     

网络式软件非功能需求冲突消解

在构建非功能需求冲突管理元模型的基础上,给出相关建模元素的形式化描述,将需求冲突的语义定义作为检测依据。根据不同的需求冲突类型和程度,提出一种排除冲突和降低冲突的网络式软件非功能需求冲突消解方法。以旅游出行领域中计算行程费用服务的非功能需求为例,验证了该方法的有效性。     

一种改进的Web软件非功能需求模型

针对Web软件非功能需求的复杂性, 基于ISO/IEC 9126模型以及Web软件属性图, 对基于ISO的Web软件非功能需求模型进行改进。由于已有的模型不具备明显的解释功能, 所以将Web软件所特有的非功能需求属性添加进原有模型对其进行改进, 将原有模型中的12个子属性扩充为18个子属性, 进而利用问卷调查确定原有模型与改进模型中各属性的评价值, 应用因子分析法计算出各属性的因子载荷与因子累计贡献率。结果表明, 改进后的模型能更好地解释Web软件的非功能需求。     

基于设计结构矩阵的可信软件非功能需求评估模型

可信软件非功能需求的量化评估是可信软件研究的一个重要领域。依据构件中非功能需求之间的相互关系,结合设计结构矩阵及矩阵变换、运算的方法,提出了非功能需求贡献值的概念,建立了构件和非功能需求关系的相关阵列及具有统一标准和评判尺度的可信软件非功能需求度量模型,并结合该模型构建了一种用来判断软件非功能需求是否符合软件开发者和用户预期的评估决策方法。最后通过一个实例来说明本模型的合理性和有效性。     

动态需求跟踪中多义关键词的语义判断方法

虽然与信息检索（IR）方法相比，基于本体的动态需求跟踪方法能提高跟踪链的精度，但构建一个合理、有效的本体特别是领域本体是一个相当复杂和繁琐的过程。为了减小构建领域本体带来的时间成本和人力成本，通过将修饰词和通用本体相结合，提出基于修饰词本体的关键词语义判断方法（MOKSJM）。首先，对关键词和修饰词的搭配关系进行分析；然后，采用修饰词本体结合规则的方式来确定关键词的语义，以避免关键词的多义性对动态需求跟踪结果造成的偏差；最后，根据上述分析的结果，对关键词语义作出调整，并通过相似度得分来体现其语义。修饰词在需求文档、设计文档等中数量较少，因此建立修饰词本体所带来的时间成本和人力成本相对较小。实验结果表明，MOKSJM与基于领域本体的动态跟踪方法在召回率相当时，精度差距更小；与向量空间模型（VSM）方法相比，MOKSJM能有效提高需求跟踪结果的精度。     

一种面向特征的软件产品线非功能需求建模方法

分析传统非功能需求定义的不足,基于需求分析阶段的系统抽象—"需求模型"重新定义非功能需求,规范并简化功能需求与非功能需求之间的关系。扩展面向特征的软件产品线建模方法,在特征模型中显式地建模功能需求、非功能需求、非功能需求类型以及它们之间的相互关系,沿用传统特征模型中固有的变化性建模机制建模并管理非功能需求的变化性,显式地复用与非功能需求相关的建模知识和资产,为进一步研究定量评估产品线变体质量的新技术奠定基础。设计了一个基于多视图的特征建模方法,指导开发者在迭代的过程中建模非功能需求和功能需求,支持关注点分离和模型的复杂性管控。实现了工具原型并进行了实例验证。     

Eliciting and prioritizing quality requirements supported by ontologies: a case study using the ElicitO framework and tool

As software complexity grows and clients demand higher quality software, quality requirements can no longer be considered to be of secondary importance. Thus, eliciting, specifying, prioritizing and validating quality requirements is a prerequisite to the development of effective and efficient information systems. Despite the critical importance of quality requirements, there is a considerable gap in the breadth and depth of quality requirements engineering (RE) support in most RE approaches. In practice, it is often the case to have quality requirements considered as an afterthought in the systems development process. While there is a wealth of modelling techniques and tools for functional requirements, there is very limited support for quality requirements in RE. Support for quality requirements is usually ad‐hoc, without clear guidelines on how to capture, specify and manage quality requirements and also without proper usage of standardized terminologies based on established quality models such as the ISO/IEC 9126 quality model. In this paper, we discuss a quality‐driven RE framework and tool that applies knowledge management techniques and quality ontologies to support RE activities. The ontology implements the quality characteristics and metrics prescribed by the ISO/9126 quality model, providing a common vocabulary to address quality concerns/aspects across RE activities. We empirically validate how the framework and tool can be used to effectively support the requirements elicitation and prioritization activities through a case study addressing the development of an intranet portal project at the University of Manchester.     

Acquiring and incorporating state-dependent timing requirements

Some real-time systems are designed to deliver services to objects that are controlled by external sources. Their services must be delivered on a timely basis, and the system fails when some services are delivered too late. In general, the timing requirements of the system may change when the states of the objects monitored by the system change. Such a system may fail if the timing requirements which it is designed to meet are erroneous. It may underutilize resources and consequently be costly or unreliable if the requirements are too stringent. Hence, one must identify how changes in object states call for changes in system requirements and how these changes should be incorporated into the design and implementation of the system. This paper first describes a methodology to determine timing requirements and to take into account requirement changes at runtime. The method is based on several timing requirement determination schemes. Simulation data show that these schemes are effective for applications such as mobile IP hand-offs. The paper then discusses how to incorporate this methodology in the system architecture and in the development process.

Exploring a Bayesian and linear approach to requirements traceability

Context

For large software projects it is important to have some traceability between artefacts from different phases (e.g.requirements, designs, code), and between artefacts and the involved developers. However, if the capturing of traceability information during the project is felt as laborious to developers, they will often be sloppy in registering the relevant traceability links so that the information is incomplete. This makes automated tool-based collection of traceability links a tempting alternative, but this has the opposite challenge of generating too many potential trace relationships, not all of which are equally relevant.

Objective

This paper evaluates how to rank such auto-generated trace relationships.

Method

We present two approaches for such a ranking: a Bayesian technique and a linear inference technique. Both techniques depend on the interaction event trails left behind by collaborating developers while working within a development tool.

Results

The outcome of a preliminary study suggest the advantage of the linear approach, we also explore the challenges and potentials of the two techniques.

Conclusion

The advantage of the two techniques is that they can be used to provide traceability insights that are contextual and would have been much more difficult to capture manually. We also present some key lessons learnt during this research.     

架构设计决策管理工具的研究与设计

目前的架构设计决策隐含于最终架构制品中,导致了涉众交流困难、演化代价高、难以复用等问题。针对上述问题,通过分析架构设计决策的属性及决策制定过程,提出一种描述设计决策与其他外部元素之间关系的元模型,在此基础上设计一个结合编码化和人际化的管理策略的架构设计决策管理工具,实现对设计决策的显式编档、管理和复用。     

Implementation decision making for internetware driven by quality requirements

Internetware is an emerging software paradigm in the open,dynamic and ever-changing Internet environment.A successful internetware must demonstrate acceptable degree of quality when carrying out its functionality.Hence,when internetware is being dynamically constructed,making implementation decisions to satisfice the quality requirements becomes a critical issue.In the traditional software engineering,quality requirements are usually refined stepwise by sub-requirements utilizing goal modeling perspective,until some potential functional design alternatives are identified.The goal-oriented paradigms have adopted graphical goal models to reason about quality requirements and proposed qualitative or quantitative reasoning schemas.However,these techniques may become unviable due to the ever-changing operating environment and demands for run-time decision making.In this paper,we propose an approach for implementation decision making driven by quality requirements for internetware.It focuses on the symbolic formula representation of requirements goal models with the tree structure,which is of well-defined syntax and clear traceability.Furthermore,we explore some reasoning rules which effectively automate each reasoning action on the formulae.This supports multiple-factor decision making.A case study is also provided to illustrate our proposed approach.We have developed a supporting tool based on our theoretical approach that we also present in this paper.     

Development of a new software for comprehensive management and traceability of hospital radiopharmacies

A database software application for comprehensive management and traceability of hospital radiopharmacies has been developed and implemented. This software is a customizable shareware called Radiolab, which provides an immediate and complete traceability of all preparations, controls and radiopharmaceuticals, as well as a great help in the management of reports, orders, stock and radioactive waste. Available by now in five languages (English, Spanish, French, Portuguese and Italian) this software and its manual can be downloaded from the Internet at www.radiopharmacy.net.     

一种软件需求描述语言的设计与实现

提出了一种面向软件行为的需求建模方法和需求描述语言BDL,介绍了需求描述语言的设计和实现方法。利用此需求建模可以根据用户的需求信息寻找出目标系统的有效行为,建立目标系统的行为模型。该行为模型可以帮助用户和开发人员正确认识和理解目标系统的行为,而且能为以后自动检测系统的各种特性提供良好的基础。