Dean, T.R. and J.R. Cordy, "A Syntactic Theory of Software Architecture", IEEE Transactions on Software Engineering, 21(4), 302-333 (Apr., 1995).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Networks] Distributed Systems. 1. Introduction Architectural specifications have an increasingly important role in the design and development of computer based systems. This role is evidenced by the emergence of software architecture with its formal underpinnings as a distinct field [28,50,55,3,18,13], and by the proliferation of specialized methods and notations for architectural descriptions of software [6,14,27,43,53,26] Besides their use as documentation and as an abstraction mechanism to manage structural complexity, architectural specifications can also aid in rigorous system ....

.... languages which support a box and line type block diagram notation, such as ROOM [52] SDL [51,35] and ModeChart [36] architectural description languages such as Aesop [26] Wright [6] UniCon [53] Rapide [43] and ACME [27] and other formal notations such as those used in [49] 31] and [18]. All of these techniques refer to the notions of component, connector, and configuration to describe interfaceconnection architectures (systems of modules interconnected through their interface ports) 44] While the separation of structure from behavior (functionality) is evident in many of ....

[Article contains additional citation context not shown here]

T.R. Dean and J.R. Cordy. A syntactic theory of software architecture. IEEE Trans. Softw. Eng., 21(4):302--313, April 1995.

....4 describes the user interface of our architectural analysis environment. Finally, in Section 5 some conclusions and related future work are presented. 2 Architectural analysis framework 2. 1 Model Several notations and languages have been proposed to describe software systems architecture [7, 8, 9, 10, 11]. However most of these notations have been used within forward engineering approaches, i.e. they are architectural or configuration integration languages producing system descriptions that can be, for some of them, further processed to generate real software systems. These descriptions usually ....

....set I of connectors of type inter process connector(IPCs) Programs, which constitute an application, cooperate by exchanging data and synchronizing themselves through connectors. The IPCs that can bind program components are represented in the following taxonomy which is partially derived from [8]: ffl shared file: a data repository accessed sequentially by several programs; ffl shared memory: data that can be accessed at random and are shared among different programs; ffl remote procedure call (RPC) a procedure call like mechanism between different programs; ffl stream: a ....

T. R. Dean and J. R. Cordy, "A Syntactic Theory of Software Architecture", IEEE Trans. Software Eng., vol. 21, n. 4, pp. 302-313, Apr. 1995.

....benchmark ART and the results obtained on architectural concepts identification on the benchmark. Section 5 discusses related research and Section 6 presents conclusions and future work. 2 Architectural Model Several notations and languages were proposed to describe software systems architecture [5,13,25,33,38,42]. However most of these notations have been used within forward engineering approaches. They are architectural or configuration integration languages producing system descriptions that can be, in some cases, further processed to generate real software systems. These descriptions usually represent ....

....(IPC) Programs are separately executable units that constitute an application and cooperate by exchanging data and synchronizing themselves through connectors. The IPCs that can bind program components are represented in the following 4 DRAFT taxonomy, which is partially derived from [13]: shared file: a data repository accessed sequentially by several programs; shared memory: data that can be accessed at random and are shared among different programs; remote procedure call (RPC) a procedure call like mechanism between different programs; stream: a unidirectional ....

T. R. Dean J. R. Cordy. A syntactic theory of software architecture. IEEE Transactions on Software Engineering, 21(4):302--313, Apr 1995.

....to the factory. interface interface Explicit Interface Multiple Interfaces Wrapper Employ interface more specific Wrapper interface Wrapper 1 2 3 Fig. 11. Sequence of Transformations using Interfaces or Wrappers The following approaches are graph grammar based. DEAN and CORDY [DC95] use an architecture like language which identifies for example the entities task and file and the relationships memory access and invocation. Thus they can represent system structures as graphs. The graph productions are used to characterize systems according to their conformance with a given ....

Thomas R. Dean and James R. Cordy. A Syntactic Theory of Software Architecture. IEEE Transactions on Software Engineering, 21(4):302--313, 1995.

....the static components of the system, but not so the dynamic components that define the interaction among them [GS93, AG94] In these graphs, relations have fundamental importance and the modalities used should be able to reflect this relevance. There exist some work in this area as, for example, [DC95] where a (non modal) syntactic language for the description of architectures is presented. ....

