Existing approaches to modeling software systems all too often neglect the issue of component mismatch identification and resolution. The traditional view of software development over-emphasizes synthesis at the expense of analysis - the latter frequently being seen as a problem one only needs to deal with during the integration stage towards the end of a development project. Our work combines two software modeling and analysis techniques, all tool supported, and emphasizes the vital role analysis can play in identifying and resolving risks early on. Our work also combines model-based development (e.g., architectural modeling) with component-based development (e.g., COTS and legacy systems) and shows how their mismatch detection capabilities complement one another in providing a more comprehensive coverage of development risks.
- A Component-Based Perspective of Software Mismatch Detection and Resolution
- Automatically Detecting Mismatches during Component-Based and Model-Based Development
|COTS Software Incorporation|
|Product Families and Product Lines|
|Refinement from Software Requirements to Architecture|
|Architecture and Design Recovery (reverse engineering)|
|Software Architecture and UML|