Home-grown CASE tools with XML and XSLT

This paper demonstrates an approach to software generation where xml representations of models are transformed to implementations by XSLT style sheets. Although XSLT was not primarily intended for this use, it serves quite well. There are only few problems in this approach, and we identify these based on our examples

CHARACTERISTICS AND EVALUATION METHODS OF THE CASE TOOLS

The acronym CASE – Computer Assisted Software Engineering – is the term used to indicate a collection of methods, tools and processes used in the development of software products with the assistance of the computer.IPSE

Providing Automatic Support for Heuristic Rules of Methods

In method-based software development, software engineers create artifacts based on the heuristic rules of the adopted method. Most CASE tools, however, do not actively assist software engineers in applying the heuristic rules. To provide an active support, the rules must be formalized, implemented and integrated within the framework of current CASE tools. In this paper we describe an approach for formalizing the heuristic rules of methods

Perancangan Case Tools untuk Diagram Use Case, Activity, dan Class untuk Permodelan Uml Berbasis Web Menggunakan HTML5 dan PHP

This study is intended to generate an application tools (CASE tools) that allows a software developer to create a modeling system design using Unified Modeling Language (UML), especially in making use case, activity or class diagrams more quickly and easily. The tools developed will also facilitate developers in doing UML modeling by accessing the network through a web-based internet application. With the web-based applications, the users require only a browser and an internet connection to use this application. This application also helps developers to understand of how to make UML diagrams correctly and good. In this research traditional methods Scrum model is used. Scrum method is Agile methods that is a process to cultivate software easily and can be developed in accordance with the development of information technology. Scrum is using empirical methods or in other words every stage in it involves inspection and adaptation

Constraint specification by example in a Meta-CASE tool

CASE tools are very helpful to software engineers in different ways and in different phases of software development. However, they are not easy to specialise to meet the needs of particular application domains or particular software modelling requirements. Meta-CASE tools offer a way of providing such specialisation by enabling a designer to specify a tool which is then generated automatically. Constraints are often used in such meta-CASE tools as a technique for governing the syntax and semantics of model elements and the values of their attributes. However, although constraint definition is a difficult process it has attracted relatively little research attention. The PhD research described here presents an approach for improving the process of CASE tool constraint specification based on the notion of programming by example (or demonstration). The feasibility of the approach will be demonstrated via experiments with a prototype using the meta-CASE tool Diagram Editor Constraints System (DECS) as context

CASE Tools for IT-System Integration

Proceedings of 14th International Multi-Conference on on Advanced Computer Systems ACS-AISBIS 2007, Szczecin, Poland, 17-19 Oct. 2007The article deals with the compare of standard and new suggested information system (IS) development logical stages. Standard and suggested stages are integrated, new CASE-tool is developed for high-quality IS development in the shortest terms support. The work includes some new and fundamental approaches and suggests specific concepts to IS development

A structured approach to integrate heterogeneous case tools

Multiple CASE tools that support systems analysis and design are available today. These tools are becoming indispensable in its support for the systems development process, although the support varies in term of the methods that are supported. Heterogeneous CASE tools, i.e. CASE tools that support the conventional system development paradigm on the one hand and CASE tools that support the object-oriented development paradigm on the other hand, need to be integrated to support system development in both paradigms, or to enable a change-over from one development paradigm to the other. Although standards and frameworks for tool integration are emerging, a structured approach or method to integrate heterogeneous CASE tools is required. This poster proposes the CUBE approach to integrate heterogeneous CASE tools

Safe and Verifiable Design of Concurrent Java Programs

The design of concurrent programs has a reputation for being difficult, and thus potentially dangerous in safetycritical real-time and embedded systems. The recent appearance of Java, whilst cleaning up many insecure aspects of OO programming endemic in C++, suffers from a deceptively simple threads model that is an insecure variant of ideas that are over 25 years old [1]. Consequently, we cannot directly exploit a range of new CASE tools -- based upon modern developments in parallel computing theory -- that can verify and check the design of concurrent systems for a variety of dangers\ud such as deadlock and livelock that otherwise plague us during testing and maintenance and, more seriously, cause catastrophic failure in service. \ud Our approach uses recently developed Java class\ud libraries based on Hoare's Communicating Sequential Processes (CSP); the use of CSP greatly simplifies the design of concurrent systems and, in many cases, a parallel approach often significantly simplifies systems originally approached sequentially. New CSP CASE tools permit designs to be verified against formal specifications\ud and checked for deadlock and livelock. Below we introduce CSP and its implementation in Java and develop a small concurrent application. The formal CSP description of the application is provided, as well as that of an equivalent sequential version. FDR is used to verify the correctness of both implementations, their\ud equivalence, and their freedom from deadlock and livelock