Dean, T. and Cordy, J. A syntactic theory of software architecture. IEEE Transactions on Software Engineering, 21(4), April 1995.

....recently, connectors have become topical and a language bred in industry, Gestalt [Schwanke 1994] is based heavily on the ideas of both UniCon and WRIGHT. Work has also proceeded on the theoretical side, with a taxonomy of system structures and a notation for their connections being described in [Dean 1995]. In [Rice 1994] and [Magee 1994b] attempts have been made to provide formal models for configuration programmming languages, but neither of these places emphasis on connectors. The work that goes into the greatest depth formally so far is that of [Allen 1994b] Mention should also be made of the ....

Dean T and Cordy JR, A syntactic theory of software architecture, IEEE Trans on Soft Eng. 21 (4) 302--313, April 1995.

....Networks] Distributed Systems. 1. Introduction Architectural specifications have an increasingly important role in the design and development of computer based systems. This role is evidenced by the emergence of software architecture with its formal underpinnings as a distinct field [28,50,55,3,18,13], and by the proliferation of specialized methods and notations for architectural descriptions of software [6,14,27,43,53,26] Besides their use as documentation and as an abstraction mechanism to manage structural complexity, architectural specifications can also aid in rigorous system ....

.... languages which support a box and line type block diagram notation, such as ROOM [52] SDL [51,35] and ModeChart [36] architectural description languages such as Aesop [26] Wright [6] UniCon [53] Rapide [43] and ACME [27] and other formal notations such as those used in [49] 31] and [18]. All of these techniques refer to the notions of component, connector, and configuration to describe interfaceconnection architectures (systems of modules interconnected through their interface ports) 44] While the separation of structure from behavior (functionality) is evident in many of ....

[Article contains additional citation context not shown here]

T.R. Dean and J.R. Cordy. A syntactic theory of software architecture. IEEE Trans. Softw. Eng., 21(4):302--313, April 1995.

....# calculus, complexity theory, databases, incremental compilers, and analysis of concurrent systems. This work is motivated by the use of graphs in software architecture to describe specific and generic organizational patterns of system components (Garlan and Shaw, 1993; Abowd et al. 1993; Dean and Cordy, 1995), and similarly, in distributed systems to describe their communication structures (Hinterplattner et al. 1990; Milne and Milner, 1979; Milner, 1978; Erdogmus et al. 1996; Milner et al. 1992) The general goal is to develop a formal graph calculus for specifying and reasoning about topological ....

....A generic configuration typically contains infinitely many instances (distinct configurations) obeying certain topological constraints. An important application of this in software engineering concerns the formal specification and analysis of architectural styles (Garlan and Shaw, 1993; Dean and Cordy, 1995). ....

Dean, T. and Cordy, J. (1995). A syntactic theory of software architecture. IEEE Trans.

....documents. Interest in software architectures is arising: a recent work on the use of a logic notation for formalizing them is [118] Such a paper contains a formal model based on logic for dealing with evolving software architectures, namely for configuration and version management. Instead, in [45] Prolog is actually used as tool for manipulating software architectures by pattern matching. Also arising is the interest in the quality of design documents: a number of software quality measures can be defined by set of rules which analize and evaluate program structure. A typical measure ....

T. Dean and J. Condy. A Syntactic Theory of Software Architecture. IEEE Transactions on Software Engineering, 21(4):302--313, April 1995.

....in the context of different design methodologies, then the conceptual model of a component should be independent of the notation, terminology, etc. associated with a specific design methodology. A number of recent papers in the area of software architecture support this and other worthwhile goals [1, 5, 9, 11, 12]. In this paper, we would like to extend this idea of methodologyindependence to the notion of a test case. If testing is to be used as the approach to validating components, then optimally, one would like to associate test cases with specific components. Indeed, test cases which have been ....

Dean, T.R., and J.R. Cordy, "A Syntactic Theory of Software Architecture," IEEE Transactions on Software Engineering, vol. 21, no. 4, April 1995, pp. 302-313.

....by the recovery process. The result of the recovery or restructuring process is a concrete architecture that conforms with the conceptual architecture as it is specified by the AQL query. We adopt a typed, attributed, directed graph formalism which is similar to some approaches in the literature [5]. The graph representation of the target system (G t or, G s ) is defined as a tuple: G s = hV s ; A s i where V s is the set of typed vertices obtained from the target system (source code entities) and A s is the set of allowable edges between vertices obtained from the language domain model. ....

