Academia.eduAcademia.edu

Outline

Title
Abstract
Figures
Introduction
Simple Object Access Protocol (Soap)
Conclusion
References

The artifacts of component-based development

Profile image of M.Shaukat HayatM.Shaukat Hayat

2012, Arxiv preprint arXiv:1202.2425

Abstract

Component based development idea was floated in a conference name "Mass Produced Software Components" in 1968 [1]. Since then engineering and scientific libraries are developed to reuse the previously developed functions. This concept is now widely used in SW development as component based development (CBD). Component-based software engineering (CBSE) is used to develop/ assemble software from existing components [2]. Software developed using components is called component ware [3]. This paper presents different architectures of CBD such as ActiveX, common object request broker architecture (CORBA), remote method invocation (RMI) and simple object access protocol (SOAP). The overall objective of this paper is to support the practice of CBD by comparing its advantages and disadvantages. This paper also evaluates object oriented process model to adapt it for CBD.

Figures (2)
The object oriented process model is the only process model that indicates the reuse of existing SW parts [8].
The object oriented process model is the only process model that indicates the reuse of existing SW parts [8].

Related papers

An Improved Model for Component Based Software Development
Usman Mir Khan

Software development costs, time-to-market and quality product are the three most important factors affecting the software industry. Various tools and techniques are invented by researchers and practitioners to improve in delivering quality software systems with lower cost and shorter time to market. One such practice is development of software using Component Based Software Development (CBSD) techniques. CBSD recommended building software systems using existing reusable components, instead of writing from scratch. The main objective of CBSD is to writes once and reuse any number of time with no or minor modification. Some of the advantages that a company may avail by adapting CBSD for the Software development are shorter development time which results in meet tight dead line, Increase productivity and Quality Product. CBSD also, support reusability. The aim of this paper is to describe the characteristics of some selected state of art CBSD models that are widely practiced in softwa...

View PDFchevron_right
A Survey on Component-Based Software Development System
Gaurav Sethi

The primary goal of component-based software engineering is to address the development of systems as an erection of system components, and development component as the reusable entities and maintenance or upgrading of system. Component-based software development (CBSD) is an transpire rule that promises to take software engineering into a new epoch. The CBSD methodologies dealing with COTS components. Component based software development is integrated with a shift from statement-oriented coding to building a system by plugging together with components. The established disciplines from software engineering needs a new methodologies to support the component-based development. This requires traditional methodologies and tools to support the entire component and system's life cycle including organisational, marketing, technological and other aspects. The paper define relevant terms by relating the definitions to the already well-defined terms of object technology. The paper describe new vital activities in the component-based systems life cycle, and also discusses the technical and non-technical issues that need to be resolved for widespread assumption of this approach. This paper also presents several directions for future research and work in this area.

View PDFchevron_right
Component Based Software Design using CORBA
Mark Hermeling

2008

Component based software design depends heavily on communication between components. In the past engineers have tried to minimize communication delays by combining components into monolithic systems or by using custom coded transportation mechanisms. This has resulted into inflexible , fragile systems that are hard to design and test. This paper demonstrates through performance measurements that a high-performance ORB like OIS's ORBexpress makes flexible, re-usable component based software designs a reality. like CORBA. Embedded CORBA ORBs like OIS's ORBexpress are highly optimized. The level of performance they provide makes the need for monolithic designs a thing of the past. This paper will explore proper component based design in the context of the SCA and will cover how ORBexpress provides the required communication performance. Even though this paper is mainly focussed on the SCA the arguments are equally applicable to other component based standards such as the OMG De...

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
Emergence of Component Based Software Engineering
Dr. Ardhendu Mandal

It was noticed that, most software systems are not new but are variants of systems that had been already developed. Hence, a new systems may be developed partially if not completely, from the pre-existing systems by reusing it. This brings the idea of reusability and gave the birth of a noble concept of Component Based Software Development, beyond object oriented development paradigm. Component Based Software Development aims to construct complex software systems by means of integrating reusable software components. This approach promises to alleviate the software crisis at great extents. The objective of this paper is to gain attention towards this new component based software development paradigm and to highlight the benefits and impact of the approach for making it a successful software development approach to the concerned community and industry.

