Abowd, G., Allen, R., and Garlan, D. Using Style to Give Meaning to Software Architecture. In Proc. Of SIGSOFT '93: Foundations of Software Engineering, Software Engineering Notes 118(3), pp. 9-20, ACM Press, Dec. 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....library approach, the structure of interconnections between components is reused, not the components themselves. Software architecture reuse is based on the definition of architectural styles , that is descriptions of families of architectural designs that share a set of common assumptions [Abowd93] An architectural style provides a specialised component vocabulary (e.g. client, server, application server etc. a connector vocabulary (e.g. pipe, data stream etc. and a set of rules for building specific topologies using components and connectors. Architectural styles improve the ....

Abowd, G., Allen, R., and Garlan, D. Using Style to Give Meaning to Software Architecture. In Proc. Of SIGSOFT '93: Foundations of Software Engineering, Software Engineering Notes 118(3), pp. 9-20, ACM Press, Dec. 1993.

....understand the ramifications of changes, and thereby more accurately estimate costs of modifications [6] 4. Analysis: Architectural description provides new opportunities for analysis [6] includinghigh level forms of system consistency checking [2, 4] conformance to an architectural style [1], and domain specific analyses for architectures that conform to specific styles. 3 Purpose of the panel Whatever the long term impact of software architecture may turnout tobe, an appropriatestartingpoint is a concrete appraisal of the current state of the practice in the use of software ....

Gregory Abowd et al. Using style to give meaning to software architecture. In Proc. of SIGSOFT'93: Foundations of Software Engineering, December 1993.

....Architecture in Section 3.1.1. Another approach to utilising architectural styles is to encode a description of the components and constraints of an architecture into an software development environment. Thus the environment forces the designer to conform to the specified style. Garlan et al. [1, 30] describe an architecture in terms of its components, connectors, configurations, ports, and roles. Hence a description of an architectural style provides ffl a vocabulary of the basic design elements (components and connector types) ffl a set of configuration rules which constrain how ....

....on the description of design artifacts has been done by practitioners who do not share a belief in the merit of formal specifications: they used natural language and diagrams for their documentation. As a consequence there is only a small body of work on how to formally specify design artifacts [1, 20, 23, 24, 36, 37, 59]. There is scope for further work in this area. ffl Experimental validation of claims that certain documentation or specification styles do improve understanding in practice is required. All aspects of research into software development need a firm experimental foundation. Evaluation problems ....

G. Abowd, R. Allen, D. Garlan, Using style to give meaning to software architecture, Proceedings of SIGSOFT'93: Foundations of Software Engineering, ACM Software Engineering Notes 18, 3 (December 1993) 9--20.

....a design based on the architecture. Another approach to utilizing architectural styles is to encode a description of the components and constraints of an architecture into an software development environment. Thus the environment forces the designer to conform to the specified style. Garlan et al. [1, 34] describe an architecture in terms of its components, connectors, configurations, ports, and roles. Hence a description of an architectural style provides ffl a vocabulary of the basic design elements (components and connector types) ffl a set of configuration rules which constrain how ....

G. Abowd, R. Allen, and D. Garlan. Using style to give meaning to software architecture. In Proceedings of SIGSOFT'93: Foundations of Software Engineering, ACM Software Engineering Notes, volume 18 of 3, pages 9--20, December 1993.

....architectural trade offs in an informed manner, in full realization of the pros and cons of any architectural operation. 11 5 Conclusions The majority of research in software architecture and design concentrates on formalizing and analyzing existing or already designed systems or styles (e.g. [1], 9] 11] There has been little work on a generative approach to architectural design. The unit operations and the associated design space developed here provides generative and structure transforming operations, along with the ability to reason about architectural trade offs with respect to ....

