p { margin-bottom: 0.1in; line-height: 120%; }
SysML is a subset and extension of UML, and I think providing a means to do text based modeling of SysML would also be very powerful.
From a high level, there are changes to the diagrams, including adding additional diagrams:
1. Requirements Diagram
2. Parametric Diagram
Structure: Object, Profile, Deployment, and Component diagrams are removed.
Behavior: Communication, Interaction Overview, and Timing diagrams are removed. Protocol state machines are removed (behavior state machines remain).
Here is what I think the priority of the changes would be:
High Priority Changes:
-
Blocks (Class)
-
Block Definition Diagram (Class Diagram)
-
No arrowheads on both ends (associations have no arrowheads)
-
Internal Block Diagram
-
4 properties of Blocks, but only parts, references are high priority
-
Proxy ports and flow specifications
-
Requirement (Class) and Requirement Diagram
-
DeriveReqt, Verify, Satisfy (Trace)
Medium Priority Changes:
-
Blocks – value properties and constraint properties
-
Allocation
Low Priority Changes:
-
Parametric Diagram
-
Model Elements support
-
Conform (dependency)
-
View (package)
-
Viewpoint (Class)
-
Rationale and Problem (Comments)
-
ValueType
-
QuantityKind / Unit
-
Blocks – value properties and constraint properties
-
Activity extensions
-
Control as Data
-
Continuous Systems
-
Probability
-
Copy (Trace)
-
Constraint Blocks
If this request is aligned with the vision of modeling languages that PlantUML would support, I would be willing to help volunteer to lead this effort.