The goal of this experiement is to learn what is Model-Based Integration Mismatches, what are the causes of these mismatches, how to detect such type of mismatches, and what kind of available tools that can help/assist/automate the inference process.
I chose Sonargraph-Architect to See its analysis result.
I have a "Free-Community License" to use this tool. The license provided by www.hello2morrow.com; 2002-2011 hello2morrow GmbH, through an allowed/permited procedure.
The author of the tool: Alexander von Zitzewitz.
The example given in this post discussed in the A. Egyed and C. Gacek resaerch paper titled, "Automatically Detecting Mismatches during Component-Based and Model-Based Development", in Proc. of the International Conference on Automated Software Engineering, Cocoa Beach, Florida, Oct. 1999, pp. 191-198.
My reasons to study this example is only for academic purposes. I research in this area and I wanted to understand the Model-Based Integration Mismatches, apply the "View Integraion Framework" proposed by the authors, and regenerate the analysis results with the available tools.
I have been using Sonargraph-Architect for 5 months. While I was reading the paper mentioned above I was sure that Sonargraph-Architect will detect the Architecturtal mismatch shown in the example of the paper.
The example shows that a dependency in Design View violates some Architectural View Constraints.
In different words, a dependency in the Design View has no corresponding dependency in the Architectural View.
The Design model has a dependecy from User Interface to Inventory System.
However, the Architectural view does not have such a dependency.
I still haven't contact the Authors for a permission to copy the figures provided in their paper.
But, the Sonargraph analysis result shown below.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment