采用标准数据接口SDAI的CAD／CAM系统集成

如何将ＳＴＥＰ的方法和规范应用于系统开发是解决计算机集成制造系统（ＣＩＭＳ）开发的关键问题之一。集成化ＣＡＤ／ＣＡＭ系统是ＣＩＭＳ的核心，实现将ＣＡＤ的工程设计功能和ＣＡＭ的制造功能的结合。本文讨论通过ＳＴＥＰ的标准数据接口ＳＤＡＩ实现系统集成的集成方法，采用ＳＴＥＰ的数据交换、建模思想，实现了一个产品模型为核心的ＣＡＤ、ＣＡＭ集成系统－ＧＨＣＡＤ（高化ＣＡＤ）。     

面向集成的CAD系统

在ＣＩＭＳ中，集成是关键技术。设计者在不同环境中产生的数据需要相互交换和共享。该文主要介绍设计阶段产生的数据如何与ＣＡＰＰ／ＣＡＭ集成。开发特征造型系统，建立包含零件的几何信息和加工信息的信息模型，最后输出ＳＴＥＰ中性文件，达到ＣＡＤ／ＣＡＰＰ／ＣＡＭ集成。     

STEP信息集成软件工具的设计和实现

ＳＴＥＰ是国际标准化组织ＩＳＯ正在组织开发的应用于计算机集成制造系统（ＣＩＭＳ）信息集成的产品数据表达与交换标准，ＳＴＥＰ不仅是一种规范，更是一种信息集成技术，本文以ＣＡＤ／ＣＡＰＰ／ＣＡＭ系统集成为背景，提出了ＳＴＥＰ信息集成支持工具ＥｘＴｒａ的设计和实现技术，该软件工具已成功且有效地应用于ＣＡＤ／ＣＡＰＰ／ＣＡＭ系统集成中。     

软件工程环境通接口比较

ＣＡＩＳ和ＰＣＴＥ是目前国际上最为成熟的两个通用工具接口标准，也是软件工程环境接口标准化的最有力的两年后选者。本文主要对ＣＡＩＳ和ＰＣＴＥ从结构模型，类型机制，进程管理，事务处理，分布式管理等方面进行了分析比较，并讨论其技术演进以及目前存在的问题，为我国件工程环境接口的开发提供参考。     

软件系统集成中的信息组织

ＰＣＴ和ＣＡＩＳ是两个最著名，最具影响的公共工具接口标准，本文介绍了ＰＣＴＥ和ＣＡＩＳ的背景以及它们的主要技术内容，并详细分析了它们之间在信息组织方面的异同和不足。     

特征模型与CAD／CAM信息集成的研究

特征建模技术是实现ＣＡＤ／ＣＡＭ集成的核心，本文对建立在Ｉ－ＤＥＡＳ之上特征建模的研究为基础，针对板块类零件，提出了基于特征的集成模型总体结构和数据的组织方法，该模型以面为纽带，将零件的几何信息加工工艺信息有机地联系在一起，以便使ＣＡＤ的数据能方便地被ＣＡＰＰ、ＮＣ等后续环节所使用，从而为ＣＡＤ／ＣＡＭ的集成奠定基础。     

GHCAD：一个产品模型为基础的CAD／CAM集成系统

ＳＴＥＰ是关于产品数据表达和交换的国际标准，如何将ＳＴＥＰ的方法和规范应用于系统开发是解决计算机集成制造系统（ＣＩＭＳ）开发的关键问题之一。集成化ＣＡＤ／ＣＡＭ系统是ＣＩＭＳ的核心，实现将ＣＡＤ的工程设计功能和ＣＡＭ的制造功能的结合。本文介绍一个产品模型为基础的ＣＡＤ／ＣＡＭ集成系统－ＧＨＣＡＤ。系统采用ＳＴＥＰ的数据交换、建模思想，以产品模型为核心，通过ＳＴＥＰ的标准数据接口ＳＤＡＩ实现了系统的集成。     

分布式集成中间体CSE／MA的设计与实现