View PDFchevron_right
MaRMI-III: A Methodology for Component-Based Development
Dong-Han Ham

ETRI Journal, 2004

As component-based development (CBD) rapidly spread throughout the software industry, a comprehensive methodology is needed to apply it more systematically. For this purpose, a new CBD methodology named Magic & Robust Methodology Integrated III (MaRMI-III) has been developed. The purpose of this paper is to present MaRMI-III by its constituent processes and claim that it can be used to support system developers conduct CBD in a consistent manner. First, we review the CBD approach to system development and the role of CBD methodology, and then we explain the several characteristics of MaRMI-III which are considered necessary to the CBD environment. Next, we explain a process model of MaRMI-III which separates the development process from the project management process and prescribes wellordered activities and tasks that the developer should conduct. Each phase forming the Process Model is explained in terms of its objectives and main constituent activities. Some techniques and workproducts related to each phase are also explained. Finally, to examine the usefulness of MaRMI-III, an analytical comparison with other CBD methodologies and the results of a questionnaire survey are described.

View PDFchevron_right
A Component-Based Framework for Software Reusability
khalid khan

Component-based development allows us to develop and integrate product components which facilitate software reusability, high quality and simplification for testing. Component-Based Software Engineering makes use of approaches which are based on architecture definition languages, object oriented design and software architecture. These strategies assist in the development of both domain-specific and generic software products. Reusability approach speeds up software development by using already developed components, thus software development cost and time is substantially reduced. I this paper, we present a Component-Based Software Engineering framework for software reusability

View PDFchevron_right
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
Component Based Software Engineering New Chalanges in Software Development
Anfal Sheikh

The primary role of component-based software engineering is to address the development of systems as an assembly of parts (components), the development of parts as reusable entities, and the maintenance and upgrading of systems by customising and replacing such parts. This requires established methodologies and tool support covering the entire component and system lifecycle including technological, organisational, marketing, legal, and other aspects. The traditional disciplines from software engineering need new methodologies to support component-based development.

View PDFchevron_right
Component-Oriented Software Development
Dennis Tsichritzis

1992

Object-oriented programming techniques promote a new approach to software engineering in which reliable, open applications

View PDFchevron_right

