非功能需求的结构化定义以及概念性追踪管理框架

针对需求工程中非功能需求概念非常模糊甚至相互矛盾、非功能需求与其他非功能需求及功能需求之间的关系繁复而难以分析和建模、非功能需求与设计阶段制品之间的追踪关系模糊而不易记录和维护等问题,分析了与非功能需求相关的概念在需求分析阶段和体系结构设计阶段的表现形式,给出了一个结构化的非功能需求定义;规范了不同类型需求之间的各种复杂关系,建立了一个跨越分析和设计阶段的概念性非功能需求追踪管理框架,规范了需求分析和体系结构设计阶段与非功能需求相关的概念和制品之间的关系。提出的结构化定义以及概念性追踪管理框架明确地刻画了非功能需求概念的外延,为简化需求模型以及进一步研制系统化、实用化的非功能需求建模及追踪管理技术奠定了理论基础。     

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

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

A model-driven traceability framework for software product lines

Software product line (SPL) engineering is a recent approach to software development where a set of software products are derived for a well defined target application domain, from a common set of core assets using analogous means of production (for instance, through Model Driven Engineering). Therefore, such family of products are built from reuse, instead of developed individually from scratch. SPL promise to lower the costs of development, increase the quality of software, give clients more flexibility and reduce time to market. These benefits come with a set of new problems and turn some older problems possibly more complex. One of these problems is traceability management. In the European AMPLE project we are creating a common traceability framework across the various activities of the SPL development. We identified four orthogonal traceability dimensions in SPL development, one of which is an extension of what is often considered as “traceability of variability”. This constitutes one of the two contributions of this paper. The second contribution is the specification of a metamodel for a repository of traceability links in the context of SPL and the implementation of a respective traceability framework. This framework enables fundamental traceability management operations, such as trace import and export, modification, query and visualization. The power of our framework is highlighted with an example scenario.     

A distributed requirements management framework for legal compliance and accountability

Increasingly, new regulations are governing organizations and their information systems. Individuals responsible for ensuring legal compliance and accountability currently lack sufficient guidance and support to manage their legal obligations within relevant information systems. While software controls provide assurances that business processes adhere to specific requirements, such as those derived from government regulations, there is little support to manage these requirements and their relationships to various policies and regulations. We propose a requirements management framework that enables executives, business managers, software developers and auditors to distribute legal obligations across business units and/or personnel with different roles and technical capabilities. This framework improves accountability by integrating traceability throughout the policy and requirements lifecycle. We illustrate the framework within the context of a concrete healthcare scenario in which obligations incurred from the Health Insurance Portability and Accountability Act (HIPAA) are delegated and refined into software requirements. Additionally, we show how auditing mechanisms can be integrated into the framework and how auditors can certify that specific chains of delegation and refinement decisions comply with government regulations.     

A SysML-based approach to traceability management and design slicing in support of safety certification: Framework,tool support,and case studies

ContextTraceability is one of the basic tenets of all safety standards and a key prerequisite for software safety certification. In the current state of practice, there is often a significant traceability gap between safety requirements and software design. Poor traceability, in addition to being a non-compliance issue on its own, makes it difficult to determine whether the design fulfills the safety requirements, mainly because the design aspects related to safety cannot be clearly identified.ObjectiveThe goal of this article is to develop a framework for specifying and automatically extracting design aspects relevant to safety requirements. This goal is realized through the combination of two components: (1) A methodology for establishing traceability between safety requirements and design, and (2) an algorithm that can extract for any given safety requirement a minimized fragment (slice) of the design that is sound, and yet easy to understand and inspect.MethodWe ground our framework on System Modeling Language (SysML). The framework includes a traceability information model, a methodology to establish traceability, and mechanisms for model slicing based on the recorded traceability information. The framework is implemented in a tool, named SafeSlice.ResultsWe prove that our slicing algorithm is sound for temporal safety properties, and argue about the completeness of slices based on our practical experience. We report on the lessons learned from applying our approach to two case studies, one benchmark and one industrial case. Both studies indicate that our approach substantially reduces the amount of information that needs to be inspected for ensuring that a given (behavioral) safety requirement is met by the design.     

