R.N. Taylor, N. Medvidovic, et al. A Component- and Message -Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, 22(6), June 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....WORK The work presented in this paper has been influenced by several di#erent proposals. First of all, we must say that the idea of working on modeling and analyzing software architectures came from the many ADLs (Architectural Description Language) like Rapide [23] Wright [3] Darwin [24] C2 [30], and xADL [11] In most of these approaches, we noticed a mismatch between the abstraction level at which we usually model the software architectures of our systems and the abstraction level at which we should work with these languages. Our opinion is that, while the semantics of concepts is ....

R. Taylor, N. Medvidovic, K. Anderson, E. Whitehead Jr., J. Robbins, K. Nies, P. Oreizy, and D. Dubrow. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, June 1996.

....a set of types for components, connectors, interfaces, and properties together with a set of rules that govern how elements of those types may be composed. Requiring a system to conform to a style has many benefits, including support for analysis, reuse, code generation, and system evolution [10,31,32]. Moreover, the notion of style often maps well to widely used component integration infrastructures (such as EJB, HLA, CORBA) which prescribe the kinds of components allowed and the kinds of interactions that may take place between them. One of the significant advantages of architectural ....

Taylor, R.N., Medvidovic, N., Anderson, K.M., Whitehead, E.J., Robbins, J.E., Nies, I<2A., Oreizy, P., and Dubrow, D.L. A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering 22(6):390-406, 1996.

....In this paper we present an object oriented framework, called FaTC2, for building fault tolerant component based systems based on the IFTC. Our framework is an extension of C2.FW[10] an OO framework which provides an infrastructure for building applications using the C2 architectural style[15]. FaTC2 introduces forward error recovery in the original framework by means of an exception handling system (EHS) An EHS offers control structures which allow developers to define actions that should be executed when an error is detected. This materializes by the capability to signal exceptions ....

....to put the system back in a coherent state. A forward error recovery mechanism manipulates the state of a system in order to remove errors and enable it to resume execution without failing. Forward error recovery is usually implemented by means of exception handling. The C2 architectural style[10, 15] is a component based architectural style which supports large grain reuse and flexible system composition, emphasizing weak bindings between components. The C2 style has been chosen due to its ability to compose heterogeneous off the shelf components[10] The work of Rakic and Medvidovic[11] is ....

[Article contains additional citation context not shown here]

R. N. Taylor, N. Medvidovic, K. Anderson, J. E. J. Whitehead, and J. Robbins. A component- and message- based architectural style for GUI software. In Proceedings of the 17th International Conference on Software Engineering, pages 295--304, April 1995.

....WORK The work presented in this paper has been influenced by several di#erent proposals. First of all, we must say that the idea of working on modeling and analyzing software architectures came from the many ADLs (Architectural Description Language) like Rapide [19] Wright [2] Darwin [20] C2 [26], and xADL [9] In all these approaches, we noticed a mismatch between the abstraction level at which we usually model the software architectures of our systems and the abstraction level o#ered by these languages. Our opinion is that, while the semantics of concepts is clear and welldefined, the ....

R.N. Taylor, N. Medvidovic, K.M. Anderson, E.J. Whitehead Jr., J.E. Robbins, K.A. Nies, P. Oreizy, and D.L. Dubrow. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, June 1996.

