Supporting software evolution with intentional software views
K. Mens, T. Mens, and M. Wermelinger. IWPSE '02: Proceedings of the International Workshop on Principles of Software Evolution, page 138--142. New York, NY, USA, ACM Press, (2002)
DOI: 10.1145/512035.512068
Abstract
Maintaining and evolving large software systems is hard. One underlying cause is that existing modularisation mechanisms are inadequate to handle crosscutting concerns. We propose intentional software views as an intuitive and lightweight means of modelling such concerns. They increase our ability to understand, modularise and browse the implementation by grouping together source-code entities that address a same concern. Alternative descriptions of the same intentional view can be provided and checked for consistency. In addition, the model supports the declaration, verification and enforcement of relations among intentional views. This facilitates software evolution by providing the ability to detect invalidation of important intentional relationships among concerns when the software is modified.
Use idea of aspects to support evolution? Has anyone done this?
---
- poorly described, more detail needed on how views are created and how they are maintained
- "concerns crosscut the dominant modularization" -. 138
- seems unapplicable given language specificity
- someone must update the view language each time the system is updated
%0 Conference Paper
%1 mens02
%A Mens, Kim
%A Mens, Tom
%A Wermelinger, Michel
%B IWPSE '02: Proceedings of the International Workshop on Principles of Software Evolution
%C New York, NY, USA
%D 2002
%I ACM Press
%K evolution views software litmap
%P 138--142
%R 10.1145/512035.512068
%T Supporting software evolution with intentional software views
%U http://dx.doi.org/10.1145/512035.512068
%X Maintaining and evolving large software systems is hard. One underlying cause is that existing modularisation mechanisms are inadequate to handle crosscutting concerns. We propose intentional software views as an intuitive and lightweight means of modelling such concerns. They increase our ability to understand, modularise and browse the implementation by grouping together source-code entities that address a same concern. Alternative descriptions of the same intentional view can be provided and checked for consistency. In addition, the model supports the declaration, verification and enforcement of relations among intentional views. This facilitates software evolution by providing the ability to detect invalidation of important intentional relationships among concerns when the software is modified.
%@ 1581135459
@inproceedings{mens02,
abstract = {Maintaining and evolving large software systems is hard. One underlying cause is that existing modularisation mechanisms are inadequate to handle crosscutting concerns. We propose intentional software views as an intuitive and lightweight means of modelling such concerns. They increase our ability to understand, modularise and browse the implementation by grouping together source-code entities that address a same concern. Alternative descriptions of the same intentional view can be provided and checked for consistency. In addition, the model supports the declaration, verification and enforcement of relations among intentional views. This facilitates software evolution by providing the ability to detect invalidation of important intentional relationships among concerns when the software is modified.},
added-at = {2006-03-24T16:34:33.000+0100},
address = {New York, NY, USA},
author = {Mens, Kim and Mens, Tom and Wermelinger, Michel},
biburl = {https://www.bibsonomy.org/bibtex/28610ced4361fa460cdcf450f5bd95c4d/neilernst},
booktitle = {IWPSE '02: Proceedings of the International Workshop on Principles of Software Evolution},
citeulike-article-id = {333433},
comment = {Use idea of aspects to support evolution? Has anyone done this?
---
- poorly described, more detail needed on how views are created and how they are maintained
- "concerns crosscut the dominant modularization" -. 138
- seems unapplicable given language specificity
- someone must update the view language each time the system is updated},
description = {sdasda},
doi = {10.1145/512035.512068},
interhash = {2362d06777adbe322a172b3521b7aef6},
intrahash = {8610ced4361fa460cdcf450f5bd95c4d},
isbn = {1581135459},
keywords = {evolution views software litmap},
pages = {138--142},
priority = {0},
publisher = {ACM Press},
timestamp = {2006-03-24T16:34:33.000+0100},
title = {Supporting software evolution with intentional software views},
url = {http://dx.doi.org/10.1145/512035.512068},
year = 2002
}