David Garlan and Dewayne Perry. Software architecture: Practice, potential, and pitfalls. In 16th International Conference on Software Engineering, pages 363--364, Sorrento, Italy, May 1994. IEEE Computer Society Press. Panel Introduction.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....among autonomous Internet repositories, making them more active and responsive to other objects on the network. Some related work in this direction has already been done in the area of interconnection languages (e.g. Conic [75] and in the more general emerging field of software architecture [36], where researchers have been looking at formalisms to define the structure of complex (distributed) systems (e.g. 1] 7.2.2 Wide Area Modeling This direction has been addressed in Oz only preliminarily at best (in Section 5.6) The main research issue here is to explore constructs for ....

David Garlan and Dewayne Perry. Software architecture: Practice, potential, and pitfalls. In 16th International Conference on Software Engineering, pages 363--364, Sorrento, Italy, May 1994. IEEE Computer Society Press. Panel Introduction.

....with other objects to enact their responsibilities. This style of communication protocol results in a decentralised system architecture. Understanding software architectures in terms of structural patterns and component interactions help in the development and evolution of complex systems [13]. Object Oriented software system development commences with a set of model requirements. Scenarios are used to describe the modelling requirements as a series of activities. A modeller does scenario based development by analysing, designing and validating the components of a model. An incremental ....

....structures to model the computational behaviours, and data structures and the connector types that use interaction models for communicating between components. Traditional software systems document the overall architecture of an individual system with textual description and box and line diagrams [13]. In contrast to this style of system development, researchers such as [1] refer to recent trends of system architects working on architectural styles which can be used to define the constraints on the structures for a family of system architectures. For example, the system architects working on ....

Garlan, D., and Perry, D. Software architecture: Practice, potential, and pitfalls. In ICSE-16 (May 1994), IEEE Computer Society Press, p. 363.

....algorithms required by an application, with a foundation in traditional paradigms such as functional programming and object oriented programming. Configuration determines which system components should exist, and how they are inter connected, and is based on principles of software architecture[GS93, PW92, GP94]. Finally coordination is concerned with the interaction of the various system components, and is founded on recent paradigms such as process calculi[Mil89, MPW92, Mil91] and the notion of interaction machines[Weg96] Having to perform three paradigm shifts during the design and implementation of ....

....of layers, their transparent integration and interactive nature of the layers have not been addressed. These are important issues when coordination is viewed as a software engineering issue. For the issue of configuration this perspective has been taken by research in software architecture[GS93, PW92, GP94, RE96]. The focus has only been on layer separation though, without paying much attention to transparent integration and without recognising coordination as a separate layer. Additionally the interactive aspects have been neglected and even dynamic layers are sometimes not supported. More recently, some ....

D. Garlan and D. Perry. Software architecture: Practice, potential and pitfalls. In Proc. of the 16th Int. Conf. on Software Engineering, May 1994.

....Engineering community, most notably by Garlan and Shaw [1] and Perry and Wolf [2] that when systems are constructed from many components, the organisation or architecture of the overall system presents a new set of design problems. One of the architectural concerns identified by Garlan and Perry [3] is the high level description of systems based on graphs of interacting components. They identify components as the primary points of computation in a system and connectors to define the interactions between these components. Our work addresses this concern in the context of distributed systems ....

D. Garlan and D. Perry, Software Architecture: Practice, Potential and Pitfalls (Panel Introduction), Proc. of 16th Intl. Conf. on Software Engineering, S orrento, May 1994.

....they are not aimed at integration with existing systems or operation in an open environment. Furthermore, only limited facilities exist for re using coordination patterns, and coordination is typically embedded in application code rather than being separated. Research in software architecture[GS93, PW92, GP94, RE96b], by contrast, has placed considerable emphasis on layer separation. However, the distinct role of coordination has only been recognised recently. Consequently several systems have emerged that address coordination issues, usually as extensions to existing systems. Examples of this are ....

D. Garlan and D. Perry. Software architecture: Practice, potential and pitfalls. In Proc. of the 16th Int. Conf. on Software Engineering, May 1994.

....The architecture enables the provision of advanced tool support for configuration management and its integration with other aspects of system management. 1 Introduction We can view a distributed system as a collection of distributed agents 1 that interact with each other [MDK93, GS93, PW92, GP94] The concerns of a distributed system can be separated into four parts (cf. Fig. 1) The communication part defines how agents communicate with each other. The computation part defines the implementation of the behaviour of individual agents. It thus determines what is being ....

D. Garlan and D. Perry. Software architecture: Practice, potential and pitfalls. In Proc. of the 16th Int. Conf. on Software Engineering, May 1994.

....to generate Darwin programs from configurations thus allowing for the inclusion of existing systems into new programs. 1 Introduction It has been observed in the Software Engineering community that systems which are constructed from a large number of components have organisational difficulties [7, 14, 6]. There is a real need for clear design specifications of component based systems at this level. This is the level of the design which deals with the high level organisation of computational elements and the interactions between those elements. We are concerned with the demonstration of soundness ....

D. Garlan and D. Perry. Software architecture: Practice, potential and pitfalls. In Proc. of the 16th Int. Conf. on Software Engineering, May 1994.

.... and Architectural Style While there is currently no single well accepted definition of software architecture it is generally recognized that an architectural design of a system is concerned with describing its gross decomposition into computational elements and their interactions [PW92, GS93b, GP94] Issues relevant to this level of design include organization of a system as a composition of components; global control structures; protocols for communication, synchronization, and data access; assignment of functionality to design elements; physical distribution; scaling and performance; ....

David Garlan and Dewayne Perry. Software architecture: Practice, potential, and pitfalls. In Proceedings of the Sixteenth International Conferenceon Software Engineering, May 1994. Panel Introduction.

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