| 1. |
- Alvaro, Alexandre, et al.
(författare)
-
Software Component Evaluation: A Theoretical Study on Component Selection and Certification
- 2007
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- Software components need to be evaluated at several points during their life cycle, by different actors and for different purposes. Besides the quality assurance performed by component developers, there are two main activities which include evaluation of components: component selection (i.e. evaluation performed by the system developer in order to select the best fit component to use in a system) and an envisioned component certification (i.e. evaluation made by an independent actor in order to increase the trust in the component). This paper examines the fundamental similarities and differences between these two types of component evaluations and elaborates how these fit in the overall process views of component-based development for both COTS-based development and software product line development.
|
|
| 2. |
|
|
| 3. |
- Bures, Tomas, et al.
(författare)
-
Progress Component Model Reference Manual - version 0.5
- 2008
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- This report describes the component model developed within PROGRESS. In addition to defining the syntax and semantics, it also gives some background and motivation, and describes how this work relates to the overall PROGRESS vision and to the work in other areas of the project.
|
|
| 4. |
- Chaudron, Michel, et al.
(författare)
-
Component-based Software Engineering
- 2008
-
Ingår i: Software Engineering, Principle and Practice. - : Wiley-Blackwell. ; , s. 605-628
-
Bokkapitel (övrigt vetenskapligt/konstnärligt)
|
|
| 5. |
- Crnkovic, Ivica
(författare)
-
Component-based Software Engineering for Embedded Systems
- 2005
-
Ingår i: From MDD Concepts to Experiments and Illustrations. - New York, New York, USA : John Wiley & Sons. - 1905209592 ; , s. 712-713
-
Bokkapitel (övrigt vetenskapligt/konstnärligt)abstract
- Component-based development (CBD) is established as a standard approach in many domains. The most attractive parts of CBD come from its business side: increasing reuse and development efficiency. On other side many technical aspects are still remaining as challenges. This is in particular true in domains of embedded and dependable systems. The seminar will give the basic characteristics of component-based software development, then challenges and current practice and research directions.
|
|
| 6. |
- Crnkovic, Ivica, et al.
(författare)
-
Guest Editorial
- 2007
-
Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 80:5, s. 641-642
-
Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)
|
|
| 7. |
- Feljan, Juraj, et al.
(författare)
-
Classification and survey of component models
- 2009
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- As component-based software engineering is growing and its usage expanding, more and more component models are developed. In this report we present a survey of software component models in which models are described and classified respecting the classification framework for component models proposed by CrnkoviA‡ et. al. [1]. This framework specifies several groups of important principles and characteristics of component models: lifecycle, constructs, specification and management of extra-functional properties, and application domain. This report analyzes a considerable amount of component models, including widely used industrial models, as well as research models.
|
|
| 8. |
|
|
| 9. |
|
|
| 10. |
- Land, Rikard, et al.
(författare)
-
A Quantitative Survey on Software In-house Integration
- 2006
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- As organizations merge or collaborate closely, an important question is how their existing software assets should be handled. If these previously separate organizations are in the same business domain - they might even have been competitors - it is likely that they have developed similar software systems. To rationalize, these existing software assets should be integrated, in the sense that similar features should be implemented only once.We have previously made qualitative observations on this topic. This report describes the follow-up study, which was performed in the form of a questionnaire aimed at validating and quantifying the previous observations. This report describes the research design, present the questionnaire together with all responses, and make some statistical analyses. This will form a basis for further publications with deeper analyses.
|
|
