User Tools

Site Tools


issue

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
issue [2013/04/05 12:09]
arnaud removed
issue [2013/05/24 15:58] (current)
arnaud
Line 1: Line 1:
 +====== The test suite shall cover instantiation semantics ======
  
 +  * A preliminary test suite for automatic instantiation of composite structures is available.
 +  * It is used to validate the instantiation semantics covered by the CS_DefaultConstructionStrategy.
 +  * It contains both structure and behaviors, and it executes successfully (No asserts fail)
 +  * It covers instantiation of composite structures in the following cases:
 +    * Instantiation of values for ports and parts
 +    * Instantiation of links for binary, assembly/​delegation,​ typed connectors, expressed between parts/​parts,​ parts/​partwithports,​ partwithports/​partwithports,​ port/parts, parts/​partwithports
 +    * Instantiation of topologies of values and links which accounts for lower bound multiplicities of ports, parts and connectorEnds (resulting in Empty topologies, Unconnected topologies, Array topologies or Star topologies)
 +    * Instantiation of default values (supports fUML ValueSpecifications,​ + OpaqueExpressions with a behavior)
 +    * Addresses instantiation with multiple levels of hierarchy
  
-  * Prototype implementation available +  * TODOS
-  * Based on an extension of CallOperationActionAction::doAction, and introduction of a new semantic strategy: CS_ConstructStrategy +    Review ​the assertions to make sure they are valid / sufficient 
-  Using this prototype implementation, ​the Test Suite for instantiation of composite structures passes +    * Cover typed/n-ary connectors 
- +    Cover untyped binary connectors 
-  Issues: +    * Cover ports typed by interfaces 
-    * How to properly determine that an operation is a <<​create>>​ operation? +    Cover structures with inifine depth (e.gis composed of a : A [1] => make sure that it is detected and that parts are not infinitely instantiated)
-      Currentlythe solution ​is implementation specific (Eclipse UML2) +
- +
-  * TODOs: +
-    * +
issue.1365163743.txt.gz · Last modified: 2013/04/05 12:09 by arnaud