refs 3020

added new constraints as per Hernan's suggestions... Also changed the text/description of the constraints to be coherent.. extended the mira.ecore to have new constraints implemented. Added new constraints are 1) CheckListReviewConstraint (to check if the checklist attached with every requirement), 2) RequirementExistsConstraint (to check if the Requirement Package has the requirement) and 3) ComponentExistsConstraint (to check if the Component Architecture has components available).

refs 2978

use "->" and "<->" respectively
refs 3025

refs 2978

refs 2978

refs 2978

refs 2978

refs 2978

ICommandStackService.getInstance().runAsCommand(project, () -> {
			dd = findDataDictionary(project, "Data Dictionary");
		});

refs 2978

refs 2756

refs 2756

refs 2756

refs 2756

refs 2756

refs 2413

refs 2413

refs 2413

- Model change listner still needed
refs 3035

  - It can be used to specify that for a particular model element no editor is available.
  - This avoids that ModelEditorBindingService further walks up the model hierarchy to look for an editor that is registered for one of the ancestors. Currently, this had the the effect that for a model element without explicit editor, the project configuration editor (that is registered for the root element "FileProject") has been opened

Use the the new ModelEditorNotAvailableBinding mechanism for the following model elements
  - SystemSchedule
  - AllocationTableCollection
  - SafetyArgumentationPackage
refs 3048

refs 3068

refs 3068

refs 3006

- Move the registration of the following annotations from org.fortiss.af3.exploration to org.fortiss.af3.exploration.smt:
  - MemoryPerNodeProvider
  - HardwareCostValueProvider
  - PowerConsumptionValueProvider
  - SafetyIntegrityValueprovider (achievable SIL: Registrations for ExecutionUnit and TransmissionUnit)

refs 3069

refs 2899

refs 2988

refs 2988

refs 2978

refs 3049

refs 2478

refs 2478