Reverse engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Software product lines: practices and patterns
Software product lines: practices and patterns
Migrating Legacy Systems towards Object-Oriented Platforms
ICSM '97 Proceedings of the International Conference on Software Maintenance
Risks Involved in Reengineering Projects
WCRE '99 Proceedings of the Sixth Working Conference on Reverse Engineering
A Case Study in Software Wrapping
ICSM '98 Proceedings of the International Conference on Software Maintenance
Mining and Managing Software Assets
STEP '02 Proceedings of the 10th International Workshop on Software Technology and Engineering Practice
Report from the Second International Workshop on Adoption-Centric Software Engineering (ACSE 2002)
STEP '02 Proceedings of the 10th International Workshop on Software Technology and Engineering Practice
Evolving Industrial Software Architectures into a Software Product Line: A Case Study
QoSA '09 Proceedings of the 5th International Conference on the Quality of Software Architectures: Architectures for Adaptive Software Systems
Extending the reflexion method for consolidating software variants into product lines
Software Quality Control
Recovering object-oriented framework for software product line reengineering
ICSR'11 Proceedings of the 12th international conference on Top productivity through software reuse
A systematic review of software architecture evolution research
Information and Software Technology
| Hi-index | 0.00 |
The Options Analysis for Reengineering (OAR) method is a systematic, architecture-centric means for mining existing components for a product line or new software architecture. The method incorporates a set of scalable techniques and exercises to collaboratively analyze existing components, determine viable mining options, and evaluate the most promising options. The OAR method has 5 activities that are followed in a systematic manner to identify components for mining and estimate the cost and risk of changes required to each legacy component to enable its reuse within a new software architecture. The OAR method provides visibility into this highly complex analysis activity. It also provides insights into implicit stakeholder assumptions, constraints, and other major drivers that impact the mining of components. Results from a pilot application of the OAR method are presented in this paper.