Academia.eduAcademia.edu

Outline

Title
Abstract
Introduction
Design and Implementation
Related Work
Conclusion
References
All Topics
Computer Science
Software Engineering

ComponentXchange: An E-Exchange for Software Components

Profile image of Jose Paulo NunesJose Paulo Nunes

2002, Proc. IADIS Int. Conf. WWW/ …

Abstract

A key challenge in Component-Based Software Engineering (CBSE) is finding appropriate software components for reuse. A component broker that allows component vendors to make available their modules, and also allows component integrators to search and select ...

Related papers

Componentware–state of the art 2003
María Victoria Cengarle

Background paper for …

Components and component-based technologies (componentware) are well-known and widely used in software development. There is a large amount of work and research in componentware. The number of available componentware approaches increases ...

View PDFchevron_right
Volume II: Technical Concepts of Component-Based Software Engineering
Kurt Wallnau

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.

View PDFchevron_right
Workshop on Component-Based Software Engineering Processes
Kingsley Nwosu

2008

Component-based software engineering (CBSE) spans a range of technologies and engineering practices. Engineering practices for component-based systems (e.g., design, integrate, test, deploy and sustain) are emerging, but in isolated settings rather than at a community level. The goal of this workshop is to provide a baseline understanding of the broad aspects of CBSE processes.

View PDFchevron_right
An Improved Repository Structure to Identify, Select and Integrate Components in Component-based Development
Muhammad DAUDA

International Journal of Software Engineering & Applications

An ultimate goal of software development is to build high quality products. The customers of software industry always demand for high-quality products quickly and cost effectively. The component-based development (CBD) is the most suitable methodology for the software companies to meet the demands of target market. To opt CBD, the software development teams have to customize generic components that are available in the market and it is very difficult for the development teams to choose the suitable components from the millions of third party and commercial off the shelf (COTS) components. On the other hand, the development of in-house repository is tedious and time consuming. In this paper, we propose an easy and understandable repository structure to provide helpful information about stored components like how to identify, select, retrieve and integrate components. The proposed repository will also provide previous assessments of developers and end-users about the selected componen...

View PDFchevron_right
Component based software developmentResearch paper
Hamna khan

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.

View PDFchevron_right
Component Based Software Development
Hamna khan, Ahsen Ilyas

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).

View PDFchevron_right
New age of software development: How component-based software engineering changes the way of software development
Mikio Aoyama

… of 1st workshop on Component Based Software …, 1998

The dawn of a new age of software development is coming. Wide spread of the Internet technology and PCs opened up new market of software as well as new architecture of software. However, conventional software development technology could not catch up with the speed.

View PDFchevron_right
A case study: demands on component-based development
Ivica Crnkovic

2000

Building software systems with reusable components brings many advantages. The development becomes more efficient, the reliability of the products is enhanced, and the maintenance requirement is significantly reduced. Designing, developing and maintaining components for reuse is, however, a very complex process which places high requirements not only for the component functionality and flexibility, but also for the development organization. In this paper we discuss the different levels of component reuse, and certain aspects of component development, such as component generality and efficiency, compatibility problems, the demands on development environment, maintenance, etc. The evolution of requirements for products generates new requirements for components, if components are not enough general and mature. This dynamism determines the component life cycle where the component first reaches its stability and later degenerates in an asset that is difficult to use, difficult to adapt and maintain. When reaching this stage, the component becomes an obstacle for efficient reuse and should be replaced. Questions related to use of standard and de-facto standard components are addressed specifically. As an illustration of reuse issues, we present a successful implementation of a component-based system which is widely used for industrial process control.

View PDFchevron_right
Component-Based Software Development Environment (Cbde)
Marcilio de souza

Proceedings of the 4th International Workshop on Pattern Recognition in Information Systems, 2004