A logical approach to systems engineering artifacts: semantic relationships and dependencies beyond traceability—from requirements to functional and architectural views

Not only system assurance drives a need for semantically richer relationships across various artifacts, work products, and items of information than are implied in the terms “trace and traceability” as used in current standards and textbooks. This paper deals with the task of working out artifacts in software and system development, their representation, and the analysis and documentation of the relationships between their logical contents—herein referred to as tracing and traceability; this is a richer meaning of traceability than in standards like IEEE STD 830. Among others, key tasks in system development are as follows: capturing, analyzing, and documenting system-level requirements, the step to functional system specifications, the step to architectures given by the decomposition of systems into subsystems with their connections and behavioral interactions. Each of these steps produces artifacts for documenting the development, as a basis for a specification and a design rationale, for documentation, for verification, and impact analysis of change requests. Crucial questions are how to represent and formalize the content of these artifacts and how to relate their content to support, in particular, system assurance. When designing multi-functional systems, key artifacts are system-level requirements, functional specifications, and architectures in terms of their subsystem specifications. Links and traces between these artifacts are introduced to relate their contents. Traceability has the goal to relate artifacts. It is required for instance in standards for functional system safety such as the ISO 26262. An approach to specifying semantic relationships is shown, such that the activity of creating and using (navigating through) these relationships can be supported with automation.     

基于SWRL的软件需求一致性验证方法

需求质量已经成为确保软件项目成功的一个重要因素,对复杂软件系统的需求进行检查和验证,是需求工程中非常重要的工作。在基于领域本体的需求获取和分析等相关工作基础上,提出了一种基于本体和语义规则的需求一致性验证方法,将自然语言描述的需求分解成若干结构良好的最小需求项,使用领域本体的概念模型对其进行形式化和结构化的表示。通过领域本体中的知识来映射需求语义,采用语义万维网规则语言（SWRL）来定义需求一致性验证的推理规则,并通过实例对此方法进行了分析和验证。     

Graph-based traceability: a comprehensive approach

In recent years, traceability has been globally accepted as being a key success factor of software development projects. However, the multitude of different, poorly integrated taxonomies, approaches and technologies impedes the application of traceability techniques in practice. This paper presents a comprehensive view on traceability, pertaining to the whole software development process. Based on the state of the art, the field is structured according to six specific activities related to traceability as follows: definition, recording, identification, maintenance, retrieval, and utilization. Using graph technology, a comprehensive and seamless approach for supporting these activities is derived, combining them in one single conceptual framework. This approach supports the definition of metamodels for traceability information, recording of traceability information in graph-based repositories, identification and maintenance of traceability relationships using transformations, as well as retrieval and utilization of traceability information using a graph query language. The approach presented here is applied in the context of the ReDSeeDS project (Requirements Driven Software Development System) that aims at requirements-based software reuse. ReDSeeDS makes use of traceability information to determine potentially reusable architectures, design, or code artifacts based on a given set of reusable requirements. The project provides case studies from different domains for the validation of the approach.     

Requirements engineering for e-business advantage

As a means of contributing to the achievement of business advantage for companies engaging in e-business, we propose a requirements engineering framework that incorporates a business strategy dimension. We employ Jackson’s Problem Frames approach, goal modeling, and business process modeling (BPM) to achieve this. Jackson’s context diagrams, used to represent business model context, are integrated with goal models to describe the requirements of the business strategy. We leverage the paradigm of projection in both approaches as a means of simultaneously decomposing both the requirement and context parts, from an abstract business level to concrete system requirements. Our approach maintains traceability to high-level business objectives via contribution relationship links in the goal model. We integrate use of role activity diagrams to describe business processes in detail where needed. The feasibility of our approach is shown by a well-known case study taken from the literature.     

A knowledge encapsulation approach to ontology modularization