....or SAL [2] or simple transitions that are not allowed to fire during model evolution (e.g. in Mur# [23] 4. RELATED WORK Several proposals have influenced our work. First of all, we should mention the many ADLs (Architectural Description Language) Rapide [19] Wright [1] Darwin [20] C2 [30], and xADL [7] that gave us the first impulse. All these approaches mainly concentrate on concepts, which are well defined, but in too many cases, the languages that render them are too di#cult for the user. This is why we decided for a well known representation of concepts, paired with a formal ....

R.N. Taylor, N. Medvidovic, K.M. Anderson, E.J. Whitehead Jr., J.E. Robbins, K.A. Nies, P. Oreizy, and D.L. Dubrow. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, June 1996.

....aid. There is no reason why a strict model of the component connector interface could not be used in conjunction with a faithful, albeit looser implementation of that interface. The C2 architectural style and its supporting infrastructure take a similar approach to strictness and flexibility [20]. Strictness is achieved through an external mechanism that is part of the C2 development environment. At run time, flexibility is achieved through a common event bus to which arbitrary components can connect, disconnect, and reconnect. C2 differs from our approach in that it has adopted a ....

R.N. Taylor, N. Medvidovic, K.M. Anderson, E.J. Whitehead, Jr., J.E. Robbins, K.A. Nies, P. Oreizy, and D.L. Dubrow. A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, Vol. 22(6): 390-406, June 1996.

....or SAL [3] or simple transitions that are not allowed to fire during model evolution (e.g. in Mur# [21] 4. RELATED WORK Several proposals have influenced our work. First of all, we should mention the many ADLs (Architectural Description Language) Rapide [17] Wright [2] Darwin [18] C2 [28], and xADL [8] are just a few examples. In all these approaches, concepts are well defined, but the concrete representation does not always support them. This is why we decided for a well known representation of concepts, paired with a formal definition of their interaction and composition. Given ....

R.N. Taylor, N. Medvidovic, K.M. Anderson, E.J. Whitehead Jr., J.E. Robbins, K.A. Nies, P. Oreizy, and D.L. Dubrow. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, June 1996.

....similarly to Wright. Since LEDA supports inheritance for roles, it contains a definition of correctness to preserve compatibility by the inheritance and refinement [13] The role inheritance must preserve behavior specified in the parent role to ensure, that the parent may be Figure taken from [60] 21 Figure 4. C2 architecture example replaced by a derived version while maintaining compatibility. Derived roles are compatible if they are more deterministic (by specifying fewer choices made by the component itself known as local choices) However, the derived role can provide more choices ....

....of semantic compatibility results in a disallowing extension of behavior. The state explosion problem is addressed by testing each attachment locally for compatibility. Therefore, the testing cannot ensure global deadlock freedom, but this is not the goal of the verification. 2.2. 5 C2 The C2 [60] style is an ADL specialized for developing GUI applications. Such systems share common attributes, for example layered architecture and message based communication. Therefore, C2 introduces support for these features by making the architecture style explicit. The C2 components form a ....

R.N. Taylor, N. Medvidovic, K.M. Anderson, E. J. Whitehead, J.E. Robbins, K.A. Nies, P. Oreizy, D.L. Dubrow, "A Component- and Message-Based Architectural Style for GUI Software," IEEE Transactions on Software Engineering, vol. 22, no. 6, pp 390-406, Jun 1996.

....major focus of our work has been precisely on alleviating this problem, and bridging the two approaches described above. While supporting powerful analysis of architectural models, we have also provided implementation support for conceptual architectures based on a specific architectural style, C2 [31]. This paper describes our experience over the past seven years in developing a family of architectural frameworks for supporting the implementation, deployment, execution, monitoring, and evolution of applications built according to C2. In this paper we demonstrate how applications designed in ....

....5 discusses the evolution of our framework design, resulting in a family of architectural frameworks. Section 6 highlights the lessons learned in the process. Section 7 discusses related approaches. The paper concludes with a brief overview of future work. 2. DESCRIPTION OF THE C2 STYLE C2 [31] is an architectural style for highly distributed, dynamic, and evolvable systems. An ADL, C2SADEL [15] has been developed to formally describe C2 style architectures. C2 style architectures are described through a set of components and connectors, and the topology into which they are composed. ....

[Article contains additional citation context not shown here]

R.N. Taylor, et al. A Component- and Message-Based Architectural Style for GUI Software. 1EEE-TSE. 22(6), 1996.

.... Attempts have been made to develop systematic techniques for dealing with architectural styles resulting in formalisms to describe styles [1,15] preliminary taxonomies [29] and informal discussions of the differences between a newly codified style and existing styles that have influenced it [11,31]. However, for the most part these studies fail to clarify the key dimensions along which one architectural style may differ from another. Another related, critical issue is ensuring that a property that is established in the model of a system s stylebased architecture holds true of the system s ....

.... Can complex, divergent architectural styles be composed from a reusable set of (simple) primitives In order to answer these questions, to date we have successfully modeled, analyzed, and implemented the structural and compositional aspects of four well known architectural styles using Alfa: C2 [31], client server [9] pipe and filter [6] and push based [11] While these styles are not a representative cross section of all architectural styles, as a collection they embody a large number of recurring architectural concepts: distribution, concurrency, events, implicit invocation, dynamism, ....

[Article contains additional citation context not shown here]

Taylor, R. N., et. al., "A Component- and Message-Based Architectural Style for GUI Software", IEEE Trans. on Software Engineering, 22(6), June 1996, pp. 390-406.

....the object model) Its integration with object models makes it a suitable candidate to model dynamism in the context of UML; however, architecture description language and many other design languages do not use object models. Even in cases where ADLs have been successfully mapped to UML (e.g. C2 [14] to object model mapping) 1] this mapping also changed the meaning of those objects (that is a main reason why stereotypes were used) For instance, in C2 one component is not aware of any components next to it and thus cannot refer to it directly by name. An object model representing a C2 ....

