群件和支持办同工作的CASE工具

协同工作的需要和计算机技术的发展群件的产生和发展提供了条件，协同工作的需要同样体现在软件开发过程中，因此应对支持协同工作的ＣＡＳＥ工具加以研究，而上前国外在这方面所作的工作却比较少。本文从产生背景、定义、分类以及相关领域等几方面对群件进行了简要的介绍，并提出了支持协同工作的ＣＡＳＥ工具的研究方向和途径。     

基于数据库的支持群体工作CAD软件的设计与实现

目前ＣＡＤ系统多是面向单个设计者，而实际的设计工作往往由多个设计者协同完成。ＣＡＤ系统应该支持多个设计者协同工作以提高工作效率。作者采用在现有的ＣＡＤ系统中加入支持设计者协同工作的模块的方法。利用这种方法将ＢＩＣＡＤ中的结构建模模块ＭＯＤＥＬ修改为ＣＷＭＯＤＥＬ，它可支持多个设计者协同工作并能缩短设计周期。实践证明这种方案是可行的。     

群件和支持协同工作的CASE工具

协同工作的需要和计算机技术的发展为群件的产生和发展提供了条件,协同工作的需要同样体现在软件开发过程中,因此应对支持协同工作的CASE工具加以研究,而目前国内外在这方面所作的工作却比较少。本文从产生背景、定义、分类以及相关领域等几方面对群件进行了简要的介绍,并提出了支持协同工作的CASE工具的研究方向和途径。     

青鸟Ⅱ型系统面向对象语言CASEC＋＋的设计和实现

ＣＡＳＥＣ＋＋语言是面向对象的ＣＡＳＥ环境青鸟Ⅱ型系统中设计、实现的一个与Ｃ＋＋完全兼容并支持永久对象的面向对象程序设计语言．在青鸟Ⅱ型系统中，它是对象管理系统ＯＭＳ（ｏｂｊｅｃｔｍａｎａｇｅｍｅｎｔｓｙｓｔｅｍ）的操纵语言和所有集成工具的编程语言，同时也是支持最终用户的通用的编程语言．本文首先简要介绍了ＣＡＳＥＣ＋＋的设计背景．然后，较详细地讨论了ＣＡＳＥＣ＋＋中新引入的语言成份：永久对象；类定义的共享机制；永久对象间的关系描述──链和对象的内容等．最后，给出了实现方法．     

WCEEC--一个基于Web的电子会议系统

介绍了一个基于Ｗｅｂ的电子会议系统ＷＣＥＥＣ的设计及其实现,该系统采用了ｂｒｏｗｓｅｒ／ｓｅｒｖｅｒ与多层ｃｌｉｅｎｔ／ｓｅｒｖｅｒ相结合的结构,可分为实时,异步和临时３种会议工作方式,具有完整的会议管理功能,支持多种会议工具,客户端程序以Ｊａｖａ ａｐｐｌｅｔ的形式实现,用户可通过Ｗｅｂ浏览器下载运行。     

声卡名词解释 EAX

就是环境音效扩展集（Ｅｎｖｉｒｏｎｍｅｎｔａｌ Ａｕｄｉｏ Ｅｘｔｅｎｓｉｏｎｓ）。它的本质是一种依赖于Ｍｉｃｍｓｏｆｔ的ＤｉｒｅｃｔＳｏｅｄ３Ｄ的开放ＡＰＩ，任何人都可以使用这一接口来开发或者在自己的软硬产品中加入对ＥＡＸ的支持。在最新发布的ＥＡＸ３．０中，加入了功能强大、简单易用的可以为每一个单独音源做反射和混响控制、局限反射群等特效设计工具，并为开发者公开了全部的环境音效参数，这对电脑音乐迷具有很大的帮助。声卡名词解释 EAX     

面向对象的实体关系模型(OOER)

实体关系模型（ＥｎｔｉｔｙＲｅｌａｔｉｏｎｓｈｉｐＭｏｄｅｌ简称ＥＲ）是软件系统分析时建立概念性数据模型的有效工具，但软件设计的本质在于数据处理、数据信息及其相应处理的分析应是软件设计的主要目的。ＥＲ模型能将问题空间直接映射成信息实体，但还缺少数据处理分析的支持，本文提出的面向对象ＥＲ模型（ＯＯＥＲ），将原ＥＲ模型扩展成信息模型和处理模型两部分，进一步增强了原ＥＲ模型数据信息的图形表达能力和数据处理分析能力。     

基于AutoCAD信号控制电路绘图及仿真系统的研究

为了解决现在铁路信号控制电路设计软件效率低、功能单一的弊端，以美国的Ａｕｔｏｄｅｓｋ公司１９９２年推出的ＡｕｔｏＣＡＤＲ１２作为主要操作平台，建立了ＶｉｓｕａｌＣ＋＋、Ｅｘｃｅｌ、ＶｉｓｕａｌＢａｓｉｃ、Ｆｏｘｐｒｏ、ＡｕｔｏＬｉｓｐ协同工作的铁路信号控制绘图及仿真软件包。此软件包性能优越、界面友好、操作简单。     

用Borland C＋＋4.5设计Windows应用程序

本文介绍了一种用ＢｏｒｌａｎｄＣ＋４．５提供的Ｂｏｒｌａｎｄ ＡｐｐｌｉｃａｔｉｏｎＥｘｐｅｒｔ（ＡｐｐＥｘｐｅｒｔ）和ＣｌａｓｓＥｘｐｅｒｔ专家系统工具建立Ｗｉｄｎｏｗｓ应用程序的简单方法。分两步进行，首先建立应用程序外壳，然后修改各项，增加新功能，以满足程序的所有要求。     