为扩展分布式计算环境，支持系统集成，本开展了基于多ａｇｅｎｔ的分布式集成中间件ＣＳＥ／ＭＡ的研究，试图为应用开发提供一种开发客户／服务器应用的通用开发框架，支持应用于开发方便灵活地建立各种客户／服务器应用。本着首先提出了ＣＳＥ／ＭＡ的框架结构，讨论利用ＣＳＥ／ＭＡ建立客户／服务器应用的组成成分，工作原理和工作过程，其次，讨论ＣＳＥ／ＭＡ的管理核心Ｒｅｇｉｓｔｅｒ所提供的服务及其实现算法，提     

CASE环境下的软硬件设计与开发集成支撑方法论

本文从受援对象入手，讨论ＣＡＳＥ环境集成支撑软硬件设计与开发的方法论问题，包括对受援对象的集成、扩充、追加等综合开发，并以工程开发和管理的细则规范系统──ＥＰＯＳ为例，提出ＣＡＳＥ前后端的自动优化支撑的必要性及规范简化方法论的设想。     

异构网络环境下X.400电子邮件系统的实现

当前电子邮件发展的特点是标准化，ＣＣＩＴＴ和ＩＳＯ联合公布的ＣＣＩＴＴＸ．４００／ＩＳＯ１００２１电子邮件标准为电子邮件的标准化奠定了基础。而Ｘ．４００标准是按照ＯＳＩ参考模型制定的，由于当前ＯＳＩ参考模型推广还不够广泛，因此需要在异构网络环境下实现Ｘ．４００电子邮件系统。本文提出了解决网络异构问题的集成开发平台应其有的特点，结合应用环境介绍了在ＴＣＰ／ＩＰ、ＤＥＣＮＥＴ、ＯＳＩ运输层之上实现集成     

Interfacing Oz with the PCTE OMS: A Case Study of Integrating a Legacy System with a Standard Object Management System

The integration of a legacy system and a standard Object Management System (OMS) is often a very challenging task. This paper details a case study, our experiment in interfacing Oz with the PCTE (Portable Common Tool Environment) Object Management System. Oz is a multi-user process-centered software development environment that has been under development in our lab since 1987, originally under the name Marvel. PCTE is a specification that defines a language-independent interface providing support mechanisms for software engineering environments (SEE). One of the premises of PCTE is that, in theory, an SEE such as Oz can be built (or extended) using the services provided by PCTE. The purpose of our experiment was to study how a legacy system such as Oz can be integrated into a new environment framework, e.g., PCTE. The architecture of the legacy system and the services of the framework are the key factors in the integration approach. Because Oz historically has included a native OMS, our experiment focused on modifying Oz to use the PCTE OMS, which has an open and standard API. This paper describes how several Oz components were changed to interface to the PCTE OMS. The resulting proof-of-concept hybrid system has process control and integration services provided by Oz, and data integration services provided in part by PCTE. We discuss in depth the solutions to the concurrency control problems that arise in such an environment, where Oz and PCTE use different approaches to transaction management (i.e., each has its own transaction manager). The PCTE implementation used in our experiment was the Emeraude PCTE V 12.5.1, and the Oz version was V 1.0.1.     

A framework for integrated CASE

An organizational framework for integrated CASE development and research that is based on the reference model for integrated software-engineering environments being developed by the NIST and the European Computer Manufacturers Association is proposed. Services defined in the reference model permit three forms of integration: data integration, control integration, and presentation integration. The reference model, which describes a wide range of CASE environments, and frameworks, can guide standards development and serve as a basis for educating software engineers. The organizational framework divides systems development and management into three activity levels: IS infrastructure planning and design is undertaken at the enterprise level, systems project management and decisions are made at the project level, and software-development processes are carried out at the individual and team level. The ways in which the organizational framework, which complements the technical framework, can guide the development and deployment of integrated CASE environments, direct future research, and help CASE users select and configure tools in an integrated CASE environment are discussed     

Automating output size and reuse metrics in a repository-basedcomputer-aided software engineering (CASE) environment