G. Abowd, R. Allen, D. Garlan, "Using Style to give Meaning to Software Architecture", Proceedings of SIGSOFT `93, Software Engineering Notes, 118(3):9-20.

....Work is currently in progress to provide open systems binding, the ability to manage group communication abstractions and component migration. We are also extending the definition of the Darwin language together with its calculus semantics to capture the notion of architectural styles [20]. We have chosen to ignore component parameterisation in arriving at the calculus model. Component parameters can determine the final structure of a system through the conditional and replicator constructs. While these could be modelled directly in calculus the resulting model is clumsy and ....

G. Abowd, R. Allen and D. Garlan, Using style to give meaning to software architecture, In Proceedings of the SIGSOFT'93: Foundations of Software Engineering, Software Engineering Notes 118(3), pp.9-20, ACM Press, Dec. 1993.

....Daniel Jacson, Mary Shaw, and Jeannette Wing [26] is one example. Their innovative claim is that connectors are first class entities, just as components are, in a system. They also have an approach for system consistency checking [4] and for conformance definition to an architectural style [2]. Other work contributing to the field of languages, tools and environments for architectural design include architecture description languages (ADLs) ADLs address the need to find expressive notations for representing architectural designs and styles. The focus of this research is to provide ....

....and global control structure; assignment of functionality to system components; protocols for communication and synchronization; scaling and performance; and selection amoung design alternatives. The X Open DTP architecture defines constraints on the structure of compliant system instances [79, 2] and is therefore a standard. A standard in the sense that it is a constraint on compliant systems. Codification of such architectural standards can be critically important in assuring that the various components of a system are integrated correctly. Architectural requirements and behavioral ....

[Article contains additional citation context not shown here]

G. Abowd, R. Allen, and D. Garlan. Using style to give meaning to software architecture. In Proceedings of SIGSOFT'93, Software Engineering Notes, volume 18, pages 9--20. ACM Symposium on Foundations of Software Engineering, December 1993.

No context found.

G. Abowd, R. Allen, and D. Garlan, "Using Style to Give Meaning to Software Architecture," Proc. SIGSOFT '93: Foundations Software Eng., ACM, New York, 1993. Also in Software Eng. Notes, Dec. 1993, pp. 9-20.

....of building such environments by providing a common basis for implementing them or at least certain key parts of them. Hence, our research is attacking a more general problem. The second area is research aimed at providing a rigorous basis for architectural specification and design [GN91, AG92, AAG93, PW92] To the extent that such research clarifies the nature of architectural representation and the meaning of architectural style, our work builds on those results. In particular, the basic model of architectural representation (Section 4.3) and the elements of style description (Section 3) ....

.... the ISO OSI 7 layer model [McC91] some user interface frameworks [K 91] and a large variety of domain specific approachesin areas such as avionics [BV93] and mobile robotics [SLF90, HR90] More specifically, we observe that architectural styles typically determine four kinds of properties [AAG93] 1. They provide a vocabulary of design elements component and connector types such as pipes, filters, clients, servers, parsers, databases etc. 2. They define a set of configuration rules or topological constraints that determine the permitted compositions of those elements. For ....

[Article contains additional citation context not shown here]

Gregory Abowd, Robert Allen, and David Garlan. Using style to give meaning to software architecture. In Proceedingsof SIGSOFT'93: Foundationsof Software Engineering, Software Engineering Notes 118(3), pages 9--20. ACM Press, December 1993.

....or blackboard organization. These convey widespread, if informal, understanding of the descriptions, and allow engineers to quickly communicate their designs to others. In many cases, such as those mentioned above, architectural idioms represent what has been termed an architectural style [AAG93]. As we describe later, an architectural style provides a design vocabulary (clients and servers, pipes and filters, blackboards and knowledge sources, etc. together with rules for how elements in that vocabulary can be combined. In essence, a style provides a specialized design language for a ....

....about the structure and underlying computational model of a system. An important class of architectural idioms constitute what some researchers have termed architectural styles. An architectural style characterizes a family of systems that are related by shared structural and semantic properties [AAG93]. More specifically, styles typically provide four things: 1) A Vocabulary of design elements component and connector types such as pipes, filters, clients, servers, parsers, databases, etc. 2) Design rules or constraints that determine the permitted compositions of those elements. For ....

Abowd, G., Allen, R. and Garlan, D. Using Style to Give Meaning to Software Architecture. In Proc. of SIGSOFT `93: Foundations of Software Engineering, Software Engineering Notes 118(3), pp 9-20, ACM Press, Dec. 1993.

No context found.

G. Abowd, R. Allen and D. Garlan, Using style to give meaning to softwarearchitecture, In Proceedings of the SIGSOFT'93: Foundations of Software Engineering, Software Engineering Notes 118#3#, pp.9-20, ACM Press, Dec. 1993.

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