Meta data;;Pre-exercise assessment;;;;;;;;;;Exercise;;;;;;;;Post-exercise assessment;;;;;;;;;;;Calculated task scores (w/o not completed tasks);;; ID;Approach;Pre_EVL_Comprehensibility;Pre_EVL_Efficiency;Pre_EVL_Memorability;Pre_EVL_Satisfaction;Pre_EVL_Comments;Pre_PaMoMo_Comprehensibility;Pre_PaMoMo_Efficiency;Pre_PaMoMo_Memorability;Pre_PaMoMo_Satisfaction;Pre_PaMoMo_Comments;Exp_Task1_Time;Exp_Task2_Time;Exp_Task3_Time;Exp_Task4_Time;Exp_Task1_Score;Exp_Task2_Score;Exp_Task3_Score;Exp_Task4_Score;SUS_Question1;SUS_Question2;SUS_Question3;SUS_Question4;SUS_Question5;SUS_Question6;SUS_Question7;SUS_Question8;SUS_Question9;SUS_Question10;SUS_Comments;Exp_Task1_Score_Calc;Exp_Task2_Score_Calc;Exp_Task3_Score_Calc;Exp_Task4_Score_Calc P1;PaMoMo;3;4;2;3;- Easy to parse for a machine, difficult to comprehend for a human user (esp. with nested statements);4;3;4;4;"- Comprehensible for human user, parsable for a machine - Not sure about its ability to express complex consistency requirements - Can one constraint reference another?";02:25;04:55;07:25;04:45;100%;90%;37,50%;50%;4;2;4;2;4;1;4;1;4;2;#NAME?;100,00%;90,00%;37,50%;50,00% P2;PaMoMo;2;4;2;2;"- If you have no idea of OCL, it is really hard to define your constraints - Also think about sets, instances and the comparison with values";4;3;4;4;"- For huge constraints, where you need some extended conditions, you need OCL again - Otherwise easier to use since you just use the information of your metamodel";04:47;07:41;07:00;n/a;100%;70%;100%;0%;3;2;4;2;3;3;2;2;4;2;"- Hard if you do not know exactly your metamodels - Defining is quite easy inform of graphical blocks - More information about the difference between RefinesLink, EquivalentToLink, SatisfiesLink would be needed";100,00%;80,00%;100,00%;n/a P3;PaMoMo;4;3;2;3;"- It is a textual language - that might suit programmers very well - Also, it is easy to generate EVL code pieces for 3rd party software rather easy";5;4;5;4;"- As a graphical language, it is easy to comprehend patterns (read) - Writing patterns depends on the quality of the editor that is used - Harder to generate code snippets";04:30;05:08;06:00;n/a;100%;100%;75%;75%;5;1;5;2;4;2;5;1;5;2;"- Intuitive and easy-to-use approach - Of course, would be easier to use with graphical toolkit - For the given (toy) examples the approach is well-suited, but for more complex metamodels with different kinds of heterogeneities this approach might also be totally unusable";100,00%;100,00%;75,00%;n/a P4;PaMoMo;4;4;5;4;- Complex constraints get potentially hard to read, but it seems possible to create any constraint needed;5;3;3;4;"- Seems more intuitive for creating complex constraints - Wondering about the efficiency to create really complex constraints - maybe EVL is here a better fit (efficiency-wise) - Tooling available?";05:38;04:01;07:01;n/a;100,00%;50,00%;12,50%;25,00%;3;2;2;4;2;3;4;2;1;4;"- Correcting or spotting errors was hard for me (partly due to the time constraint) - It felt not very intuitive to me, but I like the general idea";100,00%;50,00%;12,50%;n/a E1;EVL;3;2;4;3;;2;4;4;4;;15:50;n/a;06:00;n/a;80,00%;0,00%;0,00%;0,00%;3;2;2;2;4;3;2;3;3;3;;80,00%;n/a;0,00%;n/a E2;EVL;2;2;3;3;"- Pro: textual language seems more powerful, more expressive - Pro: Computer scientists are used to textual languages - Con: Seems complicated compared to PaMoMo";4;4;4;4;"- Pro: Seems easier for non-computer scientists - Pro. Good overview, easy to grab";09:15;n/a;06:42;n/a;80,00%;0,00%;0,00%;0,00%;1;4;2;2;4;3;2;4;1;4;#NAME?;80,00%;n/a;0,00%;n/a E3;EVL;2;2;3;2;;4;5;4;4;;06:20;10:24;07:46;n/a;100,00%;80,00%;25,00%;25,00%;2;4;1;2;1;2;2;4;3;2;- The choice of the not domain specific link metamodel (i.e., no type constraints for the link) makes the approach much harder to use;100,00%;80,00%;25,00%;n/a E4;EVL;2;5;2;3;;4;3;5;4;;n/a;n/a;n/a;n/a;0,00%;0,00%;25,00%;25,00%;3;4;2;5;5;3;3;4;1;5;#NAME?;n/a;n/a;n/a;n/a