Keller RK, Schauer R. Design components: Towards software composition at the design level. Proceedings of the 20th International Conference on Software Engineering, 1998; 302--311.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Structural composition focuses more on the actual realization of the design rather than abstractions as role models. Behavioral composition techniques such as roles [30,18] leave several choices to the designer with less guidelines on how to continue to the class design phase. Keller and Schauer [21,22] address the problem of software composition at the design level using design components. Their approach and ours share the same objective of creating software designs that are based on well defined and proven design patterns packaged into tangible, customizable, and composable design components. ....

Keller, R., and R. Schauer. Design Components: Towards Software Composition at the Design Level. Proceedings of 20 International Conference on Software Engineering, ICSE'98, pp302-311, Kyoto, Japan, April 19-25, 1998.

....contract is a set of rules and constraints on the interaction between any two objects and the contract superposes its behavior on the interaction of the two objects between which the contract is valid. Adaptation is achieved by changing the contract and not the objects. Design components [26] are another way of adapting. Design components are collections of design patterns [27] The design components can be customized and composed to form software architectures. Another way is to provide an adaptable interface to each component [28] The code in the adaptable interface can be changed ....

Keller, R.K., Schauer, R. Design Components: Towards Software Composition at the Design Level,Proceedings of International Conference on Software Engineering, April 19-25, 1998, Kyoto, Japan, pp. 302-311.

....of components to form a larger component or application presents many problems, such as how to cope with incompatible interfaces and how to provide a unified interface for a composed component. Much research has been done on how to compose software in general and components in particular (Keller and Schauer, 1998; Lewandowski, 1998; Bergmans, 2000) Because component composition is a research topic in its own, we exempt ourselves from discussion it further. The structural view of an application at the component level can be represented using package diagrams. The use of package diagrams aims at capturing ....

Keller, R.K. and Schauer, R. 1998: Design components: toward software composition at the design level. In Proceedings of the 1998 International Conference on Software Engineering, 302-311.

....In FRED [3] DP solutions are expressed at the general level as design contracts using the textual specification language Cola. The specialisation template binds a design contract to certain entities in the Java framework. Unlike our instance map, it comes out at the time of implementation. In [5], DP solutions can be composed at the design level. They are represented as an UML extension of packages. DP packages can be specialized at the general level in a way that is similar to class inheritance, but their integration is based on simple renaming. Our approach relies on a graph based ....

#Keller, R. D., Schauer, R.: Design Components: Towards Software Composition at the Design Level. In: Proc. of ICSE'98 International Conference on Software Engineering, IEEE Computer Society (1998)

....pattern according to our concept refers to a detailed description of a given solution to the problem and is typically published in a catalogue, pattern instance refers to those parts of an actually developed software that result from pattern application. A similar differentiation may be found in [5, 7, 9]. In addition to pattern and pattern instance, we introduce the term pattern prototype. Pattern prototype refers to the solution part of a pattern and is represented in the repository in a way suitable for pattern instantiation. Relationships among pattern, its prototype and instance are ....

....approach does not support multiple occurrences of some pattern participants and dependencies among them. Also, to create several possible instances within the same software system may be troublesome. An approach that relies on formulating patterns in a tangible and composable form is presented in [7]. An extension to Unified Modeling Language is proposed that depicts design pattern components in the notation similar to package notation. Different constituents that describe the design component can be displayed by zooming into detailed view. In [5] every pattern is represented by a prototype ....

#Keller, R. D., Schauer, R.: Design Components: Towards Software Composition at the Design Level. In: Proc. of the 20 th International Conference on Software Engineering, Kyoto, IEEE Computer Society (1998) 302-311

....design constraints. Design composition is discussed in Section 6. Considerations about infrastructure are made in Section 7. Section 8 follows with a review of related work. Section 9 draws conclusions and points out future work. 2. FOUNDATION Design patterns [9] the notion of design components [11] and role modeling [17, 21] build the cornerstone of our approach to compositional design reuse. Design Patterns Design patterns are frequently described as a problem context solution triple [5, 9] A design pattern systematically names, motivates, and explains a general design that addresses ....

