D. Garlan. Software architecture: a roadmap. In Proceedings of International Conference on Software Engineering (ICSE00) Limerick, Ireland, 2000.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....advanced decomposition and composition mechanisms throughout the whole software lifecycle. Most of the existing software design techniques basically support the data abstraction of the object oriented paradigm, and also more advanced concepts of abstraction such as global control flow abstraction [1]. In general, global control flow abstraction means a type of separation of concerns between intra object and inter object behavior. Data abstraction is of benefit largely in the management of development complexity, and in the facilitation of the reuse of legacy program modules. However, program ....

.... new Object [ Bae, Doo Hwan ) Server s1 = new Server( 1, Teacher.class, new Class [ String.class , new Object [ Cha, Sung Deok ) Client c[ new Client[4] public ClientServer( super( c[0] new Client( Student.class, new Class[ String.class , new Object[ Lee ) c[1] = new Client( Student.class, new Class[ String.class , new Object[ Kim ) c[2] new Client( Student.class, new Class[ String.class , new Object[ Park ) c[3] new Client( null, null, null ) an instantiation without any core class s0.connect( c[0] s0.connect( c[1] ....

[Article contains additional citation context not shown here]

Garlan D. Software architecture: A roadmap. Proceedings of the International Conference on Software Engineering: On the Future of Software Engineering, Limerick, Ireland, 2000; 91--101.

....depend on the kind of documentation being developed: in some situations a component may be as large as a major subsystem; in others it might be as small as a single object class. Typically components represent system structures such as major modules, computational elements, and run time processes[3]. By providing an abstract description of a system, the architecture exposes certain properties, while can help ensure others that a system will satisfy, key requirements in such areas as performance, reliability, portability, scalability, and interoperability [2] Ideally this representation ....

....in situations where the structure of a system s code can be partitioned into a linear sequence of logical modules, with certain visibility restrictions between those modules. The restrictions allow one to improve portability and maintainability, since the limit the effect of changes to the code [3]. As for the problem domain view, the first step is to establish what aspects of an architecture a layer diagram should capture. The following three items are paramount: The system and its surrounding environment. Dependency isolation between layers. Interaction mechanisms between ....

[Article contains additional citation context not shown here]

Garlan, D. "Software Architecture: a Roadmap". Scholl of Computer Science, Carnegie Mellon University. Pittsburg, PA.

.... levels of granularity, providing a partial blueprint for development by indicating the major components and dependencies among them, exposing the dimensions among which a system is expected to evolve, providing analysis opportunities at early stages of development, and for basic management support [3]. In order to fulfil their expected roles, software architectures should be modularised. This modularisation plays a triple role: It facilitates understanding by using high level abstractions and reducing the complexity of the task at hand, It highlights areas where work can occur in a ....

D. Garlan, Software Architecture: a Roadmap, in The Future of Software Engineering, A. Finkelstein, Ed.: ACM Press, pp. 93-101, 2000.

....elements [44] and languages [43] has also continued. The institutions of the area are also maturing. The Transactions on Software Engineering had a special issue on software architecture in 1995 [20] The special roadmap track at the ICSE 2000 conference included software architecture [22] among its topics to survey. The current ICSE has four sessions on architectural topics, and of the 22 affiliated tutorials, 8 are related to UML and 6 others have clear architectural elements. A standalone conference, the Working IEEE IFIP Conference on Software Architecture, will be held in ....

David Garlan. Software architecture: a roadmap. The Future of Software Engineering

....for more information and motivation to want to go there. More exhaustive treatises on the subject exist (e.g. 4] 10] 22] 37] 38] 40] and are being added to with increasing regularity. There have also been a number of attempts at predicting the future of software architecture (e.g. [17], 4] These have listed areas such as architecture for dynamic systems, reflective architectures, architecture migration, and others as hot topics of research and practice for the future. One thing is for certain, however: as long as people continue to build large, complex, software intensive ....

Garlan, D., "Software Architecture: A Roadmap", The Future of Software Engineering, A. Finkelstein, ed., ACM Press, 2000.

....the last ten years, software architecture has turned out to be a significant area of research and practice in software engineering. Representing architectures in an unambiguous and explicit way has been characterized as a critical issue in the design and construction of any complex software system [1]. The major goals of software architecture consist of providing blueprints for constructing software intensive systems, helping stakeholders to understand, manage and analyze fundamental system properties, as well as providing means that allow stakeholders to communicate and reason about such ....

Garlan, D.: Software Architecture: A Roadmap. In The Future of Software Engineering; Anthony Finkelstein (Ed). 22nd International Conference on Software Engineering, ICSE 2000; University of Limerick, Ireland, 4-11 June 2000.

....the examples of current practice. Nevertheless, compared to other fields, even the core of the software development curriculum must change rapidly. For example, most curricula have not kept up with practice in recognizing the role of good abstractions for software architectures in software design [3]. As another example, within the past few years the conversion of the Internet from an email telnet ftp service for professionals to an information distribution system embedded in popular culture has introduced new techniques and models for design and development: Open source software ....

David Garlan. Software Architecture: A Roadmap. In this volume.

....differ in certain key requirements. The process of identifying core requirements in order to develop architectures that are (a) stable in the presence of change, and (b) flexible enough to be customised and adapted to changing requirements, is one of the key research issues in software engineering [27]. 9 Integrated Requirements Engineering RE is a multi disciplinary activity, deploying a variety of techniques and tools at different stages of development and for different kinds of application domains. Methods provide a systematic approach to combining different techniques and notations, and ....

.... to express software architectures and reason about their behavioural properties, there is still an open question about how to analyse what impact a particular architectural choice has on the ability to satisfy current and future requirements, and variations in requirements across a product family [27]. 5. Reuse of requirements models. We expect that in many domains of application, we will see the development of reference models for specifying requirements, so that the effort of developing requirements models from scratch is reduced. This will help move many software projects from being ....

Garlan, D. (2000). Software Architecture: A Roadmap. In this volume.

No context found.

D. Garlan. Software architecture: a roadmap. In Proceedings of International Conference on Software Engineering (ICSE00) Limerick, Ireland, 2000.

No context found.

Garlan, D. (2000). Software Architecture: A Roadmap. In: A. Finkelstein (ed): The Future of Software Engineering.

No context found.

. David Garlan, Software architecture: a Roadmap, Proceedings of the Conference on The Future of Software, ELimerick, Ireland, May 2000, Page 91 101, ISBN 1-58113-253-0

No context found.

David Garlan.: Software architecture: a roadmap. ICSE - Future of SE Track (2000) 91--101

No context found.

: The Future of Software Engineering, 22 nd Intl Conf. Software Engineering, IEEE, 2000, pages 91-103

No context found.

Garlan, D., "Software Architecture: a Roadmap," in The Future of Software Engineering, A. Finkelstein, Ed.: ACM Press, 2000.

No context found.

Garlan, D. (2000) Software Architecture: A Roadmap. in this volume.

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