The goal of this assignment is to build a formalism to model RPGGames in AToMPM:

1. Implement abstract syntax using SimpleClassDiagram, enrich with global constraints if necessary, create a concrete syntax (using the ConcreteSyntax formalism), and generate a modelling environment (by compiling the metamodel and the concrete syntax model). Do this incrementally.
2. Make your RPGame visually more appealing by adding actions that move/resize/... model elements. Find useful constraints. To implement this, you'll need to make use of the mappers and parsers in the concrete syntax of your formalism.
3. Create test models that demonstrate the use of your language.
4. Optional: Create multiple concrete syntaxes for your formalism.

Write a report that discusses your solution. Your report should include an overview of your solution, with focus on the difficulties you encountered and how you solved them.

You will have to complete this assignment in groups of 2. Submit your assignment (report in PDF + zip file containing your formalism and example models) on Blackboard before Tuesday 28 October 2014 at 23:59.

Contact Simon Van Mierlo if you have a problem.

Required

Syntax and Static Semantics

1. An RPGGame consists of exactly one scene (or "level"). The scene has a name, such as Forest, Desert, Castle, etc.
2. In each scene, there are a number of connected tiles.
3. Tiles can be connected to each other from the left, right, top or bottom. This way, a map is created for the scene.
4. If a tile has a left neighbor, that neighbor should have the tile as its right neighbor, and vice versa. If a tile has a top neighbor, that neighbor should have the tile as its bottom neighbor, and vice versa.
5. In the game, there is one character: the hero. The hero is always on exactly one tile.
6. A tile can be an empty tile, or an obstacle, on which no character can stand.
7. On a "standard" tile (not an obstacle), there can be an item.
8. There is one type of item: the goal. There must be at least one goal in the game.

Optional

Syntax and Static Semantics

1. An RPGame now consists of a world that is divided into a number of scenes.
2. There is a new type of character: the villain.
3. There are two new types of tiles: a trap, and a door.
4. A door is a portal to a door on another scene.
5. The hero and a villain have a health value that depicts how much damage they can take. The default health for the hero and for a villain is 100 (although it can be set otherwise). The health always has a strictly positive value.
6. The hero, a villain, and a trap have a damage value that depicts how much damage they inflict. Damage is always strictly positive.
7. There are two new types of items: a key, and a weapon. A weapon has a strictly positive damage value.

• AToMPM main page: http://www-ens.iro.umontreal.ca/~syriani/atompm/atompm.htm
• AToMPM user manual: atompm_manual.pdf.
• AToMPM Download Link (v 0.5.3): http://www-ens.iro.umontreal.ca/~syriani/atompm/atompm.htm#dev. To install AToMPM, follow the instructions on the webpage.
• Node modules: download.
• Useful tutorials can be found on the 'Tutorials & Demos' page on the main website.

• Primitive Types: int/float/boolean/string
• Composite Types: [] for lists, {} for dictionaries
• Cardinalities are specified by the construct: map<[dir,type,min,max],[string,string,string,string]>. 'dir' is either 'in' or 'out', 'type' is the type name of the association, 'min' is the lower bound, and 'max', is the upper bound. An example: {'dir': 'in', type: 'A2B', 'min': '0', 'max': '1'} defined on class B means that an instance of B can be connected to 0 or 1 A's with the relation A2B.
• To get connected neighbors, use the 'getNeighbors' function. The signature of this function is: getNeighbors(_dir [, type, _id]) where '_dir' is either '>' (outgoing) or '<' (incoming), '_type' is an optional type name of the association (use '*' to match all relations), and '_id' is an optional model element id (if none is given, it takes the current model element). Connected neighbors include both associations and objects. For example, if an instance of class A is connected to an instance of class B with the association A2B, a getNeighbors call on the instance of class A will return the instance of the association A2B.
• Actions and Constraints are written in JavaScript. Actions and Constraints consisting of multiple lines need to have each line ending with '\'.
• When saving a model, you can create a new folder (in this example, 'test') by specifying 'test/mymodel.model' as the filename.
• When using getNeighbors, you need to pass three parameters: direction ('<' or '>'), type, and the id of the node you want to get the neighbors of. However, you should always use '*' for the type, which gets all the neighbor id's. Then you can check the type of each association by getting the '$type' attribute (a regular string) using getAttr().