Requirements

The following requirements are should be fulfilled by the graphical editing frameworks.

Elements (E):

1. Classes with name, attributes and methods
2. Groups with name, groups can be nested
3. Relations / Associations with 3 labels in different styles
4. Relations should support layered styles
5. Configuration editor (with validity verification)

Functional (F):

1. Step into groups (in the same editor and maybe open in new editor)
2. Adaptable edit policies to disable some features (e.g. creating a relation between two classes)
3. Relations between relations
4. Toolkit palette view (changeable)
5. Configuration context menu (rightclick, context buttons, etc.)
6. Support Undo and Redo of editor actions

Non-Functional (N):

1. Framework provides a stable API (avoid breaking changes)
2. Framework will be supported for around 5 years
3. Framework is open-source and licensed to use for research and teaching
4. Framework should support modular definition of language features

---

Extended (X):

1. Req. [F1] -> should also support a flat representation
2. Views on parts of the model
3. A switch for a specific feature/toolkit set when creating a new model
4. File handling: save, load, import, export, CROM export, PDF export (with model info)
5. Model templates (kinda like ".potx" for MS presentations)
6. IDE comfort features support (highlighting of paths/types/errors, missing parts, auto completion, ...)
7. General usability (accounts, cloud storage, ...)