Reference Library Component-Based Development
	This page provides access to a variety of downloadable papers that address component-based development issues. The following topics are considered: Component-Based Design (CBD) Methods Classification General Reuse Component-Based Design (CBD) Methods Built - In Testing for Component - Based Development [PDF] Component+ Partners This paper contains the three deliverables for work package 3 of the Component+Project. These include: implementation technologies of BIT components, reuse technologies of BIT components, and development of a set of sample BIT components. CBD Survey: The State of the Practice [HTML] Paul Allen This article discusses a Cutter Consortium survey on component-based developed from 118 companies from around the world. Two issues are looked at: State of the Practice, and Project Coverage. Component - Based Development with UML [PPT] Ivar Jacobson This PowerPoint presentation on component-based development outlines the following topics: what is the UML, where can UML be used, evolution of UML, vocabulary of UML, structural and behavioral things in UML, grouping things, relationships, diagrams, objectory development process, software development process, workflows, use case model, design model, deployment model, implementation model, test model, and an integrated business-modeling technique. Frameworks and Component - Based Development [PDF] Alan Wills Classes are not the best focus for object-oriented design. The most useful components in a design are frameworks - schemes of interaction between objects. These can be worked on by separate authors, kept in libraries, and recombined to make many different end-products. This paper explores the more formal aspects of this approach, within the context of popular OOA/D notations and programming languages. Incremental and Component - Based Software Development (INCO) [PDF] Dag Sjøberg and Reidar Conradi Incremental and component-based software development has been proposed to solve the high costs and high failure rates of software projects. Contents include: summary of incremental and component-based software development (INCO), goals, results, resources, state-of-the-art, rationale and approach, workplan, partner description, and associated activities and projects. Perspectives on Component-Based Development for Command and Control Systems [DOC] Randall W. Lichota This paper focuses on one application domain for which component development is already underway: command and control. A brief description of this effort is provided in the context of the Portable Reusable Integrated Software Modules (PRISM) program and its successor, the Command and Control Product Lines (CCPL) program. CCPL is spearheading the development of reusable domain-specific software components through the use of domain modeling, a common operating environment, and generic component- based architectures. However, this will only happen if commercial middleware, frameworks, and development environments are sufficiently flexible to meet the requirements of modern command and control systems. This paper highlights lessons learned from work undertaken by PRISM and CCPL and presents some perspectives on current industry directions. Strategies for Successful Component - Based Development [PDF] John Ohlinger This slide presentation contains the following topics: background on a new approach, challenges we faced, discovered strategies, lessons learned, and on-going work. The Future of Component - Based Development is Generation, not Retrieval [PDF] Hans de Bruin and Hans van Vliet Component-Based Development (CBD) has not redeemed its promises of reuse and flexibility. Reuse is inhibited due to problems such as component retrieval, architectural mismatch, and application specificness. Component-based systems are flexible in the sense that components can be replaced and fine-tuned, but only under the assumption that the software architecture remains stable during the system's lifetime. In this paper, the authors argue that systems composed of components should be generated from functional and nonfunctional requirements rather than being composed out of existing or newly developed components. They propose a generation technique that is based on two pillars: Feature-Solution (FS) graphs and top-down component composition. A FS-graph captures architectural knowledge in which requirements are connected to solution fragments. This knowledge is used to compose component-based systems. The State of the Practice [PDF] *FEE* Paul Allen This issue of Component Development Strategies (CDS) discusses the business-IT landscape. This issue contains the following contents: the state of the practice, a brief historical picture, component concepts, enabling technologies, and component-based strategies. Towards Practical Support for Component - Based Software Development using Formal Specification Position Statement [PDF] Heinrich Hussmann Starting from an analysis of the situation of a software developer using pre-fabricated components, it is investigated in which form techniques and formalisms from the area of formal specification can provide practical aid in development. Several different dimensions of precise component specification are identified. While formal specifications can be helpful for several of these dimensions, it is argued that the most relevant application area may be a flexible mechanism for creating different but consistent views on a complex system. Ideas for concrete tool support based on the Object Constraint Language (OCL) are sketched. Wren - An Environment for Component - Based Development [PDF] Chris Lüer and David S. Rosenblum This paper discusses component-based development environments (CBDEs). A prototype environment is described that implements the requirements for CBDEs to be used to study the role of environment technology in component-based development. Back to the top Classification A Classification of Software Components Incompatibilities for COTS Integration [PDF] Daniil Yakimovich, Guilherme H. Travassos and Victor R. Basili Integration of software components into a system can be hindered by incompatibilities between the components and system. To predict the possible incompatibilities and the ways to overcome them during the integration activities, a classification of incompatibilities can be useful for software developers. This can be especially crucial for COTS-based software development, where a software system is being built out of potentially highly heterogeneous software components. In this paper the authors present a classification of incompatibilities based on the properties of local component interactions. They believe that this classification can capture possible problems about software component integration in heterogeneous software systems, including architectural and functional issues. CLARiFi An Architecture for Component Classification and Brokerage [PDF] Stuart Thomason, Pearl Brereton and Stephen Linkman The European Commission funded CLARiFi project (CLear And Reliable Information For Integration) brings together academic and industrial expertise in the area of component-based software engineering. Its aim is to develop and prototype the techniques needed to produce a commercially viable component broker, based on sound research concepts. This position paper presents an overview of the project, its technical objectives, perceived benefits and lessons learned so far. CQM: A Software Component Metric Classification Model [PDF] Joaquina Martín-Albo, Manuel F. Bertoa, Coral Calero, Antonio Vallecillo, Alejandra Cechich and Mario Piattini Multiple authors have proposed metrics to quantify several components characteristics in order to help in its selection. Nevertheless, rather than helping developers, such proposals often provoke more confusion due to the fact that they do not systematically take into account different aspects of the components. Trying to achieve clarity in this line, the authors have developed the CQM model (Component Quality Model), whose first aim is to propose a classification of the defined metrics for software components. The model will also be able to be used for the evaluation of a component or a component system. Finally, it is necessary to indicate that this is the first version of the model, and it will need to be refined by means of its use and discussion in different forums. Facet - Based Classification Scheme for Industrial Automation Software Components [PDF] Vicente Ferreira de Lucena Jr. One of the most important problems at component based software development is how to manage the already developed components. Some approaches reduce this task to storing components in a repository. As the developer of components is not necessarily the user of components, we need to offer a way to guarantee the right communication among these two professionals. We need to support component developers and component users (system developers) to utilize the same vocabulary and documentation in order to improve the communication between them and, consequently, improve the reusability of developed components. In this paper the authors describe their software development process based on components. This paper contains a meta-model specially designed for the industrial automation domain, presents the authors selection process, and summarizes their work presenting their conclusion and ideas for the future. Towards a Classification Model for CBSE Research [PDF] Gerald Kotonya, Ian Sommerville and Stephan Hall This slide presentation covers the following topics: background, aims of CBSEnet, objectives of classification model, structure of model, elements of model, and model in operation. Back to the top General A Process for Gaining Competence in Component - Based Development [PDF] J. Scott Hawker and Richard Woolridge Castek is an industry leader in providing business-critical enterprise software solutions using a component based development approach. CBD/e is Castek's process for quickly building a software development organization's ability to develop and deliver component-based software. CBD/e defines an overall engagement process for Castek to work with a company in building their component-based development (CBD) ability. This engagement process includes specific software analysis and design methods for component-based development. After describing the CBD/e engagement process to provide context, this paper focuses on the CBD/e component analysis and design methodologies of that process. The paper concludes with an assessment of why CBD/e works so well. Challenges of Component - Based Development [PDF] Ivica Crnkovic and Magnus Larsson System evolution, maintenance, migration and compatibilities are some of the challenges met with when developing a component-based software system. In this paper the authors discuss the issues and challenges encountered when developing and using an evolving component-based software system. An industrial control system has been used as a case study. Component Based Development [PDF] Leo Hermans This slide presentation on component-based development covers the following topics: what are the components, components and services, separation of the what from the now, example of an initial application/component architecture, system context model, type specification model, need to refine the type specification, assessment action decomposition, model frameworks, patterns for expressing rules, and application of assessment pattern. Component Based Development [PDF] M. Huizing In this article the author discusses component-based development, specifically, what the components are, what can be expected from it, what is needed to apply components, and problems arising from applying components. Component - Based Development in a World of "e-", "i" and "x" [PDF] Michael Sparling This slide presentation on component-based development outlines the following topics: a brief history of applications, generations of the internet "i's" and "e's" , nomads and pervasive computing, miniaturization and form factors, make the customer the focus, what is a component, software components, component characteristics, in short a component is… , and what can components do for us. Component - Based Development Infrastructure: A Systematic Approach [PDF] Leonid A. Kalinichenko It is widely recognized now that OMG needs serious reconsideration of the middleware architecture to be used as a basis for component ware. Current OMA release was very good for the beginning, for the core interoperation modeling. Deficiencies of the current strategy for making systems with reuse are well known. To show that situation with the proper understanding of the essence of the component-based development is not hopeless, the author briefly refers to some results of just one research project devoted to the interoperable component-based information systems development. Component - Based Software Engineering - New Challenges in Software Development [PDF] Ivica Crnkovic 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 customizing and replacing such parts. This requires established methodologies and tool support covering the entire component and system lifecycle including technological, organizational, marketing, legal, and other aspects. The traditional disciplines from software engineering need new methodologies to support component-based development. Developing with Java Components Maximizing Productivity in Java Application Development [PDF] Sitraka This paper discusses Java components in the following contents: overview of Java and Java components, drivers for component-based development, evaluating Java component vendors, and Sitraka JClass Components. Dimensions of Component - Based Development [PDF] Colin Atkinson, Thomas Kühne and Christian Bunse As the properties of components have gradually become clearer, attention has started to turn to the architectural issues which govern their interaction and composition. In this paper the authors identify some of the major architectural questions affecting component-based software development and describe the predominant architectural dimensions. Of these, the most interesting is the "architecture hierarchy" which they believe is needed to address the "interface vicissitude" problem that arises whenever interaction refinement is explicitly documented within a component-based system. The authors present a solution to this problem based on the concept of stratified architectures and object metamorphosis Finally, they describe how these concepts may assist in increasing the tailorability of component-based frameworks. Task 1.4 - Guidelines for Component - Based Development Software Development Process for Real - Time Embedded Software Systems (DESS) [PDF] Information Technology for European Advancement The purpose of this document is to describe a number of guidelines for component identification, component-based development (CBD), component composition and component decomposition. These guidelines are aimed at a component-based development process for real-time embedded software systems. Toward a Unified Terminology for Component - Based Development [PDF] Stefan Van Baelen, David Urting, Werner Van Belle, Viviane Jonckers, Tom Holvoet, Yolande Berbers and Karel De Vlaminck In this paper the authors clarify the following dimensions of component-related issues: component blueprint versus component instance, internal (has) versus external visible (gives) component characteristics, and mandatory versus recommended versus optional component characteristics. Then the authors categorize component characteristics. Back to the top Reuse An Evolutionary Approach to Constructing Effective Software Reuse Repositories [PDF] Scott Henninger Repositories for software reuse are faced with two interrelated problems: acquiring the knowledge to initially construct the repository, and modifying the repository to meet the evolving and dynamic needs of software development organizations. This paper outlines an approach that avoids these problems by choosing a retrieval method that utilizes minimal repository structure to effectively support the process of finding software components. The approach is demonstrated through a pair of proof-of-concept prototypes: PEEL, a tool to semi-automatically identify reusable components; and CodeFinder, a retrieval system that compensates for the lack of explicit knowledge structures through a spreading activation retrieval process. A Repository to Facilitate Reuse in Component - Based Web Engineering [PDF] Martin Gaedke, Joern Rehse and Guntram Graef Web application development suffers increasingly from the coarse-grained implementation model of the Web, as established software design concepts are hardly applicable to it. The object-oriented WebComposition Markup Language (WCML) addresses these problems with a fine-grained component-based model and thus supports the application of software engineering practice to applications in the Web. This paper introduces the WebComposition Repository as a key tool for a systematic approach to code reuse. The repository is used for storing, managing, and retrieving large numbers of WCML components. Formalizing and Automating Component Reuse [PDF] Yonghao Chen and Betty H. C. Cheng Using existing components to construct software systems has significant potential to improving software productivity and quality. A key problem in software component reuse is the selection of appropriate components for satisfying a given requirement. In this paper, the authors define a component interface generality relation that provides a foundation for component selection. This generality relation, represented in terms of formal specifications, precisely captures the semantic obligations for an existing component to satisfy the requirements of a target system. The formal specifications facilitate the (semi-) automatic determination of the generality relation. The authors show how this generality relation has been used to determine the reusability of software components in a software architecture-based reuse and integration environment. Implementing Reusable Object-Oriented Components [PDF] Yannis Smaragdakis and Don Batory Object-oriented (OO) classes are generally not reusable because they are not meaningful in isolation; most classes only have meaning as members of cooperating suites of classes (e.g., design patterns). These suites usually arise in designs, but rarely exist as encapsulated entities in OO implementations. In this paper the authors present a method for directly mapping cooperating suites of classes into encapsulated C++ implementations. Their method is an improvement over the VanHilst and Notkin approach for implementing collaboration-based designs and constitutes a step towards more reusable (object-oriented) components. The Reusable Asset Specification [HTML] Paul Allen In this article the author states two chronic problems the software industry must solve for component reuse to be fully realized. Reusable Asset Specification (RAS) is also discussed which focuses on classification, content, and usage of software assets. Back to the top