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

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

工具总线模型研究

CASE环境作为一类复杂的系统软件，其体系结构至关重要。文中在软总线的基础上，从工具集成设施和工具逻辑处理功能相分离的角度，提出了一种抽象的工具总线模型，并对工具总线的基本概念、功能抽象、内部结构、接口规范等方面进行了深入的研究。     

一种基于CORBA规范的工具总线LambdaBus的设计与实现

基于工具总线的CASE(Computer Aided Software Engineering，计算机辅助软件工程)环境结构是CASE环境一种新的发展趋势，文中在一种抽象的工具总线(ToolBus)模型的基础上，对工具总线的实现方式、实现途径等方面展开了进一步的研究，并基于CORBA规范实现了一种工具总线原型LambdaBus，从而验证了工具总线模型的有效性。     

工具接口技术研究

随着CASE环境（Computer Aided Software Engineering Environment)的不断发展，工具间如何协调高效地支持整个软件开发过程显得愈为重要，文中重点研究了CASE环境中工具间的接口技术，对各种类型的接口技术进行了分析和比较，并阐述了工具接口的应用问题。     

一种基于工具总线的CASE集成模型

简要分析了当前CASE环境的集成机制，并给出了一种基于工具总线的工具集成机制的理论架构以及实现。该机制引入了工具适配器对工具总线的底层机制进行封装，满足了系统对集成的应用工具的位置无关性的要求。     

在CASE工具中引入XML视图

从数据库设计的角度出发，在CASE(计算机辅助系统工程)工具中添加了创建XML视图的功能，也就是说在使用CASE对实体及其相互联系建模之后，在创建数据库对象的DDL语句的同时自动的创建此数据库的XML视图．具体的方法是将E-R模型转换为DTD来完成了这个数据库的XML视图的创建，一次性的完成了数据库的设计和此数据库的XML视图的创建，从而避免了程序员为了生成视图而对此数据库进行的二次开发，因此提高了工作效率．     

CASE工具在信息系统开发中的应用研究

本文阐述了基于CASE的系统开发方法与CASE开发环境。以ORACLE DESIGNER／2000为例,详细地说明了CASE工具在系统分析与动态建模、应用程序生成与系统优化、文档集成等方面的使用技巧。     

软件体系结构讲座：（八）体系结构设计工具

本讲介绍几个软件体系结构设计的工具系统,它们是:UniCon(一个体系结构描述的语言和工具集),Ae-sop(一个构造特殊风格的体系结构设计环境)和WRIGHT(一个支持体系结构规格说明的语言)。     

计算机软件开发工具的集成和应用研究

主要探讨了如何针对不同的软件开发机构特点，构造与之相适应的计算机辅助软件工程（CASE）工具支持的集成化开发环境，用以支持软件开发机构的软件开发过程。     

Meta—CASE技术的探讨

Meta－CASE是通过Meta－CASE工具生成CASE工具，形成支持软件开发方法工具集的技术．本文主要就Meta－CASE技术及ToolBuilder技术进行分析和讨论．     

Process integration in CASE environments

Research in CASE environments has focused on two kinds of integration: tool and object. A higher level of integration, process integration, which represents development activities explicitly in a software process model to guide and coordinate development and to integrate tools and objects, is proposed. Process integration uses software process models (SPMs) a process driver, a tool set, and interfaces for both developers and managers to form the backbone of a process-driven CASE environment. The developer's interface, a working environment that lets developers enact an SPM, and the manager's interface which gives managers and analysts the tools to define, monitor, and control the SPMs that developers are working on concurrently are discussed. The Softman environment experiment, an implementation of process-driven CASE environments with existing CASE environments, is reviewed     

CHARMY: A Framework for Designing and Verifying Architectural Specifications

Introduced in the early stages of software development, the Charmy framework assists the software architect in making and evaluating architectural choices. Rarely, the software architecture of a system can be established once and forever. Most likely poorly defined and understood architectural constraints and requirements force the software architect to accept ambiguities and move forward to the construction of a suboptimal software architecture. Charmy aims to provide an easy and practical tool for supporting the iterative modeling and evaluation of software architectures. From an UML-based architectural design, an executable prototype is automatically created. Charmy simulation and model checking features help in understanding the functioning of the system and discovering potential inconsistencies of the design. When a satisfactory and stable software architecture is reached, Java code conforming to structural software architecture constraints is automatically generated through suitable transformations. The overall approach is tool supported.     

Multiuser collaborative work in virtual environment based CASE tool

