The design and implementation of hierarchical software systems with reusable components

Batory, Don; O’Malley, Sean

doi:10.1145/136586.136587

Cited by 442 publications

(256 citation statements)

References 24 publications

Supporting

Mentioning

250

Contrasting

Unclassified

Order By: Relevance

“…An architecture must capture variability so as to represent product families [23], and domain-specific languages are used to define such families and generate individual products. In generative programming, for example, an architecture is represented as templates based on GenVoca grammar [3], and code for different products can be generated from instances of such templates. In this paper we propose an alternative approach.…”

Section: Domain Modelsmentioning

confidence: 99%

“…According to the feature model, each of pdt 3 and pdt 5 may or may not exist. If only pdt 3 exists, then we have the cruise control system; and if both pdt 3 and pdt 5 co-exist then we have the adaptive cruise control system. Looking at Fig.…”

Section: Example: a Component Model For Vehicular Systemsmentioning

confidence: 99%

“…12(a). [3] START ACCEL RESUME sensor (e.g. a radar) and calculates the distance separating the vehicle from the traffic in front of the vehicle.…”

Section: Example: a Component Model For Vehicular Systemsmentioning

confidence: 99%

See 2 more Smart Citations

Domain-Specific Software Component Models

Lau

Taweel

2009

Component-Based Software Engineering

View full text Add to dashboard Cite

Abstract. We believe that for developing applications in a specific domain, the best kind of software component model to use is a domain-specific one. We also believe that current component models intended for specific domains are actually not domain-specific. In this paper we present an approach for deriving domain-specific component models from the domain model of a given domain, and show why such a component model is better than existing models that are not domain-specific.

show abstract

Section: Domain Modelsmentioning

confidence: 99%

Section: Example: a Component Model For Vehicular Systemsmentioning

confidence: 99%

See 1 more Smart Citation

Domain-Specific Software Component Models

Lau

Taweel

2009

Component-Based Software Engineering

View full text Add to dashboard Cite

show abstract

“…Hewlett Packard have been rumoured to be representing their product lines as DSSAs. As early as 1986 a product-line for CAD software had been considered [3]. Product-line approaches appear to be very productive and promising; we present possible product-line descriptions later in two chapters of this book.…”

Section: Components and How To Use Themmentioning

confidence: 99%

“…These can be set up to be interactive, capturing design decisions as required. This has been called "generative reuse" by its originator, Don Batory [3], and is an approach that can be expected to be developed further.…”

Section: Components and How To Use Themmentioning

confidence: 99%

An Introduction and History of Software Architectures, Components, and Reuse

Barroca¹,

Hall²,

Hall³

2000

Software Architectures

View full text Add to dashboard Cite

SummarySoftware components and architectures are gaining considerable support as the way to develop object-oriented systems and business applications. Current developments in component-based software reuse is taking place in the context of some thirty years of history. It is as well to rehearse that history, as we do in this chapter, and draw lessons from it, lest we repeat the errors of the past.This chapter fills in the background to the rest of the book. Concepts and ideas assumed in the other chapters will be explained and set in a context which will aid the reading and understanding of those chapters. The specialist reader already conversant with the field may wish to skip this chapter, though it is hoped that even for such a reader the orientation adopted here will be informative and helpful.

show abstract

Feature-oriented engineering of PBX software for adaptability and reuseability

Kang

Kim

Lee³

et al. 1999

Softw: Pract. Exper.

View full text Add to dashboard Cite

Incorporating a high level of adaptability and reusability into software is one challenge that all software engineers face. PBX (Private Branch Exchange) is one such system that requires a high level of adaptability and reusability because of rapidly expanding service features, ever changing communication technology, continuously evolving standards and diverse communication laws and standards in different countries. The software engineering community has made various efforts to address the problem of enhancing software adaptability and reusability. As a result, many programming concepts, such as information hiding, encapsulation, object orientation, abstract data type and modularization, have been developed. Although adequate application of these principles requires the domain or program family perspective, most methods, so far, have been oriented toward developing a single application. FORM (Feature-Oriented Reuse Method), the domain-based software reuse method applied in this paper, concentrates on analyzing and modeling commonalities and differences in applications of a given domain and using the analysis results to develop domain-oriented architectures and software components. The model that captures commonalities and differences is called the 'feature model' and it is used for both the engineering of reusable domain artifacts and the development of actual application software with reusable artifacts. We found that FORM facilitates analysis of variability, as well as commonality, of software before the start of engineering and implementation. With this understanding, adaptability and reusability can be built into software. Also, feature modeling has been found to be an effective method for identifying objects.

show abstract

The design and implementation of hierarchical software systems with reusable components

Cited by 442 publications

References 24 publications

Domain-Specific Software Component Models

Domain-Specific Software Component Models

An Introduction and History of Software Architectures, Components, and Reuse

Feature-oriented engineering of PBX software for adaptability and reuseability

Contact Info

Product

Resources

About