基于本体的特定领域软件体系结构设计的研究

随着软件重用技术的不断发展和成熟，软件重用巳从代码级逐步提高到系统级，特定领域的软件体系结构设计是系统级软件重用的重要研究内容之一。为了进一步提高软件重用性和建立一个理想的软件体系结构，文中对特定领域软件体系结构、本体进行了基本分析，介绍了本体在特定领域软件体系结构设计中的应用研究，从而，提出了一个体系结构与实际应用相结合有效途径。     

实施一个面向对象框架的方法

软件重用是在软件开发中避免重复劳动的解决方案，通过软件重用，可心提高软件开发的效率和质量。然而通常的一些重用技术如使用类库等仍然不能满足对重用的要求。一个面向对象的框架是针对某些特定领域的一些组件的整合，它从更高的层次和更大的规模来软件重用。它不仅重用了代码，而且重用了分析和设计，以求更好地提高效率和质量。该文主要从方法学的角度讨论如何实施一个面向对象的框架（Object-Oriented Framework,简称为OOF）的方法，同时介绍国内外在面向对象框架领域的一些研究和实践活动，并对如何加强相关领域的研究提出一些思路。     

基于Java平台的通用构件库的研究与设计

为提高软件的复用程度，采用了基于领域工程的开发方法，提出了领域信息系统设计体系结构和软件构架．重点讨论了领域信息系统模型结构和通用构件库的设计，初步实现了通用构件库中对构件的标识、验证和分类功能，并在组件模型JavaBeans支持下，实现了构件库分析过程的UML描述。通用构件库具有类继承度高、类耦合度低、类封装性高、类多态性低、构件的方法重用效率和类重用效率均比较高等特点并为快速重构应用系统提供了技术上的保证。     

软件重用技术研究

目前软件重用技术已经成为内容非常广泛的研究领域,是当今软件工程领域中的一个研究热点。文中重点论述了目前研究得较多且应用较广泛的基于构件的软件重用技术,指出目前软件重用技术中存在的带有普遍性的问题,针对一些流行的关于软件重用的模糊、错误的认识进行了分析,并提出一些观点。     

基于本体的特定领域软件体系结构设计的研究

随着软件重用技术的不断发展和成熟,软件重用已从代码级逐步提高到系统级,特定领域的软件体系结构设计是系统级软件重用的重要研究内容之一。为了进一步提高软件重用性和建立一个理想的软件体系结构,文中对特定领域软件体系结构、本体进行了基本分析,介绍了本体在特定领域软件体系结构设计中的应用研究,从而,提出了一个体系结构与实际应用相结合有效途径。     

基于代数规格说明的软件构件重用方法

软件重用的关键是构造可重用的构件库中合适构件重用的方法，文中提出了采用基于代数规格说明的形式化方法来表示软件构件，并给出可重用构件进行抽取，修改的规格说明匹配法，在考虑了精确匹配算法的基础上，特别针对构件抽取着重提出了弱精确匹配方法。     

领域分析方法及技术的讨论

本文讨论领域分析方法，说明领域分析方法在软件重用技术中的应用和作用，企图通过这些方法来揭示领域内各个应用系统的公性和差异，以及所有应用系统都适应的参考体系结构模型。文章通过三个不同层次对领域及分析过程的讨论，提出一个一般的领域分析实施过程框架，这将有利于领域分析活动的分类和管理，也为领域分析的标准化提供了一种参考解决方案。     

产品线工程理论应用与研究

产品线工程（Product Line Engineering）是运用软件重用思想的一种软件开发方法,它属于一种大粒度的软件复用方式,用于开发相同领域的类似产品过程。由于PLE强调针对特定产品集合的领域开发和面向重用技术,所以能有效地提高软件产品的开发效率和质量,降低软件开发成本。文中介绍了PLE理论,着重研究产品线模型、开发模式、生命周期和体系结构,介绍领域工程和应用工程在生命周期内部的交互作用。通过产品线开发周期分析和比较出PLE在系统开发过程中的特点,最后介绍PLE在HIS系统中的开发应用。     