The development of monolithic ontologies for complex domains may face various challenges in reasoning and implementation. The notion of modularity can be employed for developing more efficient ontologies, especially in distributed environments. In this paper, we introduce a framework for developing ontologies in a modular manner. We describe the interface-based modular ontology formalism, (IBF), which theoretically supports the framework. The main feature of the framework is its support for knowledge encapsulation, i.e., it allows ontologies to define their main content using well-defined interfaces, such that their knowledge bases can only be accessed by other ontologies through these interfaces. An important implication of the proposed framework is that ontology modules can be developed completely independent of each other’s signature and languages. Such modules are free to only utilize the required knowledge segments of the others. We also investigate the issues of inconsistency in the proposed modular ontology framework. We provide solutions for isolating inconsistent ontology modules from the other parts of a modular ontology and also resolve inconsistencies which may be arisen by integrating consistent knowledge bases.     

Requirements traceability: Theory and practice

Current literature as well as standards that mandate requirements traceability do not provide a comprehensive model of what information should be captured and used as a part of a traceability scheme, leading to wide variation in the quality and usefulness of traceability practice across systems development efforts. In this paper, we present a framework for representing and developing a traceability scheme. The experiences of an organization using traceability as an important component of a quality software engineering process are discussed. Models describing the traceability practice in the organization, as well as issues and lessons learned, both from organizational and technical perspectives, from implementing a comprehensive traceability practice are presented.     

Ontology oriented programming in go!

In this paper we introduce the knowledge representation features of a new multi-paradigm programming language called go! that cleanly integrates logic, functional, object oriented and imperative programming styles. Borrowing from L&O [1] go! allows knowledge to be represented as a set of labeled theories incrementally constructed using multiple-inheritance. The theory label is a constructor for instances of the class. The instances are go!’s objects. A go! theory structure can be used to characterize any knowledge domain. In particular, it can be used to describe classes of things, such as people, students, etc., their subclass relationships and characteristics of their key properties. That is, it can be used to represent an ontology. For each ontology class we give a type definition—we declare what properties, with what value type, instances of the class have—and we give a labeled theory that defines these properties. Subclass relationships are reflected using both type and theory inheritance rules. Following [2], we shall call this ontology oriented programming. This paper describes the go! language and its use for ontology oriented programming, comparing its expressiveness with Owl, particularly Owl Lite[3]. The paper assumes some familiarity with ontology specification using Owl like languages and with logic and object oriented programming.     

模糊Jena的研究

