J.C.S.P. Leite, M. Sant'Anna, and F.G. Freitas. Draco-PUC: A Technology Assembly for Domain Oriented Software Development. Proceedings of the third IEEE International Conference of Software Reuse, pages 94--100, November 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....elicitation, and representation of software products, techniques that systematize these tasks are necessary. One can assume that this is a well resolved situation, since there are several DA approaches found in the technical literature (Prieto, 1987,1993,1994) Cohen, 1991) Neighbors, 1992) (Leite, 1994) (Gomaa, 1994,1995) Arango et al., 1994) Simos, 1994) Stars, 1996) Jacobson et al., 1997) Griss et al., 1998) However, when considering the issue of knowledge acquisition, these approaches do recognize the importance of this activity, but they do not provide a systematic process for performing ....

....Under this perspective, two issues are important in order to evaluate the DA approaches: knowledge elicitation and its representation. The analyzed approaches were: Facets and Sandwich Method (Prieto, 1987, 1994) Feature Oriented Domain Analysis (Cohen, 1991, 1994) DRACO (Neighbors, 1992) (Leite, 1994); Evolution Domain Life Cycle (Gomaa, 1994, 1995) Arango s DA Generic Process (Arango et al., 1994) ODM (Simos, 1994) Stars, 1996) and RSEB (Jacobson et al., 1997) Griss et al., 1998) Fig. 1. Simplified Perspective of Knowledge Acquisition within DA We were able to observe that most approaches ....

Leite, J.C.S.P., 1994, "Draco-Puc: A Technology Assembly for Domain Oriented Software Development" , in: Proceedings of the Third International Conference on Software Reuse, pp. 94-100, Rio de Janeiro, Brazil.

....correctness preserving transforms, with the goal of enhancing program efficiency without changing its behavior, until the specification has been transformed to executable code. 3 General purpose transformation systems and models of transformation systems include Draco [Nei84, Nei89] Draco PUC [Lei94], IP [Sim95] Kids [Smi85, Smi91] and REFINE [Rea92] POPART Paddle [Wil93] TAMPR [Boy89] and TXL [Cor95] Domain specific transformation systems include AP5 [Coh93] in the domain of data structures and Sinapse [Kan93] in the domain of mathematical modeling. 2. Conventional high level language ....

Julio Casar Sampaio do Prado Leite, Marcelo Sant'Anna, Felipe Gouveia de Freitas, Draco-PUC: a Technology Assembly for Domain Oriented Software Development. In [Fra94].

....of transformations which successively converts the specification into a concrete implementation in an executable programming language. 89 What is the benefit of using Draco The payoff occurs when the high level abstractions of the application domain languages and modelling languages are reused [Lei94]. Two challenges must be overcome, however. First, a relevant language for a given application domain may not exist. In this case, the system designer must create the language before any specification can be written. Second, the transformation of programs from one language to another is only ....

Julio Leite, Marcelo Sant'Anna, and Felip de Freitas. Draco-PUC: a technology assembly for domain oriented software development. In Proceedings of the 3rd International Conference on Software Reuse, Rio de Janeiro, November 1994,

....be executed in a sequence defined by a combination of the pattern characteristics and the results of user interaction during instantiation. The Pattern Instantiation Environment (PIE) is a prototype tool developed to support the application of design patterns. PIE is supported by the Draco PUC [LSF94] software machine, which is a meta program generator that supports the construction and usage of domain oriented software. Draco PUC follows the Draco paradigm [Nei84] for software development which, as mentioned in [LSF94] states that it is possible to develop software based on the reuse of ....

....the application of design patterns. PIE is supported by the Draco PUC [LSF94] software machine, which is a meta program generator that supports the construction and usage of domain oriented software. Draco PUC follows the Draco paradigm [Nei84] for software development which, as mentioned in [LSF94] states that it is possible to develop software based on the reuse of high level abstractions. In PIE, the reuse of high level abstractions is Figure 2: Structure of the PIE. provided by instantiations of design patterns and the representation domain is the product language in which ....

Julio Leite, Marcelo Sant'Anna, and Felipe Freitas. Draco-PUC: a technology assembly for domain oriented software development. In Proceedings of the Third International Conference on Software Reuse, pages 94--100, Los Alamitos, CA, 1994. IEEE Computer Society Press.

....paradigm is based on the concept of domain oriented software building through transformation. Neighbors [NEI 80] built the first Draco machine prototype. The Draco machine was later rebuilt at PUC RJ [PRA 92] using new modern hardware and software platform languages. Several research projects [LEI 94, LEI 95] to make changes and improvements resulted in new versions of the Draco machine, each one more effective and powerful than the previous one. Part of a Mondel specification Part of the Java programs generated automatically USR Interface.java import java.rmi. public interface ....

Leite, J.C.S. & Freitas, F.G. & Sant'Anna, M. Draco-PUC: a Technology Assembly for Domain Oriented Software Development. 3rd. IEEE International Conference of Software Reuse, Rio de Janeiro (RJ), Nov/1994.

....already marked with tags as defined by Staa s proposal. However, we can also produce documentation for bare source code. This is possible because we generate the software documentation based on the source code grammar and on the markup grammar. We have used the transformation system of Draco PUC [Leite94] to produce the language dependent information and to recover the system structure. Talisman [Staa93] CASE tool was used to deal with the markup information. Finally we use a standard browser to access the resulting documentation. The transformation system plays the role of the extractor, ....

....The information extraction system (see Figure 6) parses the source code and produces information that is going to be used by the information formatting system. The formatting system then produces a hypertext system in HTML. The first part of the process, the extraction system, uses Draco PUC [Leite94] transformation capabilities. The second part of the architecture, the formatting system, is based on a repository based CASE tool called Talisman [Staa93] presented in Talisman CASE tool. Both Draco PUC and Talisman are the result of several years of research at PUC Rio in the areas of ....

[Article contains additional citation context not shown here]

Leite, J. C. S.P.; Sant'anna M. ; Freitas, F. G.; "Draco-PUC : a Technology Assembly for Domain Oriented Software Development"; Proceedings of the 3 rd IEEE International Conference of Software Reuse; 1994.

No context found.

J.C.S.P. Leite, M. Sant'Anna, and F.G. Freitas. Draco-PUC: A Technology Assembly for Domain Oriented Software Development. Proceedings of the third IEEE International Conference of Software Reuse, pages 94--100, November 1994.

No context found.

J. Leite, M. Sant'Anna, and F. Freitas. Draco-PUC: A Technology Assembly for Domain Oriented Software Development. Proceedings of the third IEEE International Conference of Software Reuse, pages 94--100, November 1994.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC