An evaluation of object-oriented CASE tools: the Newbridge experience

Author(s):  
T. Church ◽  
P. Matthews
Keyword(s):  
Author(s):  
JUNICHI YAMAMOTO ◽  
AKIHIKO OHSUGA ◽  
SHINICHI HONIDEN

Although many CASE tools for object-oriented methods (OO CASE tools) have been proposed, few, if any, can verify that the constructed analysis and design models actually match the requirements of the system being developed. In order to realize this kind of verification, we propose a software development method amalgamating OO CASE tools and algebraic specification techniques. We are developing an experimental system named COOAD (CASE tool for Object-Oriented Analysis and Design) in order to examine the effectiveness of our proposition. COOAD supports object-oriented analysis and design, verification of the analysis and design, and generation of code. In this paper, we propose the software development method, introduce COOAD, and illustrate the facilities of COOAD with an example.


Author(s):  
Assunaueny Rodrigues de Oliveira ◽  
Alvaro Sobrinho ◽  
Reudismam Rolim de Sousa ◽  
Lenardo Chaves e Silva ◽  
Helder Fernando de Araujo Oliveira ◽  
...  

2018 ◽  
Vol 18 ◽  
pp. 03003 ◽  
Author(s):  
Maxim Sergievskiy ◽  
Ksenia Kirpichnikova

Most of object-oriented development technologies rely on the use of the universal modeling language UML; class diagrams play a very important role in the design process play, used to build a software system model. Modern CASE tools, which are the basic tools for object-oriented development, can’t be used to optimize UML diagrams. In this manuscript we will explain how, based on the use of design patterns and anti-patterns, class diagrams could be verified and optimized. Certain transformations can be carried out automatically; in other cases, potential inefficiencies will be indicated and recommendations given. This study also discusses additional CASE tools for validating and optimizing of UML class diagrams. For this purpose, a plugin has been developed that analyzes an XMI file containing a description of class diagrams.


2000 ◽  
Vol 42 (2) ◽  
pp. 115-128 ◽  
Author(s):  
R.I Ferguson ◽  
N.F Parrington ◽  
P Dunne ◽  
C Hardy ◽  
J.M Archibald ◽  
...  
Keyword(s):  

2011 ◽  
pp. 199-216
Author(s):  
Liliana Favre ◽  
Liliana Martinez ◽  
Claudia Pereira

This chapter describes a reuse-based rigorous process to transform UML static models to object-oriented code. The bases of this approach are the GSBLoo algebraic language to cope with concepts of UML static models and the SpReIm model for defining structured collections of reusable components. We have defined a mapping between UML static models and GSBLoo. The emphasis in this chapter is given to the last steps in the road from UML to code. Eiffel™ is the language of choice in which we chose to demonstrate the feasibility of our approach. We analyze how to transform GSBLoo specifications into code. In particular, we show how to translate different kinds of UML associations to Eiffel. Also, we describe how to construct assertions from GSBLoo specifications. All of the proposed transformations can be automated; they allow traceability and can be integrated into the iterative and incremental software development processes supported by the existing UML CASE tools.


Sign in / Sign up

Export Citation Format

Share Document