Stay in the loop

What is your occupation?

How much experience do you have with Model-Driven Engineering (MDE)?

How much experience do you have with graph transformation (GT)?

How much experience do you have with Eclipse as an IDE?

How much programming experience do you have?

How much experience do you have with visual (programming) languages?

Is the textual syntax of the pattern language easily understandable?

What do you particularly like/dislike about the textual syntax? How would you change/improve it?

How helpful is the visualisation when defining complex patterns?

How disturbing is it that the visualisation is read-only?

What do you particularly like/dislike about the visual syntax? How would you change/improve it?

Do you like the combined mix of textual and visual syntax?

What do you particularly like/dislike about the combined mix of textual and visual syntax? What would you improve?

How helpful are the error/warning messages if the textual specification contains errors?

Are you satisfied with the usability of the textual editor?

How can we improve the textual editor?

How useful is the JavaDoc (and the choice of method names) of the generated API?

Was switching between .gt files and the Java code that makes use of patterns/rules a seamless experience?

How can we further improve the integration with Java?

Will you consider using eMoflon::IBeX-GT in a future Java project?

If you would choose to use eMoflon::IBeX-GT instead of Java for a particular programming task, what do you think would be the main reason for doing so?

If you would choose NOT to use eMoflon::IBeX-GT instead of Java, what do you think would be the primary reason?

Do you think the pattern language is expressive enough to specify patterns of realistic complexity in practice?

How important are the following language features for you? [Attribute constraints and assignments]

How important are the following language features for you? [Pattern/rule reuse via refinement]

How important are the following language features for you? [(Negative) application conditions]

How important are the following language features for you? [Complex graph conditions (||, &&)]

How important are the following language features for you? [Support for reactive programming (subscription methods to appearing and disappearing matches)]

Do you think an important language feature is missing? Tell us what you would like to have.

Did you enjoy working through the handbook?

What exactly did you like (most)?

What was not so good? How can we improve the handbook?

How was the level of difficulty of the handbook?

How useful do you find the appendix at the end of the handbook?

How else should we document eMoflon::IBeX-GT?

2018/05/14 3:17:43 PM MEZ

the visualization is not editable.

Can not debug the project in eMoflon::IBeX-GT and and less documentation available in internet.

Extremely important

Very important

Extremely important

manual was excellent even for a layman.

some small mistakes in the screenshot.

2018/05/14 3:23:06 PM MEZ

White text on black boxes is not easily readable (especially if there is a lot of light in the background)

Make it possible to directly navigate to the patterns/rules from the code

Using patterns is closer to the underlying model, easier to adapt to changes, less error-prone and much less work than hard-coding the operations on the EMF model

Using a different programming language

Very important

Not so important

Extremely important

Detailed descriptions

Easy to skip an paragraph, and keep wondering why something is missing

Provide more examples where you showcase more features (so one can see the functionality described in the appendix in action)

2018/05/14 3:44:08 PM MEZ

The block structure is really easy to understand, arrows are also some kind of visualized by -->.

I like the simplicity of the syntax, i.e. that you can map each textual element to concrete element of the visual syntax. Improvements: Overlapping is sometimes a difficult problem.

Textual syntax ensures precision, while visual syntax supports understandability.

Sometimes, updates are not propagated, such that you have to refresh manually frequently.

I don't know, it's a challenging task indeed.

Coding effort is reduced, nice visualization.

I'm not that used to the syntax yet, you have to specifiy (meta) models in advance.

Not so important

Extremely important

Extremely important

Good screenshots, understandable guidelines, interesting additional information.

Pay attention that it remains well-structured when extending it"!

It's well-documented!

2018/05/14 3:47:33 PM MEZ

babri@mail.uni-paderborn.de

NACs not explicitly as conditions but instead directly something like !occupiedNext in the "when" clause

Mark condition directly as NAC via e.g. "N" in top left instead of own box with "forbid .."

If a rule is refined it would be nice so highlight the refined part somehow

Lot of copy paste for similar rules (up, left, right, down,...) - but currently no idea how to improve Navigation back from Java to .gt file

Visualization not only IT experts understand

Very important

Extremely important

Very important

Handbook 2: First following the handbook then creating own rules

First handbook no really task without copy paste in the end

2018/05/14 3:57:21 PM MEZ

Very important

Very important

Extremely important

Very important

2018/05/16 12:52:46 PM MEZ

Student (BSc or BEng)

improvement in code-completion

Very important

Very important

to see the practical usage

implementing the java classes without help might be too difficult

2018/06/04 6:05:48 PM MEZ

the ++ and -- is intuitive, and there are no unnecessary chars like "

it would be great to toggle c´class attributes

for complex rules

it is only available in Java, but I use java rarely