Taylor, R. N., Medvidovic, N., Anderson, K. N., Whitehead, E. J. Jr., Robbins, J. E., Nies, K. A., Oreizy, P., and Dubrow, D. L., A Component- and MessageBased Architectural Style for GUI Software IEEE Transactions on Software Engineering, vol. 22, pp. 390406, 1996.

....transform transform Derived User Defined like something like something like map map map A B map compare a) b) c) d) Figure 1. Model Transformation, Mapping, and Comparison class) All types of diagrams (and models) we analyzed (including some outside the UML domain such as C2SADEL [5]) can be positioned relative to these three dimensions. The first of the three dimensions in Figure 2 is the lowlevel high level dimension. This dimension denotes the level of abstraction of diagrams. For instance an architectural model is usually more abstract (high level) than a design model. ....

Taylor, R. N., Medvidovic, N., Anderson, K. N., Whitehead, E. J. Jr., Robbins, J. E., Nies, K. A., Oreizy, P., and Dubrow, D. L., A Component- and Message-Based Architectural Style for GUI Software IEEE Transactions on Software Engineering, vol. 22, pp. 390-406, 1996.

....as a foundation for our model repository. The repository contains all relevant product information about the designed software system. Having used UML as a meta model does, however, not exclude using ADLs in our integration approach. To this end, we have found ways to integrating ADLs (e.g. C2 [12]) in UML [5] Note that we adopted the use of UML s extensibility mechanism to represent C2 ADL concepts foreign to UML [1] Although this mechanism has limitations it is still sufficient for our purposes here. To manipulate and analyze the model repository, we use Rational Rose as well as our ....

Taylor R. N., Medvidovic N., Anderson K. N., Whitehead E. J. Jr., Robbins J. E., Nies K. A., Oreizy P., and Dubrow D. L.: A Component- and MessageBased Architectural Style for GUI Software. IEEE Transactions on Software Engineering 22(6), 1996, 390-406.

....of views, such as class, object, sequence, activity, statechart, and use case views. Those views span a wide range of concerns and support structural, behavioral and scenario modeling. In [3] we have investigated the issue of architecture to design integration in the context of the C2 ADL [4] and the Unified Modeling Language (UML) There, we discussed how to transform C2 architecture descriptions into (high level) UML designs. Since designs are refinements of architectures and those designs are likely further refined into lowerlevel designs (and implementations) they could become ....

Taylor, R.N., Medvidovic, N., Anderson, K.N., Whitehead, E.J., Jr., Robbins, J.E., Nies, K.A., Oreizy, P., and Dubrow, D.L.: A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, vol. 22, no. 6, pp. 390-406, 1996.