Measurement of software development productivity is needed in order to control software costs, but it is discouragingly labor-intensive and expensive. Computer-aided software engineering (CASE) technologies-especially repository-based, integrated CASE-have the potential to support the automation of this measurement. We discuss the conceptual basis for the development of automated analyzers for function point and software reuse measurement for object-based CASE. Both analyzers take advantage of the existence of a representation of the application system that is stored within an object repository, and that contains the necessary information about the application system. We also discuss metrics for software reuse measurement, including reuse leverage, reuse value, and reuse classification that are motivated by managerial requirements and the efforts, within industry and the IEEE, to standardize measurement. The functionality and the analytical capabilities of state-of-the-art automated software metrics analyzers are illustrated in the context of an investment banking industry application that is similar to systems deployed at the New York City-based investment bank where these tools were developed and tested     

Integrated CASE for cleanroom development

An integrated CASE environment for performing cleanroom systems engineering is proposed. The cleanroom integrated CASE environment is viewed as a series of iterative development activities. The fundamental integrating concepts and principles of cleanroom engineering provide a seamless development environment, with no information loss or artificial bridges between activities. It is shown that the integrated CASE environment for cleanroom systems development requires a formal methodology that covers the entire development process, which comprises cleanroom development concepts, a central repository of development information and a set of automated tools that work together transparently through the common repository. Three projects representative of experience in implementation of cleanroom CASE are discussed: a structuring facility for Cobol, a real-time system, and compiler components for a runtime library     

Strategies for integrating CASE environments

An experimental information-system environment, called DAIDA (development assistance for integrated database applications), developed as part of the European Community's ESPRIT program is described. DAIDA goes beyond traditional knowledge-based techniques for CASE by addressing three important dimensions of integration in a process-oriented model: how to handle dependencies among development stages, how to manage the evolving relationship among systems and their technical and social environments, and how to integrate development tasks-from both development in the small, in which the focus is the content of actions and results, and development in the large, which is concerned with object and process management and the collaboration of people involved in developing and using systems. This threefold integration strategy is discussed, along with the DAIDA architecture and a development example. The ConceptBase process information repository, which is used to define the process-oriented integration model, is also discussed     

软件体系结构、应用平台及框架仓库技术

应用平台是新近提出的一种中间件（ｍｉｄｄｌｅｗａｒｅ）技术，其主旨是为应用提供更强大的支持（如提高质量、增加复用、提高生产率、降低维护）。最近几年兴起的软件体系结构研究已为应用平台的研究开发打下了必要的技术基础。ＣＡＳＥ集成工具与环境是应用平台的物理支撑，框架仓库和面向对象组织是应用平台的集成保证。应用平台不仅是新兴的技术和概念，而且具有很大的现实意义和极广阔的应用前景。本文对应用平台和应用平台的关键支撑技术及有关概念（包括：应用平台、软件体系结构和框架仓库等）进行综述，并给出作者的观点。     

TBus：一种CASE环境体系结构风格研究与实现

CASE(Computer Aided Software Engineering计算机辅助软件工程)环境作为一类复杂的系统软件，其体系结构至关重要。本文在工具总线(ToolBus)的基础上，从软件体系结构的角度，提出了一种基于工具总线的CASE环境体系结构风格TBus，对体系结构模型、系统行为进行了形式化描述，以及相应的工具结构模型、工具适配器结构模型、工具集成机制等方面进行了深入的研究与分析。建立TBus体系结构风格，对于促进分布式CASE环境和软件平台开发具有重要的指导意义。     

数据集成技术综述

从现行信息需求出发,介绍了数据集成技术发展的必要性,讨论了已有的数据集成技术,分析了这些技术的优缺点,介绍了网格技术、本体技术两个新的异构数据集成技术。在此基础上给出了本体技术和中间件相结合数据集成解决方案。最后,提出了数据集成方法的发展方向。     

异构分布对象系统集成模型研究

分布对象计算技术为用户提供了方便的分布应用开发工具。然而,随着分布对象计算技术的应用和发展,异构分布对象系统的集成也正在成为急需解决的问题。用户对异构分布对象系统的集成有各种各样的需求,因此提供异构分布对象系统集成的工具也多种多样。文中将现有的异构分布对象系统的集成工具归纳为四种集成模型,并在对它们进行比较的基础上结合应用需求讨论了各种集成模型的适用场合。