by Alexander Egyed, Nenad Medvidovic, Cristina Gacek
Abstract:
Existing approaches to modelling software systems all too often neglect the issue of component-mismatch identi®cation and resolution. The traditional view of software development over-emphasises synthesis at the expense of analysis ± the latter frequently being seen as a problem which only needs to be dealt with during the integration stage towards the end of a development project. The paper discusses two software modelling and analysis techniques, all tool supported, and emphasises the vital role analysis can play in identifying and resolving risks early on. This work also combines model-based development (e.g. architectural modelling) with component-based development (e.g. COTS and legacy systems), and shows how their mismatch-detection capabilities complement one another to provide a more comprehensive coverage of development risks.
Reference:
Component-based perspective on software mismatch detection and resolution. (Alexander Egyed, Nenad Medvidovic, Cristina Gacek), In Journal IEE Proceedings - Software, volume 147, 2000.
Bibtex Entry:
@Article{dblp:journals/iee/EgyedMG00,
author = {Alexander Egyed and Nenad Medvidovic and Cristina Gacek},
title = {Component-based perspective on software mismatch detection and resolution.},
journal = {Journal IEE Proceedings - Software},
year = {2000},
volume = {147},
number = {6},
pages = {225-236},
abstract = {Existing approaches to modelling software systems all too often neglect
the issue of component-mismatch identi®cation and resolution. The
traditional view of software development over-emphasises synthesis
at the expense of analysis ± the latter frequently being seen as
a problem which only needs to be dealt with during the integration
stage towards the end of a development project. The paper discusses
two software modelling and analysis techniques, all tool supported,
and emphasises the vital role analysis can play in identifying and
resolving risks early on. This work also combines model-based development
(e.g. architectural modelling) with component-based development (e.g.
COTS and legacy systems), and shows how their mismatch-detection
capabilities complement one another to provide a more comprehensive
coverage of development risks.},
file = {:Journals\\IEE Software 2000 - A Component-Based Perspective of Software Mismatch Detection and Resolution\\Component-based perspective on software mismatch detection and resolution-preprint.pdf:PDF},
keywords = {},
}