Towards Composing Software Components in Both Design and Deployment Phases (original) (raw)

CASCON'98 Workshop Report: Component-Based Software Composition

Has component-based software composition reached a level of maturity where building software from components with minimal programming is feasible? Even if component-based software composition is feasible, is it practical? Building software with components is an approach to increasing productivity, whether these components are available commercially or within an organization. This workshop will focus on both research and current practice. 1. Background Component-based software composition has been discussed for about 30 years, but only recently has a level of maturity been reached where building software from components with minimal programming is feasible. There are now a number of competing and maturing visions of software composition [1,2,3,4]. For example, CORBA, the World Wide Web and ActiveX all offer views of how software components should be integrated and defined. The reasons behind component-based software composition include [5,6]: q The capability of (sutomated) assembly of software components, bringing greater quality and reliability, reduced time to develop and test new systems, and cost amortization from multiple use of software components, which could lead to increased productivity in software development q Increased productivity for software users through improvements in quality of components and dependability of systems q Development of appropriate technologies and processes to overcome barriers to widespread use and reuse of software components

Composition Environments for Deployable Software Components

2002

Component-based software development is revolutionizing the software industry by promoting a view of software development in which applications are composed out of reusable, relatively large-grained, and mostly pre-existing components. Adoption of component-based software development leads to an important distinction in roles between those that develop and make available individual components and those that compose applications out of available components. As a result, application composition is no longer a matter of writing and combining source code, but instead of composing deployable components-components that are pre-packaged, independently distributed, easily installed and uninstalled, and self-descriptive.

An Approach for Component-Based Software Composition

2008 Electronics, Robotics and Automotive Mechanics Conference, 2008

Presently, not only a large amount of information resources are available on the Web, but also a complete lattice of dynamic applications, namely, software components and Web Services. Hence, an increasing demand of a proper model and architecture for composition of software components has triggered a huge amount of integration efforts. However, most of them are partially ignoring operational and knowledge-oriented aspects which can hinge on semantics. In this paper, we present a semantically enhanced framework for software composition focusing on component-based systems.

Report of the International Symposium on Component-Based Software Engineering

ACM SIGSOFT Software Engineering Notes, 2005

The International Symposium on was held at 28 th International Conference on Software Engineering in Edinburgh, Scotland, May 24-25, 2004. The Symposium brought together researchers and practitioners from several communities: component technology, composition languages, compositional analysis, software architecture, software certification and scientific computing. The primary goal of the symposium was to continue clarifying the concepts, identifying the main challenges and findings of predictable assembly of software components. This report gives a comprehensive summary of the position papers, of the symposium, its findings, and its results.

Component-Based Design: Towards Guided Composition

2003

In this paper, we present a mathematical model for the composition of software components, at a semantic modelling level. We describe a mathematical concept of a single software component and identify properties that ensure its potential behaviour can be captured. Based on that, we give a formal definition of composition and examine its effect on the individual components. We argue that properties of the individual components can, under certain conditions, be preserved in the composite. The proposed model can be used for guiding the composition of components as it advocates formal reasoning about the composite before the actual composition takes place.

Toward a unified terminology for component-based development

2000

Component-oriented programming (COP) and component-based development (CBD) have become rather mature software development approaches in the last years, with both quite good conceptual and technological support. In spite of this rapid growth, the concepts used when talking about components are not always well-defined and can lead to misconception, misunderstanding and confusion. Although the general, abstract definition of a component, as defined at WCOP'96 [1]

Component Based Software Development

Khan,H.,&Hassina. S.,&Ilyas.Ahsen.(2020)-Component Based Software Development.Academia.edu, 2020

Software industries are affected most by quality of product, development cost and time-to-market. Many new models are introduced to deliver a quality product within given time. CBSD is one of them which has gain so much popularity because of its characteristics like least coding is involved, components written in different languages can be integrated with interfaces to acquire required product, testing and maintenance also becomes so easy. CBSD suggested assembling software frameworks utilizing existing reusable segments, rather than composing without any preparation. The primary target of component-based software development is to composes as soon as and recycle any quantity of period with not any or slight change. In this paper we have discussed CBSD, how it is useful, how components are integrated its life cycle, extended models and also the risks and challenges. Keywords-Component-based software development (CBSD), Component-based software Engineering (CBSE), COTS (commercial off-the-shelf), quality-of-service (QOS).

A Software Process Model for Component-Based Development

In the present study software life cycle and reusability issues that arise during component-based software development are discussed. The first part concentrates on mechanisms to achieve software reusability, such as composition and inheritance, it also outlines the main reasons why software is not extensively reused and examines the difficulties associated with software reusability. In the second part, the main issues concerning a seamless software life cycle model are considered, its purpose was to present a software life cycle model that takes component-based software development into account. Finally, the article covers other general aspects that form a more complete assessment of the whole software process; for instance, the most frequently used abstraction mechanisms and an estimate of the time and effort spent on each phase of the described life cycle model.

Elicit A New Component based Software Development Model

International Journal of Computer Applications, 2013

This is an era of embryonic software development where there is loads of pressure not only on developers but also on software development organizations in order to stumble on unswerving, fast and lucrative methods in software production. Therefore, to fulfill the need, Component-Based Development (CBD) has been broadly used in software development as it enhances reusability, flexibility, and reduces the cost as well as time. In this paper, we are proposing a life cycle model commonly encountered in component based development methodologies. This model is divided into five stages or phases. Each phase describes its sub segments and activities necessary to develop Component Based software in a short span of time, effectively and efficiently. This model emphasizes not only on the development architecture but also focuses on validation of the integration of components, to accommodate client needs and requirements. The proposed model can be used for developing a process for producing Component-Based systems.

Volume II: Technical Concepts of Component-Based Software Engineering

2003

The Software Engineering Institute (SEI) is undertaking a feasibility study of "componentbased software engineering" (CBSE). The objective of this study is to determine whether CBSE has the potential to advance the state of software engineering practice and, if so, whether the SEI can contribute to this advancement. This report is the second part of a threepart report on the study. Volume I contains a market assessment for CBSE. Volume III outlines a proposed course of action for the SEI. Volume II, this report, establishes the technical foundation for SEI work in CBSE. The paper asserts that the key technical challenge facing CBSE is to ensure that the properties of a system of components can be predicted from the properties of the components themselves. The key technical concepts of CBSE that are needed to support this vision are described : component, interface, contract, component model, component framework, composition, and certification.