A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Active design reviews: principles and practices
ICSE '85 Proceedings of the 8th international conference on Software engineering
Reuse in Command-and-Control Systems
IEEE Software
A procedure for designing abstract interfaces for device interface modules
ICSE '81 Proceedings of the 5th international conference on Software engineering
Designing software for ease of extension and contraction
ICSE '78 Proceedings of the 3rd international conference on Software engineering
Chapter I: Notes on structured programming
Structured programming
On the Design and Development of Program Families
IEEE Transactions on Software Engineering
The Modular Structure of Complex Systems
IEEE Transactions on Software Engineering
Refinement of Software Product Line Architectures through Recursive Modeling Techniques
OTM '09 Proceedings of the Confederated International Workshops and Posters on On the Move to Meaningful Internet Systems: ADI, CAMS, EI2N, ISDE, IWSSA, MONET, OnToContent, ODIS, ORM, OTM Academy, SWWS, SEMELS, Beyond SAWSDL, and COMBEK 2009
Proceedings of the 20th ACM SIGPLAN workshop on Partial evaluation and program manipulation
Domain modeling as a basis for building a meshing tool software product line
Advances in Engineering Software
| Hi-index | 0.00 |
The success of family-oriented software development processes depends on how well software engineers can predict the family members that will be needed. Commonality analysis is an analytical technique for deciding what the members of a family should be. It is in use at Lucent Technologies as part of a domain engineering process known as family-oriented abstraction, specification, and translation (FAST). Lucent software developers have performed commonality analyses on more than 20 families; results have been sufficiently encouraging that the analysis process is rapidly undergoing institutionalization.