This paper presents an Component-Based Software Development Environment-CBDE that supports the construction and reuse of software components according to Catalysis. Its integrates a CASE tool, named to MVCase, and a RAD tool, named to C-CORE, to support the whole process of Component-Based Software Development (CBD). The CBD process, follows the spiral model of software development, including activities that start from communication with the customers to identify the requirements for construction and reuse of components, until the delivery and customers component assessment. This paper focuses on details related to the two phases of the CBD Construction process. The MVCase and C-CORE help the software engineer automating great part of the components construction and reuse tasks. The CBDE is a computer system that provides support for development, repair and improvements 338

View PDFchevron_right
Software Component Models from a Technical perspective
ABDUL AZIM

2007

Component-based Software Development is an approach that has many benefits, such as improving application developer productivity, reducing costs and complexity. Programming within this approach is like assembly rather than development, which reduce skill requirements, and allow expertise focus on domain problems. The foundation of any CBSD methodology is its underlying component model, which defines what components are, how they can be constructed, and specifies the standards and conventions that are needed to enable composition of independently developed component. This paper presents a survey of the current available component technologies with focus on the technical perspective of each component model in order to have better understanding for developing a new component model. We have categorized them based on Distributed Application Support and Interaction mechanism.

View PDFchevron_right

References (19)

  1. Aoyama, M., 1998. New Age of Software Development: How Component-Based Software Engineering Changes the Way of Software Development. Proceedings of International Workshop on Component-Based Software Engineering. Kyoto, Japan.
  2. Beugnard, A. et al, 1999. Making components contract aware. In IEEE Computer, 32(7), pp 38-45.
  3. Blair, D. and Maron, M. E., 1985. An Evaluation of Retrieval Effectiveness for a Full-Text Document-Retrieval System. In Communications of the ACM, 28(3), pp 289-299.
  4. Burton, B. et al, 1987. The Resuable Software Library. In IEEE Software, pp. 25-33.
  5. Ncube, C. and Neil A.M. Maiden, 1999. PORE: Procurement-Oriented Requirements Engineering Method for the Component-Based Systems Engineering Development Paradigm. Proceedings of International Workshop on Component-Based Software Engineering, Los Angeles, CA.
  6. Frakes W. B. and Nejmeh, B. A., 1990. An Information System for Software Reuse. In Software Reuse: Emerging Technology, IEEE Computer Society Press, pp. 142-151.
  7. Franch, X., 1998. Systematic Formulation of Non-Functional Characteristics of Software. Proceedings of 3rd IEEE International Conference on Requirements Engineering, Colorado Springs, CO.
  8. Frolund, Svend and Koistinen, Jari, 1998. QML: A language for quality of service specification. Technical Report HPL-98-10, Hewlett-Packard Laboratories.
  9. Maarek, Y. S. et al. An Information Retrieval Approach for Automatically Constructing Software Libraries. In IEEE Transactions on Software Engineering, 17(8). pp. 800-813.
  10. Mili, H. et al, 1995. Reusing Software: Issues and Research Directions. In IEEE Transactions On Software Engineering, 21(6), pp. 528-562.
  11. Mili, Hafedh et al, 1994. Practitioner and Softclass: A Comparative Study of Two Software Reuse Research Projects. In Journal of Systems and Software, vol 27.
  12. Object Management Group (OMG). CORBA Component Model. OMG TC Document orbos/99-02-05. http://www.omg.org/cgi-bin/doc?orbos/99-02-05.
  13. Object Management Group (OMG). CORBA Services: Common Object Services Specifications. http://www.omg.org/cgi-bin/doc?ptc/99-10-04
  14. Puder, A. et al, 1995. Service Trading Using Conceptual Structures. Proceedings of the Third International Conference on Conceptual Structures, Santa Cruz, California.
  15. Sahuguet, Arnaud, 2000. KWEELT, the Making-of: Mistakes Made and Lessons Learned. Technical Report, Department of Computer and Information Science, University of Pennsylvania.
  16. Seacord, Robert et al, 1998. Agora: A Search Engine for Software Components. Technical Report CMU/SEI-98-TR- 011, Software Engineering Institute, Carnegie Mellon University.
  17. V. Sriram, 2001. ComponentXchange: An E-Exchange for Software Components. M.Tech. Thesis, Department of Computer Science & Engineering, Indian Institute of Technology, Kanpur.
  18. Wallnau, K. C., 1999. On Software Components and Commercial ("COTS") Software. Proceedings of International Workshop on Component-Based Software Engineering. Los Angeles, CA.
  19. XML Schema Part 0: Primer. W3C Candidate Recommendation, World-Wide Web Consortium, October 2000. http://www.w3.org/TR/xmlschema-0/

