Conference
Component-Based Software Engineering
About: Component-Based Software Engineering is an academic conference. The conference publishes majorly in the area(s): Component (UML) & Component-based software engineering. Over the lifetime, 411 publications have been published by the conference receiving 8792 citations.
Topics: Component (UML), Component-based software engineering, Software development, Software system, Software architecture
Papers published on a yearly basis
Papers
Proceedings Article•
7 Jun 2001
TL;DR: In this paper, the authors present a model of software architecture that consists of three components: elements, form, and rationale, and discuss the components of the model in the context of both architectures and architectural styles.
Abstract: The purpose of this paper is to build the foundation for software architecture. We rst develop an intuition for software architecture by appealing to several well-established architectural disciplines. On the basis of this intuition, we present a model of software architecture that consists of three components: elements, form, and rationale. Elements are either processing, data, or connecting elements. Form is de ned in terms of the properties of, and the relationships among, the elements | that is, the constraints on the elements. The rationale provides the underlying basis for the architecture in terms of the system constraints, which most often derive from the system requirements. We discuss the components of the model in the context of both architectures and architectural styles and present an extended example to illustrate some important architecture and style considerations. We conclude by presenting some of the bene ts of our approach to software architecture, summarizing our contributions, and relating our approach to other current work.
516 citations
24 May 2004
TL;DR: Fractal as mentioned in this paper is a hierarchical and reflective component model with sharing that allows fine-grained manipulation of the internal structure of components, from black-boxes to components with arbitrary reflective capabilities.
Abstract: This paper presents Fractal, a hierarchical and reflective component model with sharing. Components in this model can be endowed with arbitrary reflective capabilities, from black-boxes to components that allow a fine-grained manipulation of their internal structure. The paper describes Julia, a Java implementation of the model, a small but efficient run-time framework, which relies on a combination of interceptors and mixins for the programming of reflective features of components. The paper presents a qualitative and quantitative evaluation of this implementation, showing that component-based programming in Fractal can be made very efficient.
321 citations
9 Sep 2001
TL;DR: This work proposes a standard problem to evaluate product-line methodologies using the GenVoca design methodology, and explains a series of modeling, implementation, and benchmarking issues that it encountered, so that others can understand and compare the solution with theirs.
Abstract: We propose a standard problem to evaluate product-line methodologies. It relies on common knowledge from Computer Science, so that domain-knowledge can be easily acquired, and it is complex enough to expose the fundamental concepts of product-line methodologies. As a reference point, we present a solution to this problem using the GenVoca design methodology. We explain a series of modeling, implementation, and benchmarking issues that we encountered, so that others can understand and compare our solution with theirs.
202 citations
Proceedings Article•
1 Jan 1999
TL;DR: This paper proposes a new method, PORE, to address the lack of requirements engineering methods and product evaluation/selection process guidance for the CBSE process and ends with a ‘vision’ for future research directions for component-based systems engineering development process.
Abstract: Most current research in Component-Based Systems Engineering (CBSE) focuses on design and integration processes. There is little interest in the requirements engineering and product evaluation/selection processes that must precede design and integration. Also most current methods and tools support systems design and integration but neglect the requirements engineering and product evaluation/selection processes. However, in spite of this lack of focus on requirements engineering, a consensus seems to be emerging that the CBSE development process should be an iterative one of requirements engineering, systems design, product evaluation/selection and systems integration. This paper proposes a new method, PORE, to address the lack of requirements engineering methods and product evaluation/selection process guidance for the CBSE process. The paper ends with a ‘vision’ for future research directions for component-based systems engineering development process.
153 citations
9 Jul 2007
TL;DR: A novel approach to the analysis of the reliability of a component-based system that takes into account an important architectural attribute, namely the error propagation probability, which is the probability that an error, arising somewhere in the system, propagates to other components, possibly up to the system output.
Abstract: We present a novel approach to the analysis of the reliability of a component-based system that takes into account an important architectural attribute, namely the error propagation probability. This is the probability that an error, arising somewhere in the system, propagates to other components, possibly up to the system output. As we show in the paper, this attribute may heavily affect decisions on crucial architectural choices. Nonetheless, it is often neglected in modeling the reliability of component-based systems. Our modeling approach provides a useful support to the reliability engineering of component-based systems, since it can be used to drive several significant tasks, such as: (i) placing error detection and recovery mechanisms, (ii) focusing the design, implementation and selection efforts on critical components, (iii) devising cost-effective testing strategies. We illustrate the approach on an ATM example system.
134 citations
Performance Metrics
| Year | Papers |
|---|---|
| 2019 | 1 |
| 2016 | 18 |
| 2015 | 14 |
| 2014 | 27 |
| 2013 | 21 |
| 2012 | 26 |