extended the ExternalRelationSpecification with additional attribute "requirementImplementedCorrectly". It is to capture as a checkbox option if all the ITraceableArifacts implement the requirement.

refs 3075

refs 3075

"org.fortiss.af3.mira.verification.RequirementTraceAnalyzedChecker">
"org.fortiss.af3.mira.verification.RequirementTraceEmptyFieldChecker">
from the Constraint checker

They need to be re implemented to be similar to the others

refs 3039

refs 3039

refs 3026

refs 2413

refs 3025

refs 2413

refs 3074

- RED: Keep commented workaround to render resource schedules with null-hyperperiod (to be removed after summer school)

updated the constraints error description, fixed the null pointer error caused because of the name of the requirement and for the "multipleAspectsConstraint" constraints providing two kinds of fixes. 1) if the requirement has no aspect applied than provide an error that add one aspect (information only) and 2) if there are more than one aspect than provide the split fix to the user

refs 3020

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