This paper introduces reflexion models as a way to communicate and reason about an implemented software architecture. In particular, an engineer defines a high-level model and specifies how the model maps to the source. A tool then computes a software reflexion model that shows where the engineer's high-level model agrees with and where it differs from a model of the source.
The authors provide a formal definition of Software Reflexion Models. Furthermore, the authors make it more concrete by describing experiences in the light of reengineering, Design conformance and System Understanding.
The input of a reflexion model are a high-level model, a source model and a map. The reflextion model will then present the summary information in the context of the high-level model defined by the engineer.
%0 Conference Paper
%1 murphy95reflexionModels
%A Murphy, Gail C.
%A Notkin, David
%A Sullivan, Kevin J.
%B SIGSOFT FSE
%D 1995
%K architecture caseStudy model reconstructing software
%P 18-28
%T Software Reflexion Models: Bridging the Gap Between Source and High-Level Models.
%U http://dblp.uni-trier.de/db/conf/sigsoft/fse95.html#MurphyNS95
@inproceedings{murphy95reflexionModels,
added-at = {2009-01-23T14:25:13.000+0100},
author = {Murphy, Gail C. and Notkin, David and Sullivan, Kevin J.},
biburl = {https://www.bibsonomy.org/bibtex/2e668754d459106881a9f8f85c436e59b/ericbouwers},
booktitle = {SIGSOFT FSE},
date = {2002-12-06},
description = {This paper introduces reflexion models as a way to communicate and reason about an implemented software architecture. In particular, an engineer defines a high-level model and specifies how the model maps to the source. A tool then computes a software reflexion model that shows where the engineer's high-level model agrees with and where it differs from a model of the source.
The authors provide a formal definition of Software Reflexion Models. Furthermore, the authors make it more concrete by describing experiences in the light of reengineering, Design conformance and System Understanding.
The input of a reflexion model are a high-level model, a source model and a map. The reflextion model will then present the summary information in the context of the high-level model defined by the engineer.},
ee = {http://doi.acm.org/10.1145/222124.222136},
interhash = {4b1c29894843ec99f7e2f90643bc3753},
intrahash = {e668754d459106881a9f8f85c436e59b},
keywords = {architecture caseStudy model reconstructing software},
pages = {18-28},
timestamp = {2009-04-21T13:13:59.000+0200},
title = {Software Reflexion Models: Bridging the Gap Between Source and High-Level Models.},
url = {http://dblp.uni-trier.de/db/conf/sigsoft/fse95.html#MurphyNS95},
year = 1995
}