| |
[Download PDF here!]
Authors: Alexander Egyed and Cristina
Gacek
A
major emphasis in software development is placed on identifying and
reconciling architectural and design mismatches. Those mismatches
happen during software development on two levels: while composing
system components (e.g. COTS or in-house developed) and while
reconciling view perspectives. Composing components into a system
and ’composing’ views (e.g. diagrams) into a system model are
often seen as being somewhat distinct aspects of software
development, however, as this work shows, their approaches in
detecting mismatches complement each other very well. In both cases,
the composition process may result in mismatches that are caused by
clashes between development artifacts. Our component-based
integration approach is more high-level and can be used early on for
risk assessment while little information is available. Model-based
integration on the other hand needs more information to start with
but is more precise and can handle large amounts of redundant
information. This paper describes both integration approaches and
discusses their commonalties and differences. Both integration
approaches are automateable and some tools support is already
available.
|
|