References (25)

  1. Chaudron, M.R.V. (2005), Component-Based Software Engineering. http://www.win.tue.nl/~mchaudro/cbse2005/01_IntroC
  2. BD_Concepts.pdf, Visited May 22, 2007.
  3. Crnkovic, I., Larsoon, M. (2002). Building Reliable Component-Based Software Systems. London, Artech House.
  4. Pressman, R. S. (2005). Software Engineering. New York, McGraw Hill.
  5. Sebastian, T. (2004). The Many Dimensions of the Software Process. Crossroads ACM Press, Vol. 6(4), 22-26.
  6. Bruynooghe, R. F. Greenwood, R.M. Robertson, I. Sa, J. Snowdon, R. A., Warboys, B.C. (1994). PADM: Towards a Total Process Modelling System. Software Process Modelling and Technology, Research Studies Press, 293-334.
  7. Greenwood, M. Warboys, B.C., Sa, J. (1996). Cooperating evolving components: a rigorous approach to evolving large software systems. Proc. 18th Int. Conf. Software Engineering, Berlin, Germany, 428- 437.
  8. Schmietendorf, A. Dimitrov, E., Dumke, R. R. (2002). Process Models for the software development and performance engineering tasks, Proc. 3 rd Int. workshop on Software and performance, Rome, Italy, 211-218.
  9. Pressman, R. S. (2001). Software Engineering. New York, McGraw Hill.
  10. Jeffrey A. H. (1999). Modern System Analysis and Design. USA, Addison Wesley.
  11. Center for Technology in Government University at Albany/SUNY, (1998). A Survey of System Development Process Models. CTG.MFA-003.
  12. Brereton, O. P. (1999). The Future of Software: Defining the research agenda. Comm. ACM, 78-84.
  13. Dogru, A.H. and Tanik, M.M. (2003). A process model for component-oriented software engineering. IEEE Software, Vol. 20(2), 34-41.
  14. Deitel & Deitel. (1999). Visual Basic 6.0 How to program. USA, Prentice Hall.
  15. Roger, L. Haeng-Kon, K., Hae, S. Y. (2004). An architecture Model for dynamically converting components into web services. 11th Asia-Pacific Software Engineering Conference (APSEC'04), Busan, Korea, 648-654.
  16. Deitel & Deitel. (2001). E-Business & E-Commerce. USA, Prentice Hall.
  17. Microsoft Corp. (2007). COM Technologies, http://www.microsoft.com/com/default.mspx, Visited June 11, 2007.
  18. Rizwan J. (2006). Reuse and Component Based Development. Proc. Int. Conf. Software Engineering Research & Practice, Las Vegas, USA, 146-150.
  19. Deitel & Deitel. (2001). Java How to Program. USA, Prentice Hall.
  20. Luiz, F. C. Miriam, A.M.C., Dahai, L. (2001). Component-Based Software Process. Proc. 7th Int. Conf. Object-Oriented Information Systems, Calgary, Canada, 523-529.
  21. Jihyun, L. Jinsam, K. Gyu-Sang, S. (2003).Facilitating Reuse of Software Components using Repository Technology. Proc. 10 th Asia Pacific Conf. Software Engineering, Chiang Mai, Thailand, 136-142.
  22. Ning, J. Q. (1996). A Component-Based Software Development Model. Proc. 20th Conf. Computer Software and Applications, Seoul, Korea, 389-394.
  23. Richard, M. A. (1995). Emerging Standards for Component Software. Computer, Vol. 28(3), 68-77.
  24. Lim, W. C. (1994). Effects Of Reuse on Quality, Productivity and Economics. IEEE Software, Vol. 11(5), 23-30.
  25. Henry, E., Faller, B. (1995). Large Scale Industrial Reuse To Reduce Cost And Cycle Time. IEEE Software, Vol. 12(5), 47-53.

Related papers

A Technique for Component Based Software Development
IASET US

Navneet Kaur & Ashima Singh , 2013

The software development paradigm is moving from traditional software development , which is based on building software systems from scratch, to Component-Based Software Development (CBSD), which is based on using the reusable components as building blocks for software development. The focus of this new approach is on development of new systems by selecting and assembling a set of existing components within an appropriate software architecture. This approach provides various advantages like reduced effort ,time and cost during software development , improved software system maintainability and flexibility by allowing new components to replace old ones and enhanced system quality by allowing components to be developed by those who are specialized in the application area and systems to be built by software engineers who are specialized in component-based software development. Although CBSD has proven its usefulness in the field of software engineering but it still consists of a number of issues or factors that affect many aspec ts of CBSD like integration and testing effort and affect the produced software cost, maintainability,etc .In this paper some issues and the techniques to resolve those issues have been discussed . Thus a technique has been proposed for Component Based Software Development Organizations(CBSDO) to be used during the development of the software system by using CBSD approach.

View PDFchevron_right
Component Based Software Development – " An Efficient Approach "
IJSES Editor

—Elemental role of component based software engineering is to develop the systems of an assembly of parts, the development of parts in the form of reusable institutions, and maintenance and upgrading of systems by customizing and altering such parts. Component-based software Development (CBSD) is used to develop / collect Software from existing components. Component based software development follows some principles. Paper shows a study of various software reusable concepts. The aim is to gather useful information on software components and the component on which component reusability is highly dependent, as a result of the review of the software reusability that is very dependent on reusability, cost, optimization, and complexity of the interface, documentation quality and portability. In this paper, the main description is about component based software development where the components can be reused and combined together to form a software system that meets the user's actual requirements. This paper also shows different models of component based systems and the factors that affect component based development.

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
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
A Software Process Model for Component-Based Development
Luiz Fernando Capretz

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.

View PDFchevron_right
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved