By Topic

Computer-Aided Software Engineering, 1993. CASE '93., Proceeding of the Sixth International Workshop on

Date 19-23 July 1993

Filter Results

Displaying Results 1 - 25 of 42
  • A custodial application generator for use in a CASE tool environment

    Page(s): 325 - 337
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (540 KB)  

    Investigation of the use of CASE tool for data modeling using enhanced entity relationship (EER) diagrams during the analysis and design phase shows that there are challenging opportunities to utilize the data model in the CASE repository. The use of a custodial application (CA), generated solely from a data model and relation definition, is introduced here. A CA is an application for creating, maintaining, and querying the enterprise information which is modeled in the EER diagrams using a CASE tool. The CA is intended as: a facility for discussions between the software developer and the users in order to get user feedback for the applications developed; a facility for verifying whether the data model has represented the enterprise information or not; a starting point for the coding phase; and a final product if the user accepts the limitations of the CA. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Proceedings of 6th International Workshop on Computer-Aided Software Engineering

    Save to Project icon | Request Permissions | PDF file iconPDF (1481 KB)  
    Freely Available from IEEE
  • Author index

    Page(s): 375
    Save to Project icon | Request Permissions | PDF file iconPDF (63 KB)  
    Freely Available from IEEE
  • Title index

    Page(s): 376 - 377
    Save to Project icon | Request Permissions | PDF file iconPDF (86 KB)  
    Freely Available from IEEE
  • From code understanding needs to reverse engineering tool capabilities

    Page(s): 230 - 239
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1012 KB)  

    A major portion of the software maintenance effort is spent on the reverse engineering activity of understanding existing software. If one can learn more about how programmers understand code successfully, one can build better tools to support the understanding process. This contributes to higher quality and improved efficiency of maintenance tasks. An integrated code comprehension model and experiences with it in an industrial setting are presented. Audio-taped, think-aloud reports were used to investigate how well the integrated code comprehension model works during industrial maintenance activities that range from code fixes to enhancements, code leverage, and reuse. The tapes were analyzed for information needs during maintenance activities, and tool capabilities were derived accordingly. The results are presented and discussed View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Towards quality-oriented CASE tools

    Page(s): 18 - 28
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (988 KB)  

    The support of quality assurance activities has been almost forgotten in recent CASE tools. This paper reviews the potential quality aspects to be supported by means of quality-oriented CASE tools, and focuses attention on quality-driven validation (QDV). This method is tied to software development which is based on the active use of software quality characteristics in order to assure congruence with customer needs and is focused especially on object-oriented software. A prototype for a (QDV) support tool is also presented. The prototype illustrates the new characteristics which advanced graphical editors, as parts of CASE tools, should support in the future View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Scaffolding for re-engineering with organizational and technical frameworks [at the IRS]

    Page(s): 240 - 251
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1268 KB)  

    Three studies concerning software reengineering conducted by the US Internal Revenue Service (IRS) in 1991 and 1992 are described. The situation at the IRS-aging, piecemeal information technology systems maintained by a large staff-is familiar to many institutions. Tax records are processed across multiple locations, platforms, computer languages and data file structures. The three software reengineering studies looked at methods, CASE tool support, and a prototype project using reengineering methods and tools. Critical issues were discovered that were broader than the mechanical definitions of methods and tool technology, namely: planning an orderly transition, organizational readiness, and business reengineering. These point to the organizational and technical frameworks which support business practices of software engineering View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Towards CASE tools for prototyping Z specifications

    Page(s): 166 - 173
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (528 KB)  

    A project that aims to develop an animation environment for a formal specification is described. Two CASE tools, one for constructing (i.e., inputing, editing and syntax checking) a formal specification, and the other for executing a formal specification, are described. A case study is used to illustrate the transformation process required to construct a prototype which can be executed to validate requirements and explore their consequences. The feasibility of translating and executing formal specifications is discussed and directions for future work are presented View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Setting priorities in software product quality towards a CASE based instrument

    Page(s): 29 - 33
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (372 KB)  

    The results of a joint effort of researchers and practitioners to develop an instrument for setting priorities in software product quality in the first life cycle phase of software engineering are presented. Contrary to the specification of functional requirements, the identification of software quality factors is hardly supported by CASE methods and tools. Because of the dynamic nature of this prioritization process, the different types of participants involved, and the complex interrelations between software quality factors, CASE tool support is of utmost importance. Implementation of the instrument is suggested in automated business analysis techniques of current (advanced) CASE tools View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Apply meta-models to developing the semantics schema for ObjectMaker

    Page(s): 348 - 352
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (348 KB)  

    Experiences using metamodels of methodologies to develop an unified semantics schema for enhancing ObjectMaker, a CASE tool that supports over 20 analysis and design methodologies, are reported. The developer of the metamodels, using the metamodels as a basis, provided the suggestions to the schemea developers for how to extend and enhance the schema. It is demonstrated that the metamodel of methodologies is a useful tool for handling the complexity of methodologies, easing communications between CASE tool designers, and recording the design rationales View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using virtual subsystems in project management

    Page(s): 144 - 153
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (828 KB)  

    Software project management cannot be performed without a sufficient understanding of the entire software system. When it comes to making informed project-related decisions, management personnel require a high-level understanding of the entire system and in-depth information on selected components. Unfortunately, many software systems are so complex and/or old that such information is not readily available. Reverse engineering-the process of extracting system abstractions and design information from existing software systems-can provide some of this missing information. The authors outline how risk analysis and project management can be improved through the use of virtual subsystems created through reverse engineering View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A generic, knowledge-based re-engineering architecture

    Page(s): 190 - 198
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (840 KB)  

    A generic architecture for semi-automated reengineering and conversion of legacy systems is motivated, devised, applied, and evaluated. The motivation for mere semi-automation (as opposed to full automation) is that perfectly automatic conversion is unattainable and that explicit attention should be paid to handling the residue gracefully. The architecture needs to satisfy a number of specific application-oriented constraints, and depends heavily on the Software Refinery metaprogramming environment for its realization View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Macrotec toolset for CASE-based business modelling

    Page(s): 114 - 118
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (396 KB)  

    A new methodology for the architectural modeling and high-level requirements specification of business processes and information systems has been developed. The Macrotec toolset has been created to support and validate the methodology. Macrotec currently allows for graphical model specification, automatic graphical layout, logical and performance analysis, and hierarchical decomposition. Various tools were built or integrated into Macrotec to support this functionality. Externally, integration is achieved through a seamless user interface, and internally, integration is furthered by one single data representation scheme and a simple yet effective and extensible mechanism for tool interaction. The methodology and the CASE tool development effort that led to Macrotec are described. Macrotec's requirements, design and implementation are discussed, and the development effort is evaluated View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software engineering knowledge for software reuse

    Page(s): 263 - 269
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (448 KB)  

    The types of knowledge that are brought to bear at every stage of the software development life cycle are identified. However, some knowledge, though used, is lost when it is not captured explicitly or embedded within a software artifact. The knowledge encoded in a software artifact as software concepts can be reused. A model is proposed to illustrate the various dimensions of software reuse, namely component granularity, component origin and abstraction levels. This model is related to software reuse in CASE tools, and the degree of knowledge reuse is indicated View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Improving software design quality with ExSpect: An application of CASE-based prototyping in real-world situations

    Page(s): 174 - 177
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (312 KB)  

    ExSpect (Executable Specification Tool) has been developed for the prototyping of software systems with their environment. It is based on high-level Petri nets with hierarchy, which makes it akin to flow diagram techniques. The bottom level uses a typed functional language. ExSpect has been applied in industry, showing promising results with respect to productivity and design quality. A real-world application of ExSpect is described View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • SCALE: Software process-centered CASE environments for system composition and component reuse

    Page(s): 309 - 313
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (412 KB)  

    The European SCALE project is presented. This project aims to develop, demonstrate, and assess a set of advanced CASE process-centered environments for improving the support of system composition strategies explicitly based on the planned and intensive reuse of components View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Ways to CASE: An analysis of selected CASE experiences

    Page(s): 36 - 43
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (660 KB)  

    In the fall of 1991, Swiss companies from all industries were asked to document their CASE experiences with a structured report. Thirteen accounts were published in 1992. Most companies are past the stage of experimentation with CASE. Some of them use CASE quite successfully on rather broad scale, while others do not seem to be able to apply CASE widely despite positive evaluations and test results. The main findings of these reports, some cautionary remarks, and a few recommendations for future CASE users are given View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A blackboard architecture for intelligent assistance in software maintenance

    Page(s): 180 - 189
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (952 KB)  

    System design recovery and impact analysis are critical phases in the process of software maintenance. It is argued that the interdependence of abstraction recovery tools and application domains plays a key role in providing intelligent assistance in software maintenance, and the use of a blackboard model to address the issue of knowledge sources integration is advocated. A software maintenance expert sytem (SMES) based on a blackboard architecture has been developed to evaluate the approach. Explicit links between specification, design and implementation objects have been represented in the blackboard working memory, as well as the design decisions in the abstraction recovery process. These links are then used in the software evolution process to support impact analysis View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An integrated environment for validating conceptual models

    Page(s): 353 - 363
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (828 KB)  

    Conceptual models are constructed as part of the functional requirements specification process for information systems. Since these models are used actively during the design and implementation of the systems, an important task is to make sure that they really represent users' needs and intentions. For this purpose, validation techniques have been introduced. PPP (Phenomena, Processes, Program), an environment in which three different validation techniques, namely, model execution, view generation, and model presentation can be combined, is presented. The PPP language is described along with a simple process control example. The validation techniques are discussed, and, using an example, how the techniques are combined is illustrated. Related work and some tentative conclusions are given View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Evaluation and introduction of the structured methodology and a CASE tool

    Page(s): 48 - 59
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (800 KB)  

    Two experiments conducted to investigate how useful the CASE method (software development based on the structured methodology and supported by upper CASE tools) is and how it can be successfully introduced into software development organizations are described. In the first experiment, sample programs are developed by both the CASE and conventional methods to compare reliability of the developed programs and analysis/design improvement due to learning effect. In the second experiment, the CASE method is introduced and applied to actual software development. Two major conclusions were reached through these experiments: the CASE method enables twice as much program reliability as the conventional method does, and the success or failure of introducing the CASE method largely depends on management factors, especially on developers' maturity View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Strategic reengineering of software: Lifecycle approach

    Page(s): 211 - 220
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1008 KB)  

    Software systems must be constantly upgraded to be in tune with an evolving business environment. Due to the inefficiency of current maintenance methods, many of the old programs do not meet current strategic needs. Common goals for reengineering software have been to improve maintainability of programs and to convert programs into a newer computer, database, or language. A framework for strategic reengineering in which target systems are substantially redesigned in order to meet a company's strategic goals is described. Strategic reengineering is much like redevelopment, accelerated by reuse of information that is extracted from existing, still viable, programs. The impact of a company's strategic plans on software reengineering is discussed, and lifecycle phases of strategic reengineering with CASE are described View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Extending MELBA+ CASE tool: A design artifact maintenance

    Page(s): 90 - 99
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (748 KB)  

    A development of a design artifact maintenance model which is used to extend the MELBA+ CASE tool is described. The aim of such a model is to provide a framework for a design artifacts maintenance system. The model presented will underlie the MELBA+'s specification management system and work coherently with the tool. Providing such maintenance will provide an evolution history of design artifacts View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • CASE user satisfaction-Impact evaluations in user organizations

    Page(s): 66 - 74
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (848 KB)  

    Evaluations of the impact of CASE in user organizations based on data from a combined Danish and Finnish questionnaire study are discussed. How demographic factors, objectives for acquiring CASE, selection criteria, introduction activities, and the internal diffusion of tools relate to impact evaluations of CASE is illustrated using principal component analysis. The study points to organizational aspects rather than technical aspects as critical factors for favorable impacts of CASE View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Providing user-oriented support for software development by formal methods

    Page(s): 156 - 165
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (784 KB)  

    Existing tools for software development by formal methods lack the user-oriented properties necessary to their effective use in software engineering. A strategy for overcoming these deficiencies by interposing a user-oriented front-end editor between the user and the formal method tool itself is proposed. The feasibility of this approach is demonstrated by adapting an existing generic language-based editor to provide a front-end to an existing theorem prover. To cater for the full range of structures which arise in formal methods, a generic model of formal method documents is defined and a corresponding front-end editor for such documents that is capable of real-time interaction with a corresponding variety of tools supporting formal methods is developed as a way of catering to the full range of structures that arise in formal methods View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • GRAS, a graph-oriented database system for (software) engineering applications

    Page(s): 272 - 286
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1512 KB)  

    Modern software systems for application areas like software engineering, CAD or office automation are usually highly interactive and deal with rather complex object structures. For the realization of these systems, a nonstandard database system is needed which is able to efficiently handle different types of coarse- and fine-grained objects (like documents and paragraphs), hierarchical and nonhierarchical relationships between objects (like composition-links and cross-references), and attributes of different size (like chapter numbers and bitmaps). Furthermore, this database system should support the computation of derived data, undo/redo of data modifications, error recovery from system crashes, and version control mechanisms. We describe the underlying data model and the functionality of GRAS (GRAph Storage), a database system which has been designed according to the above-mentioned requirements. The central design decisions concerning its realization are discussed View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.