Component-based perspective on software mismatch detection and resolution

Alexander Egyed, Nenad Medvidović, C Gacek

IEE Proceedings - Software · 2000 · 29 citations · 23 references

Concepts

TL;DR

Existing software modelling approaches often ignore component‑mismatch detection, and the traditional development focus on synthesis relegates analysis to a late integration stage. The paper investigates two tool‑supported modelling and analysis techniques to demonstrate how early analysis can identify and resolve component‑mismatch risks. The authors integrate model‑based development (e.g., architectural modelling) with component‑based development (e.g., COTS and legacy systems) to combine complementary mismatch‑detection capabilities. This integration provides more comprehensive coverage of development risks by leveraging the complementary mismatch‑detection strengths of both approaches.

Abstract

Existing approaches to modelling software systems all too often neglect the issue of component-mismatch identification 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.

References

23