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.
| Original language | English |
|---|---|
| Pages (from-to) | 225-236 |
| Number of pages | 12 |
| Journal | IEE Software Engineering |
| Volume | 147 |
| Issue number | 6 |
| Publication status | Published - 2000 |
Fields of science
- 102 Computer Sciences
- 102022 Software development