Validation rules after Component/Actor refactoring

Update existing rule dealing with Components/Actors
Add new rules to cover the cases below:

rule#1: A Component or Actor “is Human” true cannot have sub components nor sub Actors (only deployments of component/actors is allowed, getContainedParts shall be empty, managing sub packages too) rule#2: Only root Actors (inside structure) can be kind UNSET (actors contained into another actor/component cannot be unset) rule#3: Add WARNING for Actor and physical component UNSET (except root component (always UNSET)) and provide a switch (QF multiple) to move towards Behavior or Node: e.g. "Switch to Behavior if possible", if possible because the switch depends on the parent or deployment rules (with messages to understand why the switch cannot be done, due to parent or deployment nature of other component/actor "Totot" & QF navigation towards this related model element) rule#4: Only Actor UNSET can deploy both components/actors kind Node or Behavior, otherwise check consistency like any other components. o Node Components (actor or not) can contain Node and deploy Node or Behavior o Behavior Components (actor or not) can contain Behavior and deploy behavior rule#5: Op Entity: isActor = false and isHuman = false, detect other cases and add switch QF rule#6: On SystemAnalysis level o System cannot contains any component/actor rule#7: On SA/LA/PA o Only one component isActor=false shall be contained in the root structure pkg (directly or recursively by owned structure pkgs (components contained into a component are allowed) ) o root Physical component UNSET

🆔 ECLIPSE-554465 / POLARSYS-2582 👷 georgiana.ecobici 📅 2019-09-04 🔎 1.4.0

eclipse-capella / capella

Validation rules after Component/Actor refactoring #945