| Ehrig H., Heckel R., Taentzer G., and Engels G.: A Combined Reference Model- and View-Based Approach to System Specification. International Journal of Software Engineering and Knowledge Engineering 7(4), 1997, 457-477. |
....constraints. Instances include, for example, start graphs, application and consistency 7 conditions, and temporal logic constraints. The idea of a combined reference model and view based specification approach has been proposed recently in the software engineering community. In [EHTE97] and [EEHT97], a specification technique based on graph transformations is presented which supports such a development approach. The use of graphs and graph transformations supports an intuitive understanding and an integration of static and dynamic aspects on a well defined semantical base. On this ....
....reference model. The views and the reference model are kept consistent manually, which is the task of a model manager. All concepts and results are illustrated at the well known example of a banking system. For the case of more than two views, more general scenarios are developed and discussed in [EEHT97]. An experimental actor language has been defined which is entirely implemented as a rule based system. In other words, the actor paradigm is used as a structuring technique for a graph rewriting system. In this context the main structuring concept, and thus the main tool for obtaining ....
[Article contains additional citation context not shown here]
G. Engels, H. Ehrig, R. Heckel, and G. Taentzer. A combined reference model- and view-based approach to system specification. Int. Journal of Software and Knowledge Engeneering, 1997. To appear. 22
....to verify a formula. The semantics of an ESV is done in two steps: to get a view structure from an ESV and to give a semantics for complex transitions. An event rewrites the system state (a global state, a data type term and an environment) into another system state. Let us mention the approach of [16] that presents a specification technique based on graph transformations used to construct the automatic integration of views. Classification. In [14] the authors propose an integration paradigm for specifications. Its aim is to deal with the integration of specifications for the different ....
Gregor Engels, Reiko Heckel, Gabriele Taentzer, and Hartmut Ehrig. A combined reference model and view-based approach to system specification. International Journal of Software Engineering and Knowledge Engineering, 7(4):457--477, 1997.
....some activities were not performed, etc. As such, they address the product inconsistencies and process inconsistencies as very related problems. This view is also shared by us and we will briefly address this deeper aspect of integration later on in this work. 11. Engels, Heckel, Taentzer, and Ehrig [Engels 1997]: The final work presented here is the work of these researchers. Some aspects of their work are again similar to the ones discussed before. In their work their thrive to create a system model out of a number of related views. Like before, their work assumes that the same names are used or a name ....
Ehrig, H., Heckel, R., Taentzer, G. and Engels, G. (1997) "A Combined Reference Model- and View-Based Approach to System Specification," International Journal of Engineering and Knowledge Engineering, Vol.7 No.4, pp. 457-477, World Scientific Publishing Company.
....DISTRIBUTE Original bank Fig. 2: Distributed development We thus use an optimistic strategy where we constrain the changes in each workspace to prevent conflicts during integration. Figure 2 is an application of the Combined Reference Model and the View Based Approach to System Specification [5]. A model, e.g. the bank, is split into several views for individual development and later integration. In this case we however block changes to the views which cause conflict during integration. Furthermore, this strategy is an extreme form of [13] and [14] which formalise and manage propagation ....
H. Ehrig, G. Engels, R. Heckel, and G. Taentzer. A Combined Reference Model- and View-Based Approach to System Specification. International Journal on Software Engineering and Knowledge Engineering, 7(4), 1997.
.... operations for graph transformation rules we consider are sequential and parallel composition for refinement in time and space respectively (see e.g. CMR 97, GPS98a] Below we give concrete set theoretic definitions of these operations, based on union and renaming of rules (see also [EEHT97] Since union identifies items of different rules that happen to have the same names we introduce renaming as an auxiliary operation to control the identifications. As precondition for the syntactic representation of renamings we assume a large enough set U as universe of items, such that all ....
G. Engels, H. Ehrig, R. Heckel, and G. Taentzer. A combined reference model- and view-based approach to system specification. Int. Journal of Software and Knowledge Engineering 7(4):457--477, 1997.
No context found.
G. Engels, R. Heckel, G. Taentzer, and H. Ehrig. A combined reference model- and view-based approach to system specification. Int. Journal of Software and Knowledge Engeneering, 7(4):457--477, 1997. Preprint at http://tfs.cs.tu-berlin.de
No context found.
G. Engels, R. Heckel, G. Taentzer, and H. Ehrig. A combined reference model- and view-based approach to system specification. Int. Journal of Software and Knowledge Engeneering, 7(4):457--477, 1997.
No context found.
G. Engels, R. Heckel, G. Taentzer, and H. Ehrig. A combined reference model- and view-based approach to system specification. Int. Journal of Software and Knowledge Engeneering, 7(4):457--477, 1997.
....the preconditions of the rule while the right hand side R describes the postconditions. During analysis, rules are considered as incomplete specifications of the transformations to be performed, i.e. additional (unspecified) changes are permitted. This (quite liberal) notion of graph transition [8] shall be strengthened in the design model by the notion of graph transformation which assumes a complete specification of the changes during a step. Figure 5 shows three rules specifying the possible effects of the use case select account. Each rule is only concerned with the interaction of one ....
....of agent based systems like autonomy, goal driven behavior, and cooperation of agents. The theory of graph transformation also provides the mathematical background for the formalization of the approach. In [4] for example, graph processes [2] and concepts of views of graph transformation systems [8] are used in order to formalize the consistency between requirement specification, analysis and design in agent oriented modeling. ....
G. Engels, R. Heckel, G. Taentzer, and H. Ehrig. A combined reference model- and viewbased approach to system specification. Int. Journal of Software and Knowledge Engeneering, 7(4):457--477, 1997.
....contrast to components, views are always system parts which cannot live alone. Views can be de ned along di erent aspects of a software system such as static structures, use cases and behaviour. On the other hand, views may be de ned for di erent kinds of users and developers of software systems [2]. In both cases, views overlap in common modeling elements, programming constructs or human computer interface parts. These parts have to be kept consistent in di erent views during system development and evolution, e.g. several descriptions of one subject in di erent views have to be equivalent. ....
G. Engels, H. Ehrig, R. Heckel, and G. Taentzer. A combined reference model- and view-based approach to system speci- cation. Int. Journal of Software and Knowledge Engeneering, 7(4):457-477, 1997.
.... caused by a known rule together with a change of context caused by an unknown rule of the environment: transition = transformation change of context This kind of transitions have been considered already for algebraic graph transformations in order to study views for system design [EHTE 97] and for Petri nets in order to study scenarios in train control systems [PJHE 98] In the former case such transitions are loose graph transformations defined by double pullbacks [HEWC 97] In the latter case transitions are open steps of open nets which allow autonomous actions on designated ....
....for DNA computing. 5. 1 Graph Transformation with Incomplete Information In Section 3 we have shown how to apply our general framework to algebraic graph transformation based on the double pushout approach, where a corresponding approach with incomplete information, called graph transition in [EHTE 97, HEWC 97, EHLO 98] has been studied already. These ideas can also be applied to any other graph transformation approach considered in the Handbook on Graph Grammars and Computing by Graph Transformation [Roz 97] Especially this seems to be of interest for the algebraic single pushout approach ....
[Article contains additional citation context not shown here]
Engels, G., Heckel, R., Taentzer, G., Ehrig, H.: A Combined Reference Model and ViewBased Approach to System Specification. Int. Journal of Software Engineering and Knowledge Eng. Vol. 7 (1997), pp. 457-477
....could distinguish between sequential and concurrent semantics as well as between classical and loose semantics. In particular, the loose semantics for graph productions turned out to be very useful for compositional reasoning about graph transformation systems which are composed of several views [EHTE97,Hec98] However, since the concrete 2 module concepts all come with a classical, sequential semantics, we do not consider this aspect. types rules procedures GCSPEC x x (x) GRACE x x (x) DIEGO x x PROGRES x x x TGT x x Table 1. Graph transformation specifications: structuring in the small. 4 ....
G. Engels, R. Heckel, G. Taentzer, and H. Ehrig. A combined reference model- and viewbased approach to system specification. Int. Journal of Software and Knowledge Engeneering, 7(4):457--477, 1997.
....behavioural constraints. For such systems, in fact, the actual behaviour depends on the interaction with the external environment. Another current stream of research concerns the enrichment of graph transformation based specification with modularity and parametrisation techniques [AEH 96,EE96,EHTE97] Also in these cases, an open or loose semantics has to be provided for modules with import export interfaces, parametrised specification components, or partial views of a system to be developed because they cannot be assumed to specify completely the behaviour of a system. A similar problem has ....
H. Ehrig, R. Heckel, G. Taentzer, and G. Engels. A combined reference modeland view-based approach to system specification. Submitted, 1997.
No context found.
Ehrig H., Heckel R., Taentzer G., and Engels G.: A Combined Reference Model- and View-Based Approach to System Specification. International Journal of Software Engineering and Knowledge Engineering 7(4), 1997, 457-477.
No context found.
G. Engels, H. Ehrig, R. Heckel, and G. Taentzer. A combined reference model- and view-based approach to system speci - cation. Int. Journal of Software and Knowledge Engineering, 7(4):457-477, 1997.
No context found.
Ehrig, H., Heckel, R., Taentzer, G., Engels, G.: "A Combined Reference Model- and View-Based Approach to System Specification," International Journal of Software Engineering and Knowledge Engineering, 7(4), pp. 457-477, 1997.
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