....the structuring of fault tolerance systems, allowing their complexity to be manageable. 2.2. The C2 Architectural Style The C2 architectural style is a component based style directed at supporting large grain reuse and flexible system composition, emphasizing weak bindings between components [23]. In this style components of a system may be completely unaware of each other, as when one integrates various commercial off the shelf components (COTS) which may have heterogeneous style and implementation language. These components communicate only through asynchronous messages mediated by ....

....the normal operation is resumed or the exception is propagated to PumpControlStation. 4. CONCLUSIONS In this paper, we have investigated the structuring of faulttolerant component based systems, at the architectural level. For the purpose of our work we have employed the C2 architectural style [23], which is a style that promotes the development of component based systems using off the shelf components. The intent was to provide an idealized C2 component with structure and behaviour equivalent to the idealized fault tolerant component [1] The communication rules between components in the ....

R. N. Taylor, N. Medvidovic, K. M. Anderson, E. J. Whitehead Jr., J. E. Robbins, K. A. Nies, P. Oreizy, and D. L. Dubrow. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, June 1996.

No context found.

R.N. Taylor, N. Medvidovic, et al. A Component- and Message -Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, 22(6), June 1996.

No context found.

Taylor, R.N., Medvidovic, N., Anderson, K.N., Whitehead, E.J., Jr., Robbins, J.E., Nies, K.A., Oreizy, P., and Dubrow, D.L.: A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, vol. 22, no. 6, pp. 390-406, 1996.

No context found.

R.N. Taylor, N. Medvidovic, K.M. Anderson, E.J. Whitehead Jr., and J.E. Robbins, "A Component- and Message-Based Architectural Style for GUI Software," IEEE Trans. Software Eng., vol. 22, pp. 390-406, June 1996.

No context found.

R. N. Taylor, N. Medvidovic, K. M. Anderson, E. J. Whitehead, J. E. Robbins, K. A. Nies, P. Oreizy, D. L. Dubrow. A Component - and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, June 1996.

No context found.

R.N. Taylor et. al. A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, June 1996.

No context found.

Taylor, R.N., et al. A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering. 22(6), p. 390-406, June, 1996.

No context found.

R.N. Taylor, N. Medvidovic, et al. A Component- and Message -Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, 22(6), June 1996.

No context found.

R.N. Taylor, N. Medvidovic, et al. A Component- and Message -Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, 22(6), June 1996.

....architectures they can model. Some ADLs are very generic, like Darwin and Wright, while others are better suited to specific domains or architectural styles: Rapide specifically supports event based architectures; C2SADEL was built to model architectures in the multi level notify request C2 style [41]; MetaH was built to model embedded systems, including both hardware and software components. Another way to differentiate ADLs is by what features of software systems they model. Koala, for instance, models product lines by modeling variation points in an architecture. C2SADEL and Darwin are both ....

R. N. Taylor et. al. A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, June 1996.

....of the extra functional properties of a system such as its availability, throughput, security and scalability. Various architecture styles motivated by software connectors have been studied, e.g. pipe and filter [14] real time data feeds [15] event driven architecture [16] messagebased style [17] and middlewarebased style [18] Architectural styles are an important mechanism for enabling reuse in family architectures [11, 13] which implies that software connectors have a major role to play in enabling architecture based reuse. Connectors provide bounded ambiguity that is necessary for ....

....using the distributor dimensions delivery and addressing. We are currently developing an infrastructure for using and experimenting with connectors for implicit invocation, real time communication and parallel execution. This infrastructure builds upon our previous work with event connectors [17]. 4. Four Way Refinement and Evolution Having discussed an approach to modeling family architectures and instantiating them into product architectures, we now discuss how to refine the resulting product architectures into the individual product design. A product architecture constitutes an ....

