Difference between revisions of "AM3/Use Cases/PetStore Navigability"

From Eclipsepedia

< AM3
Jump to: navigation, search
(First full version of the page)
(Formatting upgrade)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
 
{{Backlink|MDT}} {{Backlink|MoDisco}} [[Image:Am3Logo.png|right]]  
 
{{Backlink|MDT}} {{Backlink|MoDisco}} [[Image:Am3Logo.png|right]]  
  
This AM3 use case titled '''Pet Store Navigability''' has been implemented by [http://www.emn.fr/x-info/atlanmod/index.php/User:Doux Guillaume Doux] and published in May 2009.  
+
This AM3 use case titled '''Pet Store Navigability''' has been implemented by [http://www.emn.fr/x-info/atlanmod/index.php/User:Doux Guillaume Doux] and initially published in May 2009.  
  
 
== Keywords  ==
 
== Keywords  ==
Line 15: Line 15:
 
Considering inter-model navigabiliy, two kinds of navigation are necessary: between models and between model elements. The next figure provides examples of the two underlying kinds of link.  
 
Considering inter-model navigabiliy, two kinds of navigation are necessary: between models and between model elements. The next figure provides examples of the two underlying kinds of link.  
  
[[Image:AM3UseCase-PetStore Navigability-ModelLinkOverview.png]]
+
[[Image:AM3UseCase-PetStore Navigability-ModelLinkOverview.png|center|frame|'''Navigation Between Software Development Models''']]
'''Navigation Between Software Development Models'''  
+
  
 
The '''model-level links''' (normal lines) are stored within the megamodel and are directly navigable.  
 
The '''model-level links''' (normal lines) are stored within the megamodel and are directly navigable.  
Line 24: Line 23:
 
The next figures provide two screenshots showing how AM3 is actually used in order to navigate at both model-level and model element-level.  
 
The next figures provide two screenshots showing how AM3 is actually used in order to navigate at both model-level and model element-level.  
  
[[Image:AM3UseCase-PetStore Navigability-ModelLevelNavigationView.png]]
+
[[Image:AM3UseCase-PetStore Navigability-ModelLevelNavigationView.png|center|frame|'''Model-level Navigation View''']]
'''Model-level Navigation View'''
+
  
[[Image:AM3UseCase-PetStore Navigability-ModelElementLevelNavigationView.png]]
+
[[Image:AM3UseCase-PetStore Navigability-ModelElementLevelNavigationView.png|center|frame|'''Model element-level Navigation View''']]
'''Model element-level Navigation View'''
+
  
 
== Documentation  ==
 
== Documentation  ==

Latest revision as of 10:26, 17 November 2010

< To: MDT
< To: MoDisco
Am3Logo.png

This AM3 use case titled Pet Store Navigability has been implemented by Guillaume Doux and initially published in May 2009.

Contents

[edit] Keywords

AM3, Global Model Management, Megamodeling, DSL, PetStore, Navigability

[edit] Overview

This complete use case presents a concrete use of the generic and extensible inter-model navigability facilities offered by AM3. It shows how a snapshot taken during a software development process can be represented by a megamodel and how global model management can be used to manage and navigate the different development artifacts. The sample application considered in this use case is the standard PetStore online application. The different models and metamodels available from this use case have been developed to figure out the situation at a given time within the software development process.

This use case is provided by INRIA AtlanMod and its development has been supported by the french IDM++ project (ANR-07-TLOG-IdM++) and by the IST European MODELPLEX project (MODELing solution for comPLEX software systems, FP6-IP 34081).

Considering inter-model navigabiliy, two kinds of navigation are necessary: between models and between model elements. The next figure provides examples of the two underlying kinds of link.

Navigation Between Software Development Models

The model-level links (normal lines) are stored within the megamodel and are directly navigable.

The model element-level links (dotted lines) are considered as a refinement of the model-level links and are stored in separate weaving models. A different weaving model is required for detailing each model-level link. The navigation of the model element-level links is realized thanks to the combined use of the megamodel and the corresponding weaving models.

The next figures provide two screenshots showing how AM3 is actually used in order to navigate at both model-level and model element-level.

Model-level Navigation View
Model element-level Navigation View

[edit] Documentation

[edit] Download