ACM Computing Surveys (CSUR)
Architectural mismatch or why it's hard to build systems out of existing parts
Proceedings of the 17th international conference on Software engineering
ArchJava: connecting software architecture to implementation
Proceedings of the 24th International Conference on Software Engineering
Detecting architectural mismatches during systems composition
Detecting architectural mismatches during systems composition
Software Reuse Research: Status and Future
IEEE Transactions on Software Engineering
Parseweb: a programmer assistant for reusing open source code on the web
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Documenting after the fact: Recovering architectural design decisions
Journal of Systems and Software
Code Reuse in Open Source Software
Management Science
Toward a Catalogue of Architectural Bad Smells
QoSA '09 Proceedings of the 5th International Conference on the Quality of Software Architectures: Architectures for Adaptive Software Systems
Pragmatic software reuse
Finding relevant functions in millions of lines of code
Proceedings of the 33rd International Conference on Software Engineering
| Hi-index | 0.00 |
Opportunistic reuse, a need based sourcing of software modules without any prior plan is a common practice in software development. It is popular due to rapid productivity improvement and fewer impediments while undertaking reuse task. However, developers use informal criteria to select an external module for reuse. The composition of such a module may introduce undesirable emergent behavior due to new or unknown design decisions. Hence, we propose to systematize selection of an external module by defining selection criteria based on extracted design decisions from source code. This would help developers in making informed selection of external modules there by avoiding or being aware of design mismatches when reusing opportunistically.