Domain-specific software architecture (DSSA) frequently asked questions (FAQ)
ACM SIGSOFT Software Engineering Notes
Exploiting domain architectures in software reuse
SSR '95 Proceedings of the 1995 Symposium on Software reusability
DSSA (Domain-Specific Software Architecture): pedagogical example
ACM SIGSOFT Software Engineering Notes
Framing software reuse: lessons from the real world
Framing software reuse: lessons from the real world
Modeling multiple domains in software reuse
Proceedings of the 1997 symposium on Software reusability
Object-oriented application frameworks
Communications of the ACM
Frameworks = (components + patterns)
Communications of the ACM
Frame-based method for customizing generic software architectures
SSR '99 Proceedings of the 1999 symposium on Software reusability
Generative programming: methods, tools, and applications
Generative programming: methods, tools, and applications
Applying feature models in industrial settings
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
A Discipline of Programming
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
FORM: A feature-oriented reuse method with domain-specific reference architectures
Annals of Software Engineering
XVCL Approach to Separating Concerns in Product Family Assets
GCSE '01 Proceedings of the Third International Conference on Generative and Component-Based Software Engineering
Handling variant requirements in domain modeling
Journal of Systems and Software - Special issue: Best papers on Software Engineering from the SEKE'01 Conference
Modeling and analysis of product-line variants
Proceedings of the 16th International Software Product Line Conference - Volume 2
Hi-index | 0.00 |
Reuse of software is a promising approach to improving the efficiency of software development regarding time, cost and quality. Reuse requires a systematic approach. The best results are achieved if we focus on systems in a specific domain, so-called product line. The key difference between the conventional software engineering and software product line engineering is variant management. The main idea of software product line is to identify the common core functionality which can be implemented once and reused afterwards for all members of the product line. To facilitate this reuse opportunity the domain engineering phase makes the domain model comprising the common as well as variant requirements. In principle, common requirements among systems in a family are easy to handle. However, problem arises during handling variants. Different variants have dependencies on each other; a single variant can affect several variants of the domain model. These problems become complex when the volume of information grows in a domain and there are a lot of variants with several interdependencies. Hence, a separate model is required for handling the variants. This paper presents a mechanism, which we call, Unified Tabular Method to facilitate the management of variant dependencies in product lines. The tabular method consists of a variant part to model the variants and their dependencies, and a decision table to depict the customization decision regarding each variant while deriving customized products. Tabular method alleviates the problem of possible explosion of variant combinations and facilitates the tracing of variant information in the domain model