The file models/SE_Models/EIT_System_Use_Cases.sysml uses UML use case diagram constructs that aren't part of the SysML v2 textual notation:
// These constructs are not valid SysML v2:
actor Doctor;
usecase ApplyElectrodeBelt;
association ApplyElectrodeBeltAssoc {
memberEnd actor: EngineerTechnician;
memberEnd usecase: ApplyElectrodeBelt;
}
boundary EITSystemBoundary {
include ApplyElectrodeBelt;
// ...
}
These cause parse errors in SysML v2 parsers (I'm working on a tree-sitter-sysml right now). This was found as I was creating a training/validation corpus.
SysML v2 Equivalent
The SysML v2 approach to use cases would be:
package EIT_System_Use_Cases {
// Actors as part definitions
part def Doctor;
part def EngineerTechnician;
part def Patient;
part def EITSystem;
// Use cases
use case def ApplyElectrodeBelt;
use case def StartMonitoring;
use case def CollectImpedanceData;
// ...
// Actor-UseCase relationships via subject/actor
use case applyBelt : ApplyElectrodeBelt {
actor technician : EngineerTechnician;
}
// System boundary as a package or part containing use cases
part eitSystemBoundary : EITSystem {
perform applyBelt;
// ...
}
}
Would you like this file updated to valid SysML v2 syntax, or is this intentionally a UML-style example for educational comparison?
The file
models/SE_Models/EIT_System_Use_Cases.sysmluses UML use case diagram constructs that aren't part of the SysML v2 textual notation:These cause parse errors in SysML v2 parsers (I'm working on a tree-sitter-sysml right now). This was found as I was creating a training/validation corpus.
SysML v2 Equivalent
The SysML v2 approach to use cases would be:
Would you like this file updated to valid SysML v2 syntax, or is this intentionally a UML-style example for educational comparison?