Design patterns for object-oriented software development
Design patterns for object-oriented software development
Software reuse: architecture, process and organization for business success
Software reuse: architecture, process and organization for business success
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
PuLSE: a methodology to develop software product lines
SSR '99 Proceedings of the 1999 symposium on Software reusability
Software product-line engineering: a family-based software development process
Software product-line engineering: a family-based software development process
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
Component-based product line development: the KobrA approach
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
Designing Concurrent, Distributed, and Real-Time Applications with Uml
Designing Concurrent, Distributed, and Real-Time Applications with Uml
Object Oriented Analysis and Modeling for Families of Systems with UML
ICSR-6 Proceedings of the 6th International Conerence on Software Reuse: Advances in Software Reusability
The variation point model for software product lines
The variation point model for software product lines
Modeling variability in software product lines with the variation point model
Science of Computer Programming - Special issue: Software variability management
Fusion: A System For Business Users To Manage Program Variability
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
A major challenge for software reuse is developing components that can be reused in several applications. This paper describes a systematic method for providing components that can be extended through variation points, as initially specified in the software requirements. Allowing the reuser or application engineer to extend components at pre-specified variation points creates a more flexible set of components. The existing variation point methods do not provide enough design detail for the reuser. This paper introduces a method called the Variation Point Model (VPM), which models variation points at the design level, beginning with the common requirements.