Integrating SysML Tools with Requirements and Configuration Management
Domain 3 covers integration of SysML tools with requirements management (RM) and configuration management (CM) tools. The exam tests data ownership, stable identifiers, and lifecycle links rather than button locations.
Requirements integration
RM tools such as DOORS, DOORS Next, Polarion, and Jama hold authoritative requirement text and attributes. SysML requirement elements can mirror them, but duplication must be controlled. ReqIF, the OMG Requirements Interchange Format, exchanges requirements, attributes, and links with stable IDs. OSLC provides RESTful links between a SysML element and a requirement URL, enabling traceability without copying text. Map SysML «satisfy», «deriveReqt», «verify», «refine», and «trace» to the RM tool's link types; agree which side owns each attribute.
Configuration management integration
Models are graphs, not just files. CM must version elements and relationships, create baselines that include model, profiles, libraries, and external links, and support change sets and variants. XMI is an interchange format, not a complete CM solution. Tool APIs or OSLC configuration management can align model baselines with requirement baselines.
Worked example
Requirement REQ-101 changes from 10 Hz to 20 Hz. An OSLC link from block Camera to REQ-101 supports impact analysis; the model's «satisfy» link is not a copy of the text. Update the block's performance constraint, run validation, and baseline the model plus the REQ-101 set together. Reasoning: a stable ID and link preserve traceability; no text duplication; the baseline captures both sides.
Traps
Linking by requirement name rather than ID; ReqIF round-trip overwriting local attributes; treating XMI export as configuration management; baselining diagrams only; losing links when elements are refactored; assuming OSLC links are versioned automatically.