by Nenad Medvidovic, Paul Grünbacher, Alexander Egyed, Barry W. Boehm
Abstract:
Numerous notations, methodologies, and tools exist to support software system modeling. While individual models help to clarify certain system aspects, the large number and heterogeneity of models may ultimately hamper the ability of stakeholders to communicate about a system. A major reason for this is the discontinuity of information across different models. In this paper, we present an approach for dealing with that discontinuity. We introduce a set of "connectors" to bridge models, both within and across the "upstream" activities in the software development lifecycle (specifically, requirements, architecture, and design). While the details of these connectors are dependent upon the source and destination models, they share a number of underlying characteristics. These characteristics can be used as a starting point in providing a general understanding of software model connectors. We illustrate our approach by applying it to a large-scale system we are currently designing and implementing in collaboration with a third-party organization.
Reference:
Software Model Connectors: Bridging Models across the Software Lifecycle (Nenad Medvidovic, Paul Grünbacher, Alexander Egyed, Barry W. Boehm), In Proceedings of the Thirteenth Int'l Conference on Software Engineering & Knowledge Engineering, (SEKE 2001), Buenos Aires, Argentina, 2001.
Bibtex Entry:
@Conference{DBLP:conf/seke/MedvidovicGEB01,
author = {Nenad Medvidovic and Paul Grünbacher and Alexander Egyed and Barry W. Boehm},
title = {Software Model Connectors: Bridging Models across the Software Lifecycle},
booktitle = {Proceedings of the Thirteenth Int'l Conference on Software Engineering \& Knowledge Engineering, (SEKE 2001), Buenos Aires, Argentina},
year = {2001},
pages = {387-396},
abstract = {Numerous notations, methodologies, and tools exist to support software
system modeling. While individual models help to clarify certain
system aspects, the large number and heterogeneity of models may
ultimately hamper the ability of stakeholders to communicate about
a system. A major reason for this is the discontinuity of information
across different models. In this paper, we present an approach for
dealing with that discontinuity. We introduce a set of "connectors"
to bridge models, both within and across the "upstream" activities
in the software development lifecycle (specifically, requirements,
architecture, and design). While the details of these connectors
are dependent upon the source and destination models, they share
a number of underlying characteristics. These characteristics can
be used as a starting point in providing a general understanding
of software model connectors. We illustrate our approach by applying
it to a large-scale system we are currently designing and implementing
in collaboration with a third-party organization.},
file = {:Conferences\\SEKE 2001 - Software Model Connectors - Bridging Models across the Software Lifecycle\\Software Model Connectors - Bridging Models across the Software Lifecycle-preprint.pdf:PDF},
keywords = {},
owner = {paul},
timestamp = {2015.09.12},
}