R. N. Taylor, N. Medvidovic, K. M. Anderson, E. J. Whitehead and J. E. Robbins. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 1996, 22(6), pp. 390-406.

No context found.

Taylor, R. N., Medvidovic, N., Anderson, K. N., Whitehead, E. J. Jr., Robbins, J. E., Nies, K. A., Oreizy, P., Dubrow, D. L.: "A Component- and Message-Based Architectural Style for GUI Software," IEEE Transactions on Software Engineering, 22(6), pp. 390-406, 1996.

....expressive option. In [12] we describe this strategy and discuss how we use UML stereotypes to represent modeling constructs of several ADLs in UML. Specifically, we created a development environment called SAAGE which automates this transformation in context of the C2SADEL specification language [16]. The UML specification resulting from this transformation is stored as a Rational Rose TM model [14] A portion of the Rose model for an application architecture describing a cargo router is depicted in Figure 2: it depicts a part of the C2 architecture as a UML collaboration diagram (left) ....

Taylor R. N., Medvidovic N., Anderson K. N., Whitehead E. J. Jr., Robbins J. E., Nies K. A., Oreizy P., and Dubrow D. L.: A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering 22(6), 1996, 390-406.

....descriptions and containing rationale. The result of CBSP is an intermediate model that captures architectural decisions of requirements in form of an incomplete architecture. At the current state we applied CBSP in context of EasyWinWin [2,6] a requirements elicitation technique, and C2 [12], an architectural style for highly distributed systems. However, we believe that it can be applied to other requirements elicitation and architecture capture approaches. The following discusses the basics of our CBSP approach in context of an example followed by an update of the current state of ....

....process and vice versa. Deriving Validating Architectural Styles out of CBSP In our work to date, we have chosen to use architectural styles as guides in transforming the initial architectural decisions produced by CBSP into an actual architecture. Specifically, we have employed the C2 style [12] as discussed above. However, each style is particularly well suited for a certain type of problem; therefore, our intent is to extend CBSP to leverage other styles as well. We have begun exploring the feasibility of composing CBSP artifacts into an architecture according to the Pipeand Filter ....

Taylor R. N., Medvidovic N., Anderson K. N., Whitehead E. J. Jr., Robbins J. E., Nies K. A., Oreizy P., and Dubrow D. L.: A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering 22(6), 1996, 390-406.

No context found.

Taylor R. N., Medvidovic N., Anderson K. N., Whitehead E. J. Jr., Robbins J. E., Nies K. A., Oreizy P., and Dubrow D. L.: A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering 22(6), 1996, 390-406.

No context found.

Taylor R. N., Medvidovic N., Anderson K. N., Whitehead E. J. Jr., Robbins J. E., Nies K. A., Oreizy P., and Dubrow D. L.: A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering 22(6), 1996, 390-406.

No context found.

Taylor, R.N., Medvidovic, N., Anderson, K.N., Whitehead, E.J. Jr., Robbins, J.E., Nies, K.A., Oreizy, P., and Dubrow, D.L. 1996. A component- and message-based architectural style for gui software, IEEE Transactions on Software Engineering, 22:390--406.

No context found.

R. N. Taylor, N. Medvidovic, K. M. Anderson, E. J. Whitehead, Jr., J. E. Robbins, K. A. Nies, P. Oreizy, and D. L. Dubrow, "A component- and message-based architectural style for gui software," IEEE Trans. Softw. Eng., vol. 22, no. 6, pp. 390--406, 1996.

No context found.

R. N. Taylor et al., "A Component- and MessageBased Architectural Style for GUI Software," IEEE Trans. Software Eng., June 1996, pp. 390-406.

No context found.

Taylor, R. N., Medvidovic, N., Anderson, K. M., Whitehead, E. J.,Rob6G5 J. E., Nies, K. A., Oreizy, P.,Dub#9# D. L.: A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering, Vol. 22, No. 6, Jun 1996 25. Web6#G /55 http://www.w3.org/2002/ws/