用Jena[11]建立的本体中概念及其关系都是确定的,但是,现实世界中事物及其关系往往具有模糊性且这种模糊性会随着事物的发展而变化.为了将Web上资源及其关系的模糊性表示出来,在RDF[9]的三元组(主体、谓词、客体)中的谓词部分加入一个表示谓词的模糊性的权值,提出一个新的概念-模糊资源描述框架(FRDF,Fuzzy ...     

Modelling residual value risk through ontology to address vulnerability of PPP project system

For facilitating the management of Residual Value Risk (RVR) in Public Private Partnership (PPP) projects, an ontology-based model is established to describe the generation process and complex relationships of RVR. An ontology-based approach is proposed to analyze the RVR in PPPs, which is a framework addressing the vulnerability and a knowledge-based modeling for RVR management. The RVR ontology model is composed of class of Project, Risk, and Vulnerability, as well as taxonomy of risk factors for risk sources (RS), risk events (RE), risk consequences (RC), exposure (V1), resilience (V2) and sensitivity (V3). Meanwhile, different relationships among taxonomies, classes and individuals are expressed in model. Moreover, the object properties for class project and the object properties of inherited/non-inherited relationships are defined. Meanwhile, project-based, risk-based, and vulnerability-based datatype property are further described. Then a real individual is established by using the ontology editing software Protégé. The proposed RVR ontology model can be used to visualize and manipulate various representations in RVR management as well as to implement the work of risk reasoning and analyzing. The proposed RVR ontology framework provides a useful framework to systematize different knowledge of RVRs in PPP projects, in which the related knowledge can be described clearly and effectively. Moreover, the proposed framework can enhance data process function and improve the analysis of RVR probability and vulnerability in PPP projects through sharedness and transferability of RVR knowledge provided by ontology-based RVR model for different stakeholders in PPP projects.     

Toward reference models for requirements traceability

Requirements traceability is intended to ensure continued alignment between stakeholder requirements and various outputs of the system development process. To be useful, traces must be organized according to some modeling framework. Indeed, several such frameworks have been proposed, mostly based on theoretical considerations or analysis of other literature. This paper, in contrast, follows an empirical approach. Focus groups and interviews conducted in 26 major software development organizations demonstrate a wide range of traceability practices with distinct low-end and high-end users of traceability. From these observations, reference models comprising the most important kinds of traceability links for various development tasks have been synthesized. The resulting models have been validated in case studies and are incorporated in a number of traceability tools. A detailed case study on the use of the models is presented. Four kinds of traceability link types are identified and critical issues that must be resolved for implementing each type and potential solutions are discussed. Implications for the design of next-generation traceability methods and tools are discussed and illustrated     

Requirements traceability in model-driven development: Applying model and transformation conformance

The variety of design artifacts (models) produced in a model-driven design process results in an intricate relationship between requirements and the various models. This paper proposes a methodological framework that simplifies management of this relationship, which helps in assessing the quality of models, realizations and transformation specifications. Our framework is a basis for understanding requirements traceability in model-driven development, as well as for the design of tools that support requirements traceability in model-driven development processes. We propose a notion of conformance between application models which reduces the effort needed for assessment activities. We discuss how this notion of conformance can be integrated with model transformations.     

一种构造OWL本体的方法研究

在该文中,首先讨论了3种最常见的抽象(即包含、聚集和联系)以及他们在本体中含义,然后分析并用实例演示了3种抽象的OWL实现方法。当所有的语义联系都被识别和描述后,就产生了OWL本体的主干部分(即分类、对属性的约束、以及分类间的关系)。并提出了一种支持本体构造的语义分析方法,该方法可以识别和定义概念间的语义联系,并将概念间的语义联系映射或转换成OWL原语。     

Understanding ontology evolution: A change detection approach

In this article, we propose a change detection approach in the context of an ontology evolution framework for OWL DL ontologies. The framework allows ontology engineers to request and apply changes to the ontology they manage. Furthermore, the framework assures that the ontology and its depending artifacts remain consistent after changes have been applied. Innovative is that the framework includes a change detection mechanism that allows generating automatically a detailed overview of changes that have occurred based on a set of change definitions. In addition, different users (such as maintainers of depending artifacts) may have their own set of change definitions, which results into different overviews of the changes, each providing a different view on how the ontology has been changed. Using these change definitions, also different levels of abstraction are supported. Both features will enhance the understanding of the evolution of an ontology for different users.     

CFinder: An intelligent key concept finder from text for ontology development

Key concept extraction is a major step for ontology learning that aims to build an ontology by identifying relevant domain concepts and their semantic relationships from a text corpus. The success of ontology development using key concept extraction strongly relies on the degree of relevance of the key concepts identified. If the identified key concepts are not closely relevant to the domain, the constructed ontology will not be able to correctly and fully represent the domain knowledge. In this paper, we propose a novel method, named CFinder, for key concept extraction. Given a text corpus in the target domain, CFinder first extracts noun phrases using their linguistic patterns based on Part-Of-Speech (POS) tags as candidates for key concepts. To calculate the weights (or importance) of these candidates within the domain, CFinder combines their statistical knowledge and domain-specific knowledge indicating their relative importance within the domain. The calculated weights are further enhanced by considering an inner structural pattern of the candidates. The effectiveness of CFinder is evaluated with a recently developed ontology for the domain of ‘emergency management for mass gatherings’ against the state-of-the-art methods for key concept extraction including—Text2Onto, KP-Miner and Moki. The comparative evaluation results show that CFinder statistically significantly outperforms all the three methods in terms of F-measure and average precision.     

语义网服务中的本体集成框架

分析语义网服务中存在的各种本体异构,明确语义网服务中本体集成的主要研究方向.在此基础上,提出一个语义网服务模型下的本体集成框架,讨论其中数据层中介器和Web服务中介器的结构并阐明其工作机制,为全面解决语义网服务环境下的本体集成问题提供了一种新的思路.