知识系统的知识重用方法

KADS方法的主要贡献是提出了层次化的知识模型，这有助于领域知识和PSM的重用。但是，要真正实现领域知识和PSM的重用，还需要引入本体来实现各层次间的灵活配置，将相互独立的层次紧密地联系在一起，共同组成一个完整的系统。文中介绍了知识系统的本体的种类及其可重用性，讨论了在知识系统中引入本体以实现系统知识重用的方法。     

基于范例推理的CAD软件可重用技术的研究

基于软件重用技术与范例基技术在原理，在模具CAD领域软件的工具箱式CASE环境的研制中，通过范例基推理技术实现了CAD软件可重用机制，提出了CAD软件重用的范例定义，导出了范例推理算法，并给出范例推理可重用机制的功能模型。     

域分析:为软件重用产生有用的模型

软件重用被视为解决软件危机,提高软件生产率和质量的有效途径,近年来的软件重用研究的结果表明,基于体系结构,物定域的重用能够有很大的改进。     

A Knowledge-Based Software Engineering Environment for reusable software requirements and architectures

This paper describes a prototype Knowledge-Based Software Engineering Environment used to demonstrate the concepts of reuse of software requirements and software architectures. The prototype environment, which is application-domain independent, is used to support the development of domain models and to generate target system specifications from them. The prototype environment consists of an integrated set of commercial-off-the-shelf software tools and custom developed software tools.The concept of reuse is prevalent at several levels of the domain modeling method and prototype environment. The environment itself is domain-independent thereby supporting the specification of diverse application domain models. The domain modeling method specifies a family of systems rather than a single system; features characterize the variations in functional requirements supported by the family and individual family members are specified by the features they are to support. The knowledge-based approach to target system generation provides the rules for generating target system specifications from the domain model; target system specifications, themselves, may be stored in an object repository for subsequent retrieval and reuse.     

星载软件复用技术探讨

星载软件的开发效率是制约卫星研制能力的因素之一,研究星载软件复用技术就是为了提高星载软件的开发效率和软件的质量;文中对星载软件复用的现状进行了分析,指出了影响星载软件复用的技术因素,探讨了实施星载软件复用的方法,并以举例的方式重点阐述了如何以领域工程的方式对星载软件进行领域分析、构造可复用构件和建立软件复用库;最后,介绍了软件沿用这一特殊的星载软件复用形式,这些方法都已进人实践阶段,具有一定的应用前景.     

基于本体的领域分析

软件复用被认为是改善软件质量和提高软件生产力最有希望的技术。为了支持复用,软件开发过程必须考虑两个方面的问题:为复用开发和用复用开发。本体逐渐成为构建信息系统、提供知识共享和复用的重要机制。领域分析是软件复用工程中最重要的工作。本课题利用本体的概念,讨论了领域分析技术中的领域本体的概念、领域本体的形式化描述,本体模型的UML表达,并给出基于本体的领域分析过程,以期对软件复用工程的领域分析过程有所改进。     

Analogy-based domain analysis approach to software reuse

Domain analysis is an expansion of conventional requirements analysis. Domain analysis can support effective software reuse. However, domain analysis is time consuming and is limited to a particular application area. Analogical approaches to software reuse, on the other hand, often occur across domains. Analogical problem solving is a process of transferring knowledge from a well-understood base domain to a new target problem area. Analogy can facilitate software reuse for poorly understood problems or new application areas. Analogy shares similar concepts with reuse and some analogy theories have been applied to software reuse. However, current research on software analogy often overlooks the importance of analysis for the base domain and does not consider some critical aspects of analogy concepts. Reuse must be based on high quality artifacts, especially reuse across domains. This paper presents an approach to integrate domain analysis and analogy methods. In our view, domain analysis and software analogy have complementary roles. Domain analysis is regarded as a process to identify and supply necessary information for analogical transfer. Software analogy can provide the analyst with similar problems and solutions to reuse previous domain analysis knowledge or artifacts for a new domain. This paper presents case studies to demonstrate the increase of efficiency in applying the approach. Evaluation of the approach from various perspectives is also reported.     

