CASE工具国外使用问题及我们应采取的相应对策

本文针对国外在使用计算机辅助软件工程（CASE）工具时存在的CASE无用现象原因的分析,结合我国的具体情况,提出了一些相应的对策以将CASE工具在我国软件行业应用时的问题减少到最小。     

计算机辅助软件工程研究

计算机辅助软件工程(CASE)是目前计算机工业界和学术界研究的热点之一。本文在分析总结近年来 CASE 研究的基础上,以几个典型的 GASE 系统为背景,讨论了 CASE 的基本概念、结构框架、工具等。并研究了 CASE 从工具、到环境、进而成为一门系统开发方法学的演变过程,以及工具技术的发展对方法学研究的冲击和挑战。本文提出的观点是:CASE 是一个广义的、发展中的概念;CASE 是一个以工具和自动化开发环境为基础的方法学的概念;CASE 工具是指一个不断丰富和完善着的软件工具的集合的概念;和 CASE 库是 CASE 的核心和围绕 CASE 库来展开 CASE 研究的概念。这些都是作者近年来研究总结的结果,可作为进一步开展 CASE 研究的参考,亦可作为实际开发适合我国国情的 CASE系统时借鉴。     

CASE工具功能分析与研究

计算机辅助软件工程提供了一整套的辅助软件开发各个生命过程中的工具。本文主要通过CASE工具在药物批发系统开发过程中数据库建模功能,讨论CASE工具在软件开发中所起的作用,即使用CASE工具对系统进行建模,可以缩短系统开发周期并提高系统质量。     

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

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

集成化CASE

近几年来,随着计算机辅助软件工程(CASE)工具的发展,CASE 的研究和开发重点已从确保各 CASE 工具的正常工作转移到了确保各个不同厂家的 CASE 工具的协同工作,因而集成成为开发和维护 CASE 工具的关键技术。目前,国外许多著名的软、硬件公司都纷纷投资于集成 CASE 的研究,并提出了各种各样的CASE 策略和框架,随之也应运而生了一些国内外的 CASE 标准。本文根据 Ronald J.Jorman 和Minder Chon 发表在 IEEE Software 1992.3上的两篇文章编写而成,以有助于国内集成化 CA-SE。     

Meta—CASE技术的探讨

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

CASE方法、工具、环境以及应用研究

本文是作者在参考文献[1]有关CASE专题研究报告基础上形成的。文章就CASE方法、工具、环境及应用等几方面展开讨论,参考了国内外有关CASE的资料并实际考查和解剖了若干实际系统,从理论和实践两个方面进行了分析、归纳、和总结。它对于我们尽快的熟悉和了解CASE,了解迄今为止形形色色的CASE的发展状况,开发适合我国国情的CASE产品都有一定的参考价值。     

日本软件开发CASE工具的发展

本文就CASE工具在日本产生的背景以及CASE工具的定义加以介绍,并从支持对象和支持的构成这两方面,分析了CASE环境对日本技术发展的倾向,给出一些示例和对它的评价,最后简单地叙述CASE环境的未来。     

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

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

面向MIS的CASE工具中DFD编辑处理系统的设计与实现

管理信息系统(MIS)开发具有周期长、投资大、变化频繁、通用性低等特征,MIS 开发领域中的软件危机现象表现得尤为突出,因此,对 CASE工具的需求也就越显得迫切。据统计,面向 MIS的 CASE 国际市场1989年已达到5.5亿美元,5倍于面向工程的 CASE 市场。面向 MIS 的 CASE 工具首先要能支持 MIS 需求描述,即支持系统分析和初步设计,进一步将支持详细设计和软件代码生成,直至全面项目管理综合。根据上述支持阶段的区别,这些工具常称为第一代(上游)、第二代(下游)以及第三代 CASE 工具。MIS 成功开发的基础是正确的需求描述,其有力工具之一是数据流程图(DFD),它是计算机类技术人员与管理类技术人员实现通讯交流的最方便     

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.     

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.     

智能CASE工具设计

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

MAKING CASE AN ORGANIZATIONAL REALITY

Commercial CASE tools have limited capability in team settings that impairs their usefulness and applicability in many organizations. Organizational change issues associated with assimilating CASE tools are also not adequately addressed in most corporations. This article makes recommendations for the resolution of these issues so that organizations can adopt CASE tools and implementation strategies that deliver productivity enhancement to the software development process.     

Towards ANSI C Program Slicing using XML

In this paper, we consider ANSI C program slicing using XML (Extensible Markup Language). Our goal is to build a flexible, useful and uniform data interchange format for CASE tools, which is a key issue to make it much easier to develop CASE tools such as program slicers. Although XML has a great potential for such data interchange formats, we first point out that there are still a lot of challenging problems to be solved. Then, as a first step to our goal, we introduce ACML (ANSI C Markup Language), which describes the syntactic structure and static semantics for ANSI C code. In our preliminary experiment, we had a good result; it took only 0.5 man-month to implement Weiser's slicer based on ACML, whereas it took about 2 man-months to implement an ANSI C parser and static semantics analyzer of XCI (Experimental C Interpreter).     

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     

Computer-aided software engineering and Ada -- The technological marriage of the decade

Computer-Aided Software Engineering (CASE) tools and Ada language compilers are now available for both mainframes and Personal Computers (PCs). Although CASE methodologies have existed since the early 1970s and the use of Ada has been required by the Department of Defense since 1985, only recently have CASE and Ada become of serious interest to engineers.

This paper identifies the capabilities of PC-based CASE software, the reasons for combining CASE with Ada, and the impact of CASE and Ada on research and teaching in the areas of Industrial and Computer Engineering. Based on the authors' first-hand experience, the advantages and/or disadvantages of several CASE tools and Ada environments will be discussed. Other topics addressed include the meanings of related terminology (e.g., object-oriented programming, design methodologies) and the future ramifications of CASE and Ada on the software engineering community.