T. R. Dean and J. R. Cordy. A syntactic theory of software architecture. IEEE Transactions on Software Engineering, 21(4):302--313, April 1995.

....example of figure 10. Advantages of Darwin over Clock are that multiple architectures can be edited concurrently and easily combined, and that both automatic and userdirected architecture layout are provided. Numerous authors have pointed out that there are many styles of software architecture [2, 18] , and that architecture languages must support this heterogeneity [19] Clock s architecture language, however, supports only a single style. To address this problem, Clock architectures can be treated as primitive units for composition using other architectural techniques. There is no reason, ....

Thomas R. Dean and James R. Cordy. A syntactic theory of software architecture. IEEE Transactions on Software Engineering, 21(4):302--313, April 1995.

....interface interface name interface specification ; Resources required by this module. dependencies dependencies specification ; Many module interconnection language paradigms exist from which COIL can draw to create a language model that is symmetric in this respect [2,4,5,7,9,17,20,26,31]. While providing this type of interface symmetry, COIL must support unique features presented by CORBA such as its events service and its call back model for method invocations. To the best of the authors knowledge, this latter feature is fairly unique in the context of module interconnection ....

....with multiple application server objects associated with their underlying database systems. CORBA is designed for integrating objects, not whole applications [11] A plethora of good research on creating module interconnection languages for existing systems can be drawn upon to achieve this goal [2,4,5,7,9,17,20,26,31]. These approaches must be re contextualized and extended to deal with the unique challenges presented by database integration and evolution problems and CORBA. Syntactic Analysis COIL will be based on a formal syntactic model of a CORBA based module interconnection language. This will provide a ....

[Article contains additional citation context not shown here]

T. R. Dean and J. R. Cordy. A Syntactic Theory of Software Architecture. IEEE Transactions on Software Engineering. Vol. 21, No. 4, April 1995.

....checking, compositional verification. 1 Introduction Architectural specifications have an increasingly important role in the design and development of computer based systems. This role is evidenced by the emergence of software architecture with its formal underpinnings as a distinct field [27, 49, 54, 3, 18, 13], and by the proliferation of specialized methods and notations for architectural descriptions of software [6, 14, 26, 42, 52, 25] Besides their use as documentation and as an abstraction mechanism to manage structural complexity, architectural specifications can also aid in rigorous system ....

.... languages which support a box and line type block diagram notation, such as ROOM [51] SDL [50, 34] and ModeChart [35] architectural description languages such as Aesop [25] Wright [6] UniCon [52] Rapide [42] and ACME [26] and other formal notations such as those used in [48] 30] and [18]. All of these techniques refer to the notions of component, connector, and configuration to describe interface connection architectures (systems of modules interconnected through their interface ports) 43] While the separation of structure from behavior (functionality) is evident in many of ....

[Article contains additional citation context not shown here]

T. Dean and J. Cordy. A syntactic theory of software architecture. IEEE Trans. Softw. Eng., 21(4):302--313, Apr. 1995.

....formalisms, model checking, equivalence checking, compositional verification. 1 Introduction The increasing importance given to architectural level abstractions in software systems design is evidenced by the emergence of software architecture with its formal underpinnings as a distinct field [31, 2, 11, 16] and by the proliferation of specialized methods and notations for architectural descriptions of software [3, 22, 30] Besides their traditional use as documentation, architectural specifications can also aid in rigorous system development based on step wise refinement [27, 29] in rapid system ....

....Numerous techniques have been proposed for architectural descriptions. Examples include specification languages which support a box and line type block diagram notation [29, 28] architectural description languages [16, 30, 22] and other formal notations such as those used in [27] 18] and [11]. All of these techniques refer to the notions of component, connector, and configuration to describe interface connection architectures (systems of modules interconnected through their interface ports) 23] While the separation of structure from behavior (functionality) is evident in many of ....

[Article contains additional citation context not shown here]

T. Dean and J. Cordy. A syntactic theory of software architecture. IEEE Trans. Softw. Eng., 21(4):302--313, Apr. 1995. 14