Comprehensibility of UML-based software product line specifications

Software Product Line Engineering (SPLE) deals with developing artifacts that capture the common and variable aspects of software product families. Domain models are one kind of such artifacts. Being developed in early stages, domain models need to specify commonality and variability and guide the reuse of the artifacts in particular software products. Although different modeling methods have been proposed to manage and support these activities, the assessment of these methods is still in an inceptive stage. In this work, we examined the comprehensibility of domain models specified in ADOM, a UML-based SPLE method. In particular, we conducted a controlled experiment in which 116 undergraduate students were required to answer comprehension questions regarding a domain model that was equipped with explicit reuse guidance and/or variability specification. We found that explicit specification of reuse guidance within the domain model helped understand the model, whereas explicit specification of variability increased comprehensibility only to a limited extent. Explicit specification of both reuse guidance and variability often provided intermediate results, namely, results that were better than specification of variability without reuse guidance, but worse than specification of reuse guidance without variability. All these results were perceived in different UML diagram types, namely, use case, class, and sequence diagrams and for different commonality-, variability-, and reuse-related aspects.     

基于本体的领域特征建模过程研究

软件复用的研究和实践表明特定领域的软件复用活动相对容易取得成功,这主要是由于领域的内聚性和稳定性。而系统、全面的领域分析是成功的领域级复用活动的前提和关键。在领域分析和建模的相关研究工作中,已在特征建模方法的基础上引入本体作为特征建模的基础。在此基础上对基于本体的领域分析和建模过程进行了研究,提出了一种领域分析和建模方法OBDA（Ontology Based Domain Analysis）。该方法使用专家分析和自动分析方法相结合,分析业务动作之间的分解、泛化、刻面和依赖等关系以及各种关系的可变性,从而得到完整的领域特征模型。     

基于软件产品线的需求分析研究

软件产品线方法是一种面向特定领域的、大规模、大粒度的软件复用技术.在软件产品线的开发过程中,产品线需求分析是软件产品线开发的关键活动之一,软件产品线需求分析奠定了产品线构架的基础.通过分析软件产品线开发过程和软件产品线需求分析的特点,阐述了软件产品线需求分析方法以及软件产品线需求分析的实践风险.以领域分析和建模为切入点,对软件产品线的领域分析、需求建模和用例建模等关键方法和技术进行了重点的研究.     

Saving reuse from the noose: reuse of analogous specifications through human involvement in reuse process

Analogy is proposed as an alternative paradigm for the reuse of specifications during requirements analysis. First, critical determinants of analogies between software engineering problems are discussed in relation to a specification retrieval mechanism. Second, the process of specification reuse is examined. Specification reuse by analogy is knowledge-intensive, hence an important role is proposed for the analyst during specification reuse: analyst involvement would appear necessary to categorize a new problem, select between candidate reusable specifications, and customize the selected specification to the new domain. Finally, a specification reuse tool is proposed that recognises the collaborative nature of reuse by analogy. This tool assists and advises the analyst during reuse founded on cognitive models of analyst behaviour during analogous reasoning and reuse. The prototype version of this intelligent reuse advisor (Ira) is outlined.     

A study of software reuse in NASA legacy systems

Software reuse is regarded as a highly important factor in reducing development overheads for new software projects; however, much of the literature is concerned with cost and labor savings that reuse brings to industrial software development and little is known about the inherent risks associated with reuse, particularly in the case of mission and safety-critical software systems. We present the preliminary findings of a research project geared toward assessing the impact of risk in National Aeronautics and Space Administration (NASA) legacy software in flight control systems. We introduce the concept of context variables and the impact they have on reuse within these legacy systems as well as the genealogy classification models, which provide a simple, concise method of mapping reuse between families of software projects. This research was conducted at Global Science and Technology, Inc. under NASA grant number NCC0NNG06GI57G.