Package-oriented software engineering: a generic architecture

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.

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

Object-Oriented Software Composition, 1995

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.

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.

Lecture Notes in Computer Science, 1995

All engineering disciplines rely on standard components to design and build artifacts. The key technical challenge in software engineering is to enable the adoption of such a model to the development of software. The transformation from line-by-line development to component-based development will address many of the industry's persistent productivity and quality problems. Indeed, component-based software development has been a long-standing dream of the software industry, prompting a search for both technical and nontechnical solutions. A successful approach to component-based development requires a comprehensive solution that draws on advances in programming languages, programming paradigms, algorithm analysis, and software design. This paper presents an approach based on the C++ Standard Template Library. More than a traditional library, STL embodies a concrete approach to software design based on a well-defined taxonomy and theory of software components. I present the fundamental contributions of STL to a paradigm of component programming-a component-based software development paradigm in which there is a clear separation between component development and application development. I motivate component programming, give the requirements for components and catalogs, and give an example of component programming applied to the standard Keyword in Context (KWIC) problem. I then summarize the implications of component programming for the software industry and for software engineering education.

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.

In this paper we present the results of the CICYT ComProLab project, ref. TIC97-1158, which addresses to some particular points concerning component-based software development. We focus on components as encapsulation of abstract data types. The project stresses three particular fields: statement of non-functional issues; process modeling; and efficiency concerns on abstract data type implementations.

2020

Although component-based software development have been subject to extensive research for many years, most software systems are still based on the objectoriented paradigm. We believe that one of the main causes is a lack of support for Component-Oriented Programming (COP). Indeed, a lot of work proposed component models such as Unified Modeling Language (UML), Enterprise JavaBeans (EJB) or Corba Component Model (CCM) that are only available at design time. At the implementation stage, object-oriented languages are mainly used which prevent developers to fully switch to COP. In this paper, we identify five requirements (decoupling, adaptability, unplanned connections, encapsulation and uniformity) for COP based on an analysis of the state of the art and limitations of existing work. We then propose an extended version of the Scl component language that fulfills these requirements.

Science of Computer Programming, 2014

h i g h l i g h t s • Introduces the Special Issue on CBSE and Software Architecture. • Presents the CompArch'12 event and its constituent conferences CBSE, QoSA, ISARCS. • Introduces the papers included in this Special Issue (best papers from CompArch'12).