Very important

Extremely important

Extremely important

Extremely important

the pictures and the plain language

the syntax should describes not at the end...

when you make updates

2018/06/06 10:21:54 AM MEZ

Student (BSc or BEng)

Not so important

2018/06/06 10:24:11 AM MEZ

Student (BSc or BEng)

Not so important

Not so important

2018/06/06 10:24:41 AM MEZ

Student (BSc or BEng)

easy to understand and write down

see both parts so it is easier

Very important

Very important

2018/06/06 10:24:50 AM MEZ

Student (BSc or BEng)

It is short, so you do not have a big overhead

You get feedback directly. Maybe rearranging with the mouse would be helpfull to get a better overview of complex models.

The direct feedback is very helpfull to understand the textual syntax.

Very important

The handbook offers the possibility of just copy and paste. So you are able to do the whole handbook without understanding anything.

2018/06/06 10:25:15 AM MEZ

Very important

2018/06/06 10:25:41 AM MEZ

Student (BSc or BEng)

in dirty code it is not clear which pattern a keyword like "when" belongs to

Not so important

Extremely important

Extremely important

2018/06/06 10:26:03 AM MEZ

p_bala@me.com

Student (BSc or BEng)

I can verify my textual input with the visual output

Very important

2018/06/06 10:27:23 AM MEZ

Student (BSc or BEng)

Very important

2018/06/06 10:28:20 AM MEZ

Student (BSc or BEng)

Through the combining you can understandthe textual syntax very fast

big project, good overview with eMoflon::IBeX-GT

Little projects, much easier and faster without eMoflon::IBeX-GT

Very important

Not so important

Extremely important

2018/06/06 10:29:03 AM MEZ

Student (BSc or BEng)

Not so important

2018/06/06 10:29:55 AM MEZ

90martinis@gmail.com

Setting edges and cardinalities would be a major relief.

Mainly because I am not a Java developer/I have not Java projects on hand.

Very important

Very important

Even though I was running Eclipse on Linux everything worked as described in the handbook. An experience I never had before at University since most of these handbooks are written very sloppy. Yours was really good. It actually was fun working through.

Sometimes some verbalizations were not exactly distinct, so I had to read some paragraphs about 2-3 times.

2018/06/06 10:33:25 AM MEZ

kbiermeier1@web.de

Student (BSc or BEng)

I like that arrows are used to declare Edges/(relationship). Its easy to understand.

That they also visualize the ingeritance completly

I would like to manipulate zur visualization

Very important

Very important

Very important

Not so important

If not then do would be really helpful

Referenz manual

2018/06/06 10:34:55 AM MEZ

dirk.leffrang@gmail.com

Visual syntax should always be editable

If there are plenty of ways to manipulate a visual syntax, a textual syntax is more easy to manipulate.

Show more exact where the error occured.

Finding the files which belong together is quite difficult if you're not used to it. A shortcut/ direct link / button would be awesome.

Because the visualisation is quite good.

The Graphs in PlantUML are not editable. I don't think that a person without programming experience could handle the programm, as it's still very IT specific.

Very important

Not so important

I think more drag and drop/ click tools would be expected like in Jimdoo, etc. . Maybe even natural language processing. Additionally a GUI/ Webapplication would be amazing so that you always see visually what you're doing. Manipulations in the graph would also be a nice feature.

Using the theoretical concepts in practice.

Maybe highlight installation tools more, like plantUML (maybe show a Screenshot)

2018/06/19 2:54:32 PM MEZ

Student (BSc or BEng)

Needs more documentation

Linking the visual with the textual syntax, when you click on the visual

Very important

Very important

Mention the Appendix much earlier, so people won't miss it out in the future

2019/01/30 2:20:03 PM MEZ

Student (BSc or BEng)

2019/01/30 2:23:20 PM MEZ

Student (BSc or BEng)

Throw Eclipse away

Not so important

2019/01/30 2:23:36 PM MEZ

Student (BSc or BEng)

It is bound to eclipse. And eclipse would not be the first choice when selecting the IDE.

Extremely important

Very important

Very important

It could use some more description of what is actually happening. Sometimes you have the feeling of "Why did we just do that?" or "Ok i did this. But why? And what was it good for?"

2019/01/30 2:23:46 PM MEZ

Student (BSc or BEng)

Very important

Not so important

Very important

2019/01/30 2:28:03 PM MEZ

Student (BSc or BEng)

structural hindrances. cross references with cycles

Very important

Not so important

Extremely important

create a dictionary of language features. not only examples. show me everything i can specify. every option, operator etc. not forcing me to use it all, but to have a wiki like thing to take to if i need assistance

2019/01/30 2:30:40 PM MEZ

