ACM Computing Surveys (CSUR)
Integrated object-oriented testing and development processes
Communications of the ACM
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Design patterns for object-oriented software development
Design patterns for object-oriented software development
Sixteen questions about software reuse
Communications of the ACM
Research directions in software architecture
ACM Computing Surveys (CSUR)
An integrated approach to software reuse practice
SSR '95 Proceedings of the 1995 Symposium on Software reusability
SSR '95 Proceedings of the 1995 Symposium on Software reusability
Using design patterns to develop reusable object-oriented communication software
Communications of the ACM - Special issue on object-oriented experiences and future trends
The fountain model and its impact on project schedule
ACM SIGSOFT Software Engineering Notes
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
An Empirical Study of Representation Methods for Reusable Software Components
IEEE Transactions on Software Engineering
VLDB '96 Proceedings of the 22th International Conference on Very Large Data Bases
Hi-index | 0.00 |
Although development processes are considered important in determining the quality of the product, often processes and products are considered as separate entities. This results in loss of information regarding dependencies spanning across processes and products. In this paper we propose a unit called Unified Reuse Artifact (URA) which can represent artifacts of either the "process" or the "product," in effect representing an artifact of the "solution." With this, a solution is represented as a directed graph of URAs establishing dependencies in a unified manner. This helps bring in other possibilities like project tracking, deciphering contexts and evolution in a unified way, etc. We then propose a process model oriented towards solutions, and which strives to reuse earlier experiences with the concept of a "Solution Framework."