EDDBMS中的OEDDL与OEDML的研究与实现

ＥＤＤＢＭＳ是自行开发的面向对象的工程数据库管理系统。本文介绍了它的数据库建模语言和操纵语言的设计思想和实现方法，它对ＳＴＥＰ标准的信息建模语言Ｅｘｐｒｅｓｓ的支持。给出了采用面向对象方法实现的ＥＤＤＢＭＳ建模子系统和操纵子系统的总体框架、支持面向对象特征的数据字典的结构以及继承和封装的实现方法     

基于Web服务的协同CASE工具设计

为CASE工具提供协同功能的重要性显而易见.但现有系统功能的实现不是使用ad-hoc的方法就是使用一个特定的群件工具箱,这使得应用程序缺少可扩展性和灵活性.使用Web Service技术及其协议提出一种开发CASE工具的新途径,以解决以上问题.为满足协同工作的完整需求,系统还包括一个版本控制机制和群体意识功能组件.简要介绍这种基于Web Service的体系结构并对核心的设计和实现议题进行描述.     

Open Collaboration within Corporations Using Software Forges

A software forge is a tool platform for collaborative software development, similar to integrated CASE environments. Unlike CASE tools, however, software forges have been designed for the software development practices of the open source community. The authors discuss their experiences using a software forge to bring open source best practices into corporations. They present the design principles and benefits of a firm-internal software forge and include a case study of how one project at SAP benefitted significantly from being on the forge.     

Software development and integration in a computer supported cooperative work environment

This paper presents a prototype computer supported cooperative work (CSCW) environment that supports the engineering design process. In particular, this environment provides collaborative tools that support computer-aided design (CAD) and computer-aided software engineering (CASE). This paper takes an high level look at the system as a whole and then focuses on the method used to implement the CASE support. It addresses how group members can simultaneously work on coding a program and then integrate their work to form a single program inside this environment. © 1998 John Wiley & Sons, Ltd.     

CASE: analysis and design tools

Computer-aided software engineering (CASE) tools are defined, and ten CASE tools are briefly overviewed. Individual presentations on the various tools follow. The focus is on structured analysis, design, and programming. Two of the tools (Cradle and JSP Workbench) are implementations of the Yourdon and Jackson methods for structured analysis, structured design, and programming; three tools (Time Bench, Card Tools, and Prosa) are for real-time systems development; four (Excelerator, Adagen, Smart System, and Software Through Pictures) are general-purpose front-end CASE tools and one (Virtual Software Factory) is a CASE tool for building CASE tools     

The evolution of CASE usage in Finland between 1993 and 1996

The purpose of this paper is to report the evolution of CASE adoption in Finland based on two comparable surveys, the first conducted in spring 1993 and the second in winter 1996/1997. The study uses a process model for innovation adoption, consisting of three stages: conditions for adopting and using CASE tools; adoption and using CASE tools; and consequences of adopting and using CASE tools. At each stage, the paper points out key aspects related to CASE adoption and studies their changes from 1993 to 1996. The analysis of key aspects reveals that not so much has changed in CASE adoption during the time between the two surveys, although the expectations concerning improvements to be brought about by the CASE technology have increased significantly. There is also increased emphasis on tool interfaces and the coverage of the development process both, in the criteria for selecting CASE tools and in performance evaluations. CASE usage has progressed very slowly, if at all. CASE tools are increasingly perceived to lead to intensified project and product standardization and higher end-user participation, but the two surveys did not find any significant change in the perceived impact of CASE technology on the productivity of development or in the quality of software products, and still less in other dimensions of work unit effectiveness.     

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     

计算机辅助软件工程（CASE）工具的选择与采用

CASE工具技术在信息系统的开发中得到了越来越广泛的应用,如何在众多的CASE工具中选择最适用的一种,本文介绍了在CASE工具的选择和采用过程中需要考虑的问题。     

Empirical Evaluation of CASE Tools Usage at Nokia

We presentthe results of a research work targeted to understanding thedomains and consequences of CASE tools usage in Nokia. We aimto evaluate the importance of the various CASE tools features,as rated by our developers, and how well such features are implementedin currently available CASE tools. A structured questionnairewas sent to our most experienced developers and CASE users. Fromthis survey, it emerged that CASE tools support is reputed mostuseful for the following functions: graphical drawing, automaticdocumentation generation and storage of diagrams. The resultshint to a mismatch between the features required by the developersand those offered by CASE products. Further research is neededbefore more definite conclusions can be drawn.     

Now the learning curve affects CASE tool adoption

Part of adopting an industrial process is to go through a learning curve that measures the rate at which the average unit cost of production decreases as the cumulative amount produced increases. It is argued that organizations buy integrated CASE tools only to leave them on the shelf because they misinterpret the learning curve and its effect on productivity. It is shown that learning-curve models can quantitatively document the productivity effect of integrated CASE tools by factoring out the learning costs so that managers can use model results to estimate future projects with greater accuracy. Without this depth of understanding, managers are likely to make less-than-optimal decisions about integrated CASE and may abandon the technology too soon. The influence of learning curves on CASE tools and the adaptation of learning-curve models to integrate CASE are discussed. The three biggest tasks in the implementation of learning-curves in integrated CASE settings, locating a suitable data site, collecting the data, and validating the results, are also discussed     

智能CASE工具设计

本文提出了智能ＣＡＳＥ工具，把用户知识与系统开发人员的知识结合在一起。文章先讨论了智能ＣＡＳＥ工具的设计思想，然后，描述了智能ＣＡＳＥ工具的模型结构。