....internal structure is completely specified on its highest level. 11 Background and Related Work The literature on formal models that deal explicitly with software architecture is limited. Formal study of architectural concepts have begun emerging only recently; among those, we can cite [14, 21, 5, 8, 2]. In an early work on semantics of concurrency, Milner et al. [18, 17] define algebraic rules for composing nets (nets are analogous to modules. These rules give rise to a family of calculi called flow algebras. Flow algebras represents one of the earliest semantic theories which deal exclusively ....

....logic (Lamport s TLA) In these references, the behavioral semantics of connections is considered to be a part of the architecture definition language; this semantics must be preserved during architectural refinement. In our model, behavioral semantics is not considered at all. Dean and Cordy [5] provide a diagrammatic syntax for formalizing software architectures and architectural styles. The objects of their language nodes, variables, and connectors are analogous to primitive modules, composite modules, and connectors, respectively. The interface of a group of interconnected nodes, ....

[Article contains additional citation context not shown here]

T.R. Dean and J.R. Cordy. A syntactic theory of software architecture. IEEE Transactions on Software Engineering, 21(4):302--313, April 1995.

....In addition, it is hard to decompose an element, particularly a line, in a box and line diagram. As a result, the architecture is poorly understood by developers when the system grows larger and more complex. It also hampers attempts at making system design knowledge explicit and easy to reuse [GAO95, CoLu95, DeCo95]. The jigsaw patterns technique, as illustrated in Figure 1, can overcome these problems of box andline diagrams. In Figure 1, the component C1 could be a source or a sink process. It has room for one inward stub corresponding to one interface interacting with one connector. The connector Con C1 ....

Thomas R. Dean and James R. Cordy. A Syntactic Theory of Software Architecture, IEEE Transactions on Software Engineering, Vol. 21, No. 4, April 1995, pp302-313.

....relation, we can deduce part of the behavior of both components and the form in which they communicate (the client sends requests to the server in any moment, the server answers the requests without knowing who makes the requests, etc. There exist some current work in this area, for example in [Dean, T. and Cordy, J. 1995] where a (non modal) syntactic language for the description of architectures is presented. 7. CONCLUSIONS In this work we present a methodology for the representation of software system designs and for the verification of properties over them. The graphs of design are considered models of an ....

Dean, T. and Cordy, J. 1995. A syntactic theory of software architecture. IEEE Transactions on Software Engineering 21, 4 (April).

....define what are the building blocks of an architecture, i.e. the components and the connectors binding them together, what are the rules to combine them and to create abstractions from concrete entities. Several notations and languages have been proposed to describe software systems architecture [7, 8, 9, 10, 11]. Some of them address the structural and syntactic level and rely on simple methods to express semantics (use of typed component and connectors [8] or attribute value couples [9] Some other have powerful mechanisms to express semantics of interaction [10] but do not have mechanisms equally as ....

....create abstractions from concrete entities. Several notations and languages have been proposed to describe software systems architecture [7, 8, 9, 10, 11] Some of them address the structural and syntactic level and rely on simple methods to express semantics (use of typed component and connectors [8] or attribute value couples [9] Some other have powerful mechanisms to express semantics of interaction [10] but do not have mechanisms equally as powerful to express systems structure. However, what we are mainly interested in, is the extraction of abstract representations, or views, of a ....

[Article contains additional citation context not shown here]

T. R. Dean and J. R. Cordy, "A Syntactic Theory of Software Architecture", IEEE Trans. Software Eng., vol. 21, n. 4, pp. 302-313, Apr. 1995.

No context found.

T. R. Dean and J. R. Cordy. A syntactic theory of software architecture. IEEE Trans. on Software Engineering, 21(4):302--313, January 1995.

No context found.

Dean, T.R. and J.R. Cordy, "A Syntactic Theory of Software Architecture", IEEE Transactions on Software Engineering, 21(4), 302-333 (Apr., 1995).

No context found.

Dean, T. R. e Cordy, J. R., "A Syntactic Theory of Software Architecture", IEEE Transactions on Software Engineering, Vol. 21, No. 4, pp. 302-313, Abril, 1995.

No context found.

T.R. Dean, J.R. Cordy. A syntactic theory of software architecture. IEEE Transactions on Software Engineering, 21(4):302-313, April 1995.

No context found.

T.R. Dean and J.R. Cordy. 1995. A syntactic theory of software architecture. IEEE Transactions Software Engineering, 21(4):303--313, April 1995.

First 50 documents

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