Kruchten, P., "Modeling Component Systems with the Unified Modeling Language", Int. Workshop on Component-Based Software Eng., 1998. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
The Context-Based Constraint Language Ccl For Components - Bubl (2002) (1 citation) (Correct)
....software systems just at the time that components were starting to move into the mainstream. It supports components as implementation concepts but provides no explicit support for other aspects of their specification. Hence, a number of methods and techniques for modelling component based systems [15, 16, 22, 23, 33, 52, 57, 63] have been proposed. Many modelling or specification techniques exist for modelling component UML Components based systems. The new constraint language CCL proposed here can be applied to all of them. This paper concentrates on how to apply it to the UML components approach introduced in ....
Philippe Kruchten. Modeling component systems with the unified modeling language. In International Workshop on Component-Based Software Engineering. Carnegie Mellon University, 1998.
The Context-Based Constraint Language CCL for Components - Bübl (2002) (Correct)
....software systems just at the time that components were starting to move into the mainstream. It supports components as implementation concepts but provides no explicit support for other aspects of their specification. Hence, a number of methods and techniques for modelling component based systems [6, 7, 10, 11, 17, 28, 31, 36] have been proposed. Many modelling or specification techniques exist for modelling component UML Components based systems. The new constraint language proposed here can be applied to all of them. This paper concentrates on how to apply it to the UML components approach introduced in [7] ....
Philippe Kruchten. Modeling component systems with the unified modeling language. In International Workshop on Component-Based Software Engineering. Carnegie Mellon University, 1998.
On the Definition of Concepts in Component Based Software .. - Kiziltan, Jonsson, Hnich (Correct)
....that is they will not be changed in the same way as objects will be. The conclusion is that an object is not a component. 3 Interfaces Interfaces define the access points to components. To be precise, an interface is a collection of operations that are used to specify a service of a component [16]. In an interface, each operation s semantic is specified. This specification serves both to providers implementing the interface and to clients using the interface. The interface of a component is important for the composition and customisation of components by users, allowing to find suitable ....
Kruchten P. Modeling Component Systems with the Unified Modeling Language. In Proc. of International Workshop on Component Based Engineering, 1998.
A Model for Classifying Component Interfaces - Yacoub, Ammar, Mili (Correct)
....information is passed between two communicating components. The use of components exacerbates interface centered software architecture because components offer interfaces to the outside world, by which it may be composed with other components [3] Several work in component interfaces [for example 8,9, and 7] focused mainly on issues related to interaction between individual components. Component interfaces were classified as functional and extrafunctional [7] defined for UML models [8] and for object oriented designs [9] We further abstract component interfaces to incorporate ....
....which it may be composed with other components [3] Several work in component interfaces [for example 8,9, and 7] focused mainly on issues related to interaction between individual components. Component interfaces were classified as functional and extrafunctional [7] defined for UML models [8] and for object oriented designs [9] We further abstract component interfaces to incorporate interfaces to platforms and elaborate on the importance of such classification. In this short paper, we present a model for a component s interactions which mainly classifies interfaces as Application ....
Kruchten, P. "Modeling Component Systems with the Unified Modeling Language", First Int'l Workshop on Component-Based Software Engineering, in conjunction with ICSE'98, Kyoto, 1998
COTS-Aware Requirements Engineering and Software Architecting - Lawrence Chung The (2004) (Correct)
No context found.
Kruchten, P., "Modeling Component Systems with the Unified Modeling Language", Int. Workshop on Component-Based Software Eng., 1998.
Foundations of a Module Concept for Distributed Object Systems - Filipe (2000) (1 citation) (Correct)
No context found.
P. Kruchten. Modeling Component Systems with the Unified Modeling Language. In A.W. Brown and K.C. Wallnau, editors, Electronic Proc. of the First International Workshop on Component-based Software Engineering, April 25-26, 1998, Kyoto, Japan, 1998.
Matching, Ranking, and Selecting Components: - Cots-Aware Requirements.. (Correct)
No context found.
Kruchten, P., "Modeling Component Systems with the Unified Modeling Language", Int. Workshop on Component-Based Software Eng., 1998.
Defining Agents in a COTS-Aware Requirements Engineering Approach - Chung, Cooper (2002) (Correct)
No context found.
Kruchten, P., "Modeling Component Systems with the Unified Modeling Language", Int. Workshop on Component-Based Software Eng., 1998, http://www.sei.cmu.edu/cbs/icse98/papers/p1.html .
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