Commonality and variability in software engineering
IEEE SoftwarePublished 1 January 1998
James O. Coplien, Daniel Hoffman, David M. Weiss
Citations372
SJR quartileQ2
SJR score0.56
SNIP1.10
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
The article describes how to perform domain engineering by identifying the commonalities and variabilities within a family of products through interesting examples dealing with reuse libraries, design patterns, and programming language design.
Abstract
The article describes how to perform domain engineering by identifying the commonalities and variabilities within a family of products. Through interesting examples dealing with reuse libraries, design patterns, and programming language design, the authors suggest a systematic scope, commonalities, and variabilities approach to formal analysis. Their SCV analysis has been an integral part of the FAST (Family-oriented Abstraction, Specification, and Translation) technology applied to over 25 domains at Lucent Technologies.
Keywords
Computer Science
Design Patterns: Elements of Reusable Object-Oriented Software
21,864 Citations1994Erich Gamma, Richard F. Helm +2 more
The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns, which most experienced OOP designers will find out they've known about patterns all along.
Software Architecture in Practice
5,064 Citations1997Len Bass, Paul Clements +1 more
This second edition of this book reflects the new developments in the field and new understanding of the important underpinnings of software architecture with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters.
Communications of the ACMOn the criteria to be used in decomposing systems into modules
4,674 Citations1972David Lorge Parnas
TU/e Research PortalNotes on Structured Programming
831 Citations1970Edsger W. Dijkstra
The final author version and the galley proof are versions of the publication after peer review that features the final layout of the paper including the volume, issue and page numbers.
IEEE Transactions on Software EngineeringOn the Design and Development of Program Families
766 Citations1976David Lorge Parnas
A conventional approach called "sequential development" is compared to "stepwise refinement" and "specification of information hiding modules" and it is demonstrated that the two methods are based on the same concepts but bring complementary advantages.
ACM Transactions on Software Engineering and MethodologyThe design and implementation of hierarchical software systems with reusable components
605 Citations1992Don Batory, Sean O’Malley
A domain-independent model of hierarchical software system design and construction that is based on interchangeable software components and large-scale reuse that is a blueprint for achieving software component technologies in many domains is presented.
IEEE Transactions on Software EngineeringThe Modular Structure of Complex Systems
368 Citations1985David Lorge Parnas, Paul Clements +1 more
This paper shows how the software design technique known as information hiding, or abstraction, can be supplemented by a hierarchically structured document, which it is called a module guide, intended to allow both designers and maintainers to identify easily the parts of the software that they must understand, without reading irrelevant details.
On the Criteria to Be Used in Decomposing Systems into Modules
236 Citations1972David Lorge Parnas
Multiparadigm Design in C++
151 Citations2018
IEEE SoftwareReuse in Command-and-Control Systems
130 Citations1994Jennifer B. O'Connor, C. Mansour +2 more
This work presents CCSD's experience to date using Synthesis, an approach based on domain-specific reuse, by which an organization can standardize its perceptions of customers' needs and effective solutions.
ComputerApplying software product-line architecture
95 Citations1997David Dikel, David W. Kane +3 more
To learn what factors determine the effective use of software architecture, the authors looked at Nortel (Northern Telecom), a company with nearly 20 years of experience developing complex software architecture for telecommunications product families and identified six principles that help reduce the complexity of an evolving family of products.
LILEANNA: a parameterized programming language
51 Citations2002Will Tracz
The author describes key elements of the language and presents examples illustrating its applicability in support of a megaprogramming software development paradigm.
IEEE SoftwareCreating applications from components: a manufacturing framework design
35 Citations1996Hans Albrecht Schmid
The manufacturing application framework described, lets you develop software from components without programming and generalizes the class structure which models a fixed domain application through a sequence of transformations.
Auditdraw: generating audits the FAST way
33 Citations2002Nirmal Kumar Gupta, Lalita Jategaonkar Jagadeesan +2 more
The FAST process, the language, the accompanying process for specifying the requirements and generating the code for the 5ESS audits software, and the expected benefits of this project are described.
Lecture notes in computer scienceArchitecting for Domain Variability
15 Citations1998Jacques Meekel, Thomas B. Horton +1 more
This paper addresses how domain analysis served to help create reusable achitectures and components in the development of a real-time embedded system and the approach to incorporating tailorability into these components is described.
ACM SIGSOFT Software Engineering NotesCreating reusable architectures
11 Citations1997W. Lam
Initial experience of creating reusable architectures in the avionics domain is described and a set of RACE guidelines are presented which summarises the initial experience.