No context found.

R. N. Taylor, N. Medvidovic, K. M. Anderson, E. J. Whitehead, Jr., J. E. Robbins, K. A. Nies, P. Oreizy, and D. L. Dubrow. "A Component- and MessageBased Architectural Style for GUI Software", IEEE Transactions on Software Engineering, vol. 22, no. 6, pages 390-406, June 1996.

No context found.

R. N. Taylor, et.al. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, June 1996.

No context found.

R. N. Taylor, N. Medvidovic, K. M. Anderson, E. J. W. Jr., J. E. Robbins, K. A. Nies, P. Oreizy, and D. L. Dubrow. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, 1996.

No context found.

R. N. Taylor, N. Medvidovic, K. M. Anderson, J. E. James Whitehead, J. E. Robbins, K. A. Nies, P. Oreizy, and D. L. Dubrow. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, June 1996.

No context found.

Taylor R. N., Medvidovic N., Anderson K. N., Whitehead E. J. Jr., Robbins J. E., Nies K. A., Oreizy P., and Dubrow D. L.: A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering 22(6), 1996, 390-406.

No context found.

R. N. Taylor, N. Medvidovic, K. M. Anderson, E. J. Whitehead Jr., J. E. Robbins, K. A. Nies, P. Oreizy, D. L. Dubrow. A component- and message-based architectural style for GUI software. IEEE Transactions on Software Engineering, 22(6):390--406, June 1996.

No context found.

. Richard N. Taylor, Nenad Medvidovic, Kenneth M. Anderson, E. James Whitehead Jr., Jason E. Robbins, Kari A. Nies, Peyman Oreizy, and Deborah L. Dubrow, A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering, Vol. 22, No. 6, June 1996, pp. 390 406, http://sunset.usc.edu/~neno/teaching/s99/C2-TSE.pdf

No context found.

Taylor R.N, Medvidovic N., Anderson K.M., Whitehead E.J., Robbins J.E., Nies K.A., Oreizy P., Dubrow D.:A Component- and Message-Based Architectural Style for GUI Software. published in IEEE Transactions on Software Engineering, June 1996

No context found.

R. N. Taylor, N. Medvidovic, K.M. Anderson, Jr. E. J. Whitehead, and J.E. Robbins. A component- and message- based architectural style for GUI software. In Proceedings of the 17th International Conference on Software Engineering, pages 295-304, April 1995.

No context found.

Taylor R. N., Medvidovic N., Anderson K. N., Whitehead E. J. Jr., Robbins J. E., Nies K. A., Oreizy P., and Dubrow D. L.: A Component- and Message-Based Architectural Style for GUI Software. IEEE Transactions on Software Engineering 22(6), 1996, 390-406.

No context found.

R. N. Taylor, N. Medvidovic, K. N. Anderson, E. J. Jr. Whitehead, J. E. Robbins, K. A. Nies, P. Oreizy, and D. L. Dubrow, A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering, vol. 22, pp. 390-406, 1996.

No context found.

Taylor R.N., et al., A Component- and Message-Based Architectural Style for GUI Software. IEEE-Transactions on Software Engineering, 22(6), 1996.

No context found.

Taylor, R.N., "A Component- and Message-Based Architectural Style for GUI Software", IEEE Transactions on Software Engineering, Vol. 22, No. 6, 1996.

No context found.

R. Taylor, N. Medvidovic, K. Anderson, E. Whitehead, J. Robbins, K. Nies, P. Oreizy, and D. Dubrow. A component- and message-based architectural style for GUI software. IEEE Trans. Software Eng., 22(6):390--406, June 1996.

No context found.

R. N. Taylor, N. Medvidovic, K. M. Anderson, E. J. Whitehead Jr., J. E. Robbins, K. A. Nies, P. Oreizy, and Dubrow D. L. A Component- and MessageBased Architectural Style for GUI Software. IEEE Software, June 1996.

First 50 documents  Next 50

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