Student (BSc or BEng)

Basic editorial features

Nice to follow thru

Sometimes steps were not enough described

2019/01/30 2:32:16 PM MEZ

Student (BSc or BEng)

Extremely important

2019/01/30 2:35:14 PM MEZ

Student (BSc or BEng)

Läuft nicht stabil genug. Erkennt Fehler wo keine sind

Stabilerer Aufbau, weniger "Abstürze"... weniger resourcenfressend

Wenn ich es mir unnötig kompliziert machen möchte

Viel zu unausgereift und instabil

Es wird erst Zeilen später erklärt, was zu tun ist falls ein Fehler auftritt etc.

2019/01/30 2:35:15 PM MEZ

Student (BSc or BEng)

I understand java better than eMoflon.

Not so important

Very important

Extremely important

Extremely important

2019/01/30 2:35:54 PM MEZ

Student (BSc or BEng)

Color highlighting is nice

Visual syntax is easy to read, textual syntax is easy to edit

Add more information to the code completion proposals, especially for enum values (it was really hard to find)

The ability to easily load, save and modify models conforming to a well-defined metamodel

Small size of the project or not very compatible domain

Extremely important

Extremely important

Extremely important

Easy to understand and small enough steps, ability to experiment with the presented feautures on my own

Add some more complete documentation of the discussed features in the end (or at least a link)

Maybe using some dedicated documentation tool, e.g. ReadTheDocs

2019/01/30 2:36:50 PM MEZ

Student (BSc or BEng)

Gives a good overview of where I am/ What I am currently doing.

I I get the chance of doing so and I remember it. eMoflon could help when modelling something.

I don't remember it or I am forced to use Java.

Very important

Very important

Very important

Comment feature, really good.

Problems with Java/Eclipse. Some text was kind of dense, so some rare passages I had to read multiple times.

2019/01/30 2:37:19 PM MEZ

Student (BSc or BEng)

Not so important

Very important

Not so important

it gives not enough information for the projects

2019/01/30 2:38:02 PM MEZ

Student (BSc or BEng)

sometimes the placement of elements is really strange, but thats the only issue in my opinion

its good to get another view on the things you wrote before. Its easier to find mistakes when looking at the same thing in a different way. I would like to see on the visual side, which component/rule I am editing right now. It was sometimes confusing, and we thought we saw a different rule as it really was

i had to use eclipse, maybe i would use it if there were a more stable ide for

Extremely important

Very important

Very important

Not so important

more things you can look up, when having problems. Solutions or solution ideas for different Problems/Situations/Programming styles as described in the handbooks

2019/01/30 2:39:57 PM MEZ

IDE frisst sehr viel Leistung und bleibt oft hängen

Wenn ich mehr Arbeitsaufwand haben möchte

Strukturierte Programmierung mit guter Dokumentation ist deutlich übersichtlicher

Extremely important

Extremely important

Very important

Sehr unverständlich, stellt keinen Gesamtzusammenhang her

2019/01/30 2:41:01 PM MEZ

martenls@mail.uni-paderborn.de

Student (BSc or BEng)

More documentation/tutorials on what does what and how the different Projects(Patterns, Transformation, Xtext) can be integrated and combined

Very important

Very important

2019/01/30 2:41:32 PM MEZ

Student (BSc or BEng)

Es ist nervig, dass die Graphen immer unterschiedlich aussehen.

Not so important

2019/01/30 2:41:54 PM MEZ

Student (BSc or BEng)

changing the order/position of nodes would be helpful but is not at all necessary

Very important

Not so important

Adapting what was introduced in the handbook to own projects was difficult at parts because it might have been too specific

2019/01/30 2:53:44 PM MEZ

Student (BSc or BEng)

Very important

Very important

Very important

2019/01/30 2:56:59 PM MEZ

Student (BSc or BEng)

For me as a programmer it is just code with more restrictions

It is very difficult to gain an overview over large Models but I do not think there is a easy solution to this problem

The generated code is extremly blown up and it is very annoying to handle multiple projects at once. I prefer having one project where I can write my own code and all other projects are just libraries.

Blown up projects, bugs and issues with eclipse, too many restrictions with pattern-matcher and transformations, weird errors and warnings, I don't know enough about eMoflon::IBeX-GT to use it without running into problems.

Extremely important

Extremely important

Extremely important

Extremely important

Most of the time was spend reading through it and trough it again and try to understand what we want to achieve and how to do it and in the end it was just frustrated copy & pasting.

Visual Languages

Textual Syntax

Mix of textual and visual syntax

Error Messages

Usability in general

Switching: Java / gt files

Expressiveness

Application Conditions

Complex Conditions

Incrementality

Understandability

Not so important

Very important

Extremely important