Christine Choppy and Stphane Kaplan. Mixing abstract and concrete modules: Specification, development and prototyping. In 12th International Conference on Software Engineering, pages 173--184, Nice, March 1990.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... n ( n nb) false) nb, b stopWillBeRequested n n, b n, true stopNotWillBeRequested n (nb = n) false nb, b position n n, b new n n, false ( not b) true) not b) true) is easy to change the implementation in a modular way as justified in [9] and initially proposed in [8]. Because of a lack of space, this aspect will not be discussed further. 3.2 Code generation for ADT The lift specification uses some ADTs. One of them is List (Figure 9) which is used by Building class to store a list of floors. In CO OPN types and functions are dissociated. An ADT module can ....

Christine Choppy and Stphane Kaplan. Mixing abstract and concrete modules: Specification, development and prototyping. In 12th International Conference on Software Engineering, pages 173--184, Nice, March 1990.

....stage of development, combining code and specifications in an arbitrary way. The tool is aimed at covering the gap that exists for the time being between the initial specification of the problem and the final delivered system. Other projects support this kind of execution, but we only know [4] providing almost identical features from a compilation point of view. We have defined a process language consisting of very few elements to make it easy to learn and use: a small catalogue of tasks with well defined relationships, two mechanisms to relate tasks (rules and groupings) and a few ....

C. Choppy, S. Kaplan. "Mixing abstract and concrete modules: specification, development and prototyping". In Proceedings of XII International Conference on Software Engineering (ICSE), Nia (France), 1990

....cost is expressed in terms of simple characteristics of the rewriting system. Efficiency of rewriting may be improved through compiling the rules into code (e. g [538] or through the use of mixed evaluation combining rewriting for some specification modules and code evaluation for other modules [539, 207, 212]. In the Asspegique environment, further described in Section 6.4, the symbolic evaluation tools take conditional rewrite rules into account. There are three different possibilities for evaluation : i) standard rewriting, with textual and graphic trace options, and choice of the rewriting ....

....conditional rewrite rules into account. There are three different possibilities for evaluation : i) standard rewriting, with textual and graphic trace options, and choice of the rewriting strategy, ii) evaluation with compiled rules [538] iii) and mixed evaluation (rewriting user code) [539, 207, 212]. The mixed evaluation mode allows to perform computations where rewriting interacts with the execution of code. This code should include an implementation for constructor inverses and may be written by the user; it may be an implementation for some modules of the specification, or even for parts ....

C. Choppy and S. Kaplan. Mixing abstract and concrete modules : specification, development and prototyping. In Proc. of the 12th International Conference on Software Engineering, pages 173--184, 1990. \Phi.

....feature which contributes to the safety of the method is that the automatically generated code is never modified: Instead, the developer derives new sub classes which incorporate or replace the inherited code with hand written extensions. A related technique is the one of mixed prototyping [8], which is also based on the compilation of formal specifications, and where the generated code may be progressively replaced by hand written modules. The drawback Inherits from (and implements) User s Concrete Classes Generated Concrete Class User s Concrete Classes Generated Abstract Class ....

C. Choppy and S. Kaplan. 1990. Mixing Abstract and Concrete Modules: Specification, Development and Prototyping. In Proc. 12th Int. Conf. on Software Engineering (Nice, France, March). 173-184.

....to testing over efficiency and which involves a term rewriting system to evaluate specified functions and an interpreter for imperative ones. Other projects do exist that support execution of equations mixed with imperative programs. The closest to ours is the execution system of Asspegique [CK90], which combines PLUSS specifications with Ada implementations. There is a basic difference, however: mixed execution relies on the compilation of equations into Ada and in the generation of packages for the involved modules. We think that, in the testing framework, compilation prevents the easy ....

C. Choppy, S. Kaplan. "Mixing abstract and concrete modules: specification, development and prototyping". In Proceedings of 12th ICSE, Nice (France), 1990.

....feature which contributes to the safety of the method is that the automatically generated code is never modified: Instead, the developer derives new sub classes which incorporate or replace the inherited code with handwritten extensions. A related technique is the one of mixed prototyping (Choppy and Kaplan 1990), which is also based on the compilation of formal specifications, and where the generated code may be progressively replaced by hand written modules. The drawback with their method is that code reuse is very limited, which is unsatisfactory from a software engineering point of view, but also ....

....type of the target language a contiguous portion of memory which allows efficient indexing. Note that this requires the possibility of allocating arrays dynamically, otherwise we can only use this implementation for array types algebraically specified as bounded. Afterwards, as described in (Choppy and Kaplan 1990), we must define some basic operations, like the constructors (new and assign) and their inverses (assign inv) as well as low level testors and selectors. This is the moment we choose to pre test our new implementation: Compile the new definition, modify the configuration file, and link the ....

Choppy, C. and Kaplan, S. 1990. "Mixing Abstract and Concrete Modules: Specification, Development and Prototyping." In Proc. 12th Int. Conf. on Software Engineering (Nice, France, March). 173-184.

....links. In this paper, we consider the way we can build incremental prototypes for concurrent systems specified with CO OPN by using an object oriented programming language for the implementation. We show that the use of object oriented programming languages, compared to previous approaches [11], allows for more flexibility in the incremental prototyping process, and gives better guarantees that the final prototype conforms to the formal specification. We made this experience with the object oriented part of the Ada95 language [1] but the principles can be transposed to any modern ....

C. Choppy, S.Kaplan, "Mixing Abstract and Concrete Modules: Specification, Development and Prototyping", Proc. 12th Int. Conf. on Software Engineering, Nice, 1990.

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