Software reuse: architecture, process and organization for business success
Software reuse: architecture, process and organization for business success
ICSR-7 Proceedings of the 7th International Conference on Software Reuse: Methods, Techniques, and Tools
Reusing UML Specifications in a Constrained Application Domain
APSEC '98 Proceedings of the Fifth Asia Pacific Software Engineering Conference
Integrating Feature Modeling with the RSEB
ICSR '98 Proceedings of the 5th International Conference on Software Reuse
Barriers to adoption of software reuse a qualitative study
Information and Management
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Finding Reusable UML Sequence Diagrams Automatically
IEEE Software
Software Reuse Research: Status and Future
IEEE Transactions on Software Engineering
Model transformation language MOLA
MDAFA'03 Proceedings of the 2003 European conference on Model Driven Architecture: foundations and Applications
Complementary use case scenario representations based on domain vocabularies
MODELS'07 Proceedings of the 10th international conference on Model Driven Engineering Languages and Systems
Application logic patterns reusable elements of user-system interaction
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part I
Towards an ontology-based retrieval of UML Class Diagrams
Information and Software Technology
A survey and comparison of transformation tools based on the transformation tool contest
Science of Computer Programming
Hi-index | 0.00 |
Reuse of software artifacts (blueprints and code) is normally associated with organising a systematic reuse framework most often constructed for a specific problem domain. In this paper we present a system (language, tool, reuse process) where software reuse is based on building and retrieving of so-called software cases (large compound artifacts) that can be reused between domains. The system is opportunistic in that software cases result from usual (non-reuse oriented) activities where also semantic information is added. This information is used to support regular development but may serve later to retrieve software cases. Having this common semantic basis, we can organise a systematic cross-domain reuse process where application logic of one system can be reused for systems within different domains.