Profile contract
sysml.requirements@1
SysML 1.6 requirements diagram: requirements with id/text compartments, test cases, «deriveReqt»/«satisfy»/«verify»/«refine»/«trace»/«copy»/«master» dependencies, composition containment.
graph projectionSysML requirements diagram
Open this profile in the gallery
Primary palette
Additional context roles
Relationship roles
Legal endpoints
| Relation | Source roles | Target roles | Self relation |
|---|---|---|---|
sysml.allocate | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
sysml.composition | req.requirement, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.valuetype | req.requirement, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.valuetype | Not allowed |
sysml.copy | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
sysml.derive | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
sysml.flow | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
sysml.master | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
sysml.refine | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
sysml.satisfy | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
sysml.trace | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
sysml.verify | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | req.implementation, req.requirement, req.test, sysml.block, sysml.constraint, sysml.flowspec, sysml.interfaceblock, sysml.testcase, sysml.valuetype | Not allowed |
uml.generalization | sysml.block, sysml.interfaceblock, sysml.valuetype | sysml.block, sysml.interfaceblock, sysml.valuetype | Not allowed |
Profile verification
- Use nonempty unique requirement codes and text, plus the registered SysML dependency directions.
- Verify originates from a permitted test role; satisfy originates from a permitted implementation role; copy/master/derive retain distinct meanings.
- Traceability is not formal requirement proof.
Profile defaults
Explicit file settings override eligible CSS, then these profile defaults and the common standard apply. Unspecified semantic facts remain unspecified.
{
"projection.kind": "graph",
"projection.profile": "sysml.requirements@1"
}Projection properties
kind, profile, inputs, analysis_budget, traces, iso, depth
Design operations
- Create requirement or test/implementation context; edit code/text; draw the selected dependency role.
Bounded analysis
Structural verification and display only; no execution or implied process engine.
Outside this profile
- SysML XMI interchange
- SysML 2.0 deferred to a future profile family
- requirement formal verification
- formal OMG certification