....common design vocabulary, a documentation and learning aid, an adjunct to existing methods, and a target for refactoring. Design components address the blurring of design patterns during implementation and maintenance, and suggest a more systematic approach to define, implement, and trace them [11]. Design components are reified design patterns, Collections of design components can be envisioned that provide solutions to design problems based on role models. These design components are to be reused in a compositional way. It is understood that they be adequately and systematically ....

Rudolf K. Keller and Reinhard Schauer. Design Components: Towards Software Composition at the Design Level, Proceedings of ICSE 20, pages 302--311, Kyoto, Japan, IEEE, April 1998.

....K. Keller Reinhard Schauer 1 Introduction As part of the project SPOOL, a joint university industry collaboration between the University of Montreal and Bell Canada, we are developing a repository based environment for design recovery and analysis in largescale C telecommunications software [5, 9]. The purpose of this environment is to provide automated support for the extraction of design models from source code, by stepwise, human controlled transformation of the source code into more abstract forms of representation. To use the functionality of other tools, such as source code parsers ....

Rudolf K. Keller and Reinhard Schauer. Design components: Towards software composition at the design level. In Proceedings of the 20th International Conference of Software Engineering, pages 302-311, Kyoto, Japan, April 1998.

....stacks NMI Legend: containment referral management 3 19 At an early stage in the development of Layla, we decided to take an approach based on design patterns. Aware of their potential of making architectures easier to modify, maintain, and reuse and of their documentation value [2, 3, 7, 11], we wanted to verify whether these qualities also hold in a domain as complex as NMIs, and in which way domain specific aspects would come into play. A further objective was to organize the system of patterns that would result from our design in a systematic and coherent way. The resulting ....

Rudolf K. Keller and Reinhard Schauer. Design components: Towards software composition at the design level. In Proceedings of the Twentieth International Conference on Software Engineering , Kyoto, Japan, 1998. IEEE. to appear.

No context found.

Keller RK, Schauer R. Design components: Towards software composition at the design level. Proceedings of the 20th International Conference on Software Engineering, 1998; 302--311.

No context found.

R. K. Keller and R. Schauer. Design Components: Towards Software Composition at the Design Level. Proceedings of pages 302--311, 1998.

No context found.

R. K. Keller and R. Schauer. Design Components: Towards Software Composition at the Design Level. Proceeding of the 20th IEEE International Conference on Software Engineering, pages 302--311, 1998.

No context found.

R. K. Keller and R. Schauer. Design Components: Towards Software Composition at the Design Level. Proceedings of the 20th ACM/IEEE ICSE, pages 302--311, 1998.

No context found.

Rudolf K. Keller and Reinhard Schauer. Design Components: Towards Software Composition at the Design Level. Proceedings of the 20th International Conference on Software Engineering, pages 302--311, 1998.

No context found.

R. K. Keller and R. Schauer. Design Components: Towards Software Composition at the Design Level. Proceedings of pages 302--311, 1998.

No context found.

R. K. Keller and R. Schauer. Design Components: Towards Software Composition at the Design Level. Proceedings of the 20th International Conferenceon Software Engineering, pages 302--311, 1998.

No context found.

Rudolf K. Keller and Reinhard Schauer. Design Components: Towards Software Composition at the Design Level. Proceedings of the 20th International Conference on Software Engineering, pages 302--311, 1998.

No context found.

R. Keller and R. Schauer. Design components: Towards software composition at the design level. In Proceedings of the 20th International Conference on Software Engineering, pages 302--311. IEEE Computer Society Press, Apr. 1998.

No context found.

R. Keller and R. Schauer. Design components: Towards software composition at the design level. In Proceedings of the 20th International Conference on Software Engineering, pages 302--311. IEEE Computer Society Press, Apr. 1998.

No context found.

R. Keller and R. Schauer, "Design Components: Towards Software Composition at the Design Level," ICSE 1998.

No context found.

R. Keller, R. Schauer, "Design Components: Towards Software Composition at the Design Level" In Proc. International Conference on Software Engineering (ICSE) 1998

No context found.

[Keller, et al, 1998] Keller, R., Schauer, R., Design Components: Towards Software Composition at the Design Level

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