VRCASE is a virtual environment based Computer Aided Software Engineering (CASE) tool. It provides a 3D multiuser collaborative software modeling environment with automatic object-class abstraction, class diagram generation, and C++ skeleton generation facilities for assisting Object-Oriented software development. It allows multiple concurrent users to model software system collaboratively. To achieve efficient collaborative software development in VRCASE, we have proposed and implemented a Fine-grained locking and notification mechanism together with visual indicators to maintain system consistency among multiple concurrent users. The system evaluation shows that our approach can effectively support multiuser collaborative software design in VRCASE.     

Disaggregating and calibrating the CASE tool variable in COCOMO II

CASE (computer aided software engineering) tools are believed to have played a critical role in improving software productivity and quality by assisting tasks in software development processes since the 1970s. Several parametric software cost models adopt "use of software tools" as one of the environmental factors that affects software development productivity. Several software cost models assess the productivity impacts of CASE tools based only on breadth of tool coverage without considering other productivity dimensions such as degree of integration, tool maturity, and user support. This paper provides an extended set of tool rating scales based on the completeness of tool coverage, the degree of tool integration, and tool maturity/user support. Those scales are used to refine the way in which CASE tools are effectively evaluated within COCOMO (constructive cost model) II. In order to find the best fit of weighting values for the extended set of tool rating scales in the extended research model, a Bayesian approach is adopted to combine two sources of (expert-judged and data-determined) information to increase prediction accuracy. The extended model using the three TOOL rating scales is validated by using the cross-validation methodologies, data splitting, and bootstrapping. This approach can be used to disaggregate other parameters that have significant impacts on software development productivity and to calibrate the best-fit weight values based on data-determined and expert-judged distributions. It results in an increase in the prediction accuracy in software parametric cost estimation models and an improvement in insights on software productivity investments.     

集成CASE的集成模型

本文综述计算机辅助软件工程ＣＡＳＥ概念的发展，从第一代文件系统集成的ＵＮＩＸ环境到９０年代初的基于仓库的ＣＡＳＥ环境．集成技术方面始终围绕数据集成、控制集成、表达集成发展．ＣＡＳＥ的集成还要保证各厂家开发的工具和可重用成分可移植．为此，本文介绍了近代ＣＡＳＥ环境集成的模式，ＣＡＩＳ和ＰＣＴＥ作为集成核心模型的原理，以及发展到８０年代后期信息仓库的由来．信息仓库是ＰＣＴＥ成果的进一步发展，１９８８年ＥＣＭＡ提出以信息仓库为核心的烤面包实现集成模型．它是当今ＣＡＳＥ环境研究开发的基本模型．本文详细论述了信息仓     

基于.NET平台的信息系统开发方法

介绍了软件开发的相关环境、模式以及工具,提出一个基于.NET平台的信息系统的开发框架,以建筑设计项目管理软件开发为实例,对系统设计和实现过程作出技术分析.     

Providing Architectural Languages and Tools Interoperability through Model Transformation Technologies

Many architectural languages have been proposed in the last 15 years, each one with the chief aim of becoming the ideal language for specifying software architectures. What is evident nowadays, instead, is that architectural languages are defined by stakeholder concerns. Capturing all such concerns within a single, narrowly focused notation is impossible. At the same time, it is also impractical to define and use a “universal” notation, such as UML. As a result, many domain-specific notations for architectural modeling have been proposed, each one focusing on a specific application domain, analysis type, or modeling environment. As a drawback, a proliferation of languages exists, each one with its own specific notation, tools, and domain specificity. No effective interoperability is possible to date. Therefore, if a software architect has to model a concern not supported by his own language/tool, he has to manually transform (and, eventually, keep aligned) the available architectural specification into the required language/tool. This paper presents DUALLy, an automated framework that allows architectural languages and tools interoperability. Given a number of architectural languages and tools, they can all interoperate thanks to automated model transformation techniques. DUALLy is implemented as an Eclipse plugin. Putting it in practice, we apply the DUALLy approach to the Darwin/FSP ADL and to a UML2.0 profile for software architectures. By making use of an industrial complex system, we transform a UML software architecture specification in Darwin/FSP, make some verifications by using LTSA, and reflect changes required by the verifications back to the UML specification.     

基于LePUS的设计模式CASE工具的设计与实现

设计模式是软件工程界的热点，在面向对象软件设计中扮演着重要角色，自动化支持设计模式非常必要。为此，以LePUS语言为基础，提出了一个支持设计模式的CASE工具原型模型，该工具支持设计模式代码框架的自动生成，更重要的是该工具可以通过加入新的设计模式而得以扩展。此外，详细分析了实现中的源程序内部表示、设计模式实例化、动态模板生成技术等关键技术。