Related papers

Component Based Software Engineering
Ralf Reussner

International Journal of Computer Applications, 2010

Traditional software estimation models are directed towards large monolithic software development projects. Contemporary software development practices require a new approach to software cost estimation. Contemporary development practices characterize a software application as interacting, independent components. Component-based development offers many potential benefits such as a greater reuse. Component based software development approach is based on the idea to develop software systems by selecting appropriate off-the shelf components and then to assemble them with a welldefined software architecture. Software community faces a major challenge that is raised by fast growing demand for rapid and cost-effective development and maintenance of large scale and complex software systems. To overcome the challenge, the new trend is to adopt component based software engineering (CBSE).The key difference between CBSE and traditional software engineering is that CBSE views a software system as a set of off-the-shelf components integrated within appropriate software architecture. CBSE promotes large-scale reuse, as it focuses on building software on building software systems by assembling off-the-shelf components rather than implementing the entire system from scratch. CBSE also emphasis on selection and creation of software architecture that allow systems to achieve their quality requirements .As a result, CBSE has introduced fundamental changes in software development and maintenance.

View PDFchevron_right
A Component-Based Software Engineering Environment
Eduardo de Almeida

The Journal of Object Technology, 2004

Software Engineering Environments (SEEs) have been extensively studied, aiming to provide help in software development. Component-Based Software Engineering (CBSE) arises as an approach for constructing software through reusable components, reducing development costs and time, among other benefits. This paper identifies the main requirements for Component-Based Software Engineering Environments (CBSEEs), and presents Orion, a CBSEE which integrates different works from our research group, involving development tools, a repository, a process model and a middleware platform.

View PDFchevron_right
Component Software and the Way Ahead
Clemens Szyperski

2000

Components capture the deployment nature of software; objects capture its runtime nature. Components and objects together enable the construction of nextgeneration software. However, as discussed in this chapter, many problems still need to be solved before component software can become ubiquitous. One important step to be taken is to move from component introversion to component extroversion and to adopt component-based software architecture on a much broader basis. To avoid the many traps on that way, it is useful to emphasize: Components are units of deployment and versioning but the atoms of configuration. To control the complexity explosion of peer-to-peer component architectures, component frameworks need to be pursued beyond their current weak foundation.

View PDFchevron_right
Component Selection for Component Based Software Engineering
Dr. Arvinder Kaur

International Journal of Computer Applications, 2010

Component selection is not an easy task in Component Based Software Engineering .and it is very difficult to select component for CBSE. Component Based Software Engineering (CBSE) is a concerned with the assembly of pre-existing software components that leads to a software system that responds to client-specific requirements. This paper presents an approach for defining evaluation criteria for reusable software components. We introduce taxonomy of factors that influence selection, describe each of them, and present a hierarchical decomposition method for deriving reuse goals from factors and formulating the goals into an evaluation criteria hierarchy. It also presents a summary of the common problems in reusable off-the-shelf software selection, describes the method .It also indicates that the evaluated aspects of the method are feasible, improve the quality and efficiency of reusable software selection. In this paper the selection of component is done on the basis of the cost of the component which is calculated on the basis of the quality attributes of the component. The approach used for selecting the component is a part of OTSO method that has been developed for reusable component selection process.

View PDFchevron_right
Volume I: Market Assessment of Component-Based Software Engineering
Kurt Wallnau

2001

View PDFchevron_right

Related topics

  • Computer Science
  • Software Engineering
  • Component Based Software Enginee...
  • Specification Language
    • 580 California St., Suite 400
    San Francisco, CA, 94104
    © 2025 Academia. All rights reserved