Downselecting a modeling language

[capsulecorplab]

In order to document the flight software architecture using a model-based approach, we need to down-select a modeling language to support tasks, s.a., #2, #3, #9, & #11. The following is a trade-study of available modeling languages that support architecture modeling

Criteria	SysML v1	SysML v2	PlantUML	M30ML
Extensible ontology language	x	x	x	x
Supports both textual & graphical view generation		x		x
Lightweight textual syntax		x	x	x
Relatively minimal overhead with modern doctools			x	x
Supports execution semantics		x

[capsulecorplab]

Leaning toward M30ML for architecture modeling, as it is currently the path of least resistance. This will also allow for easier integration with packaging the flight software as a dof Component for modeling CubeSat components, interfaces, & functions - since dof already includes a data structure definition for a Component, with plans to include Interface & Function

[Robb1994]

I agree with Sean, it looks like M30ML is a good choice moving forward.

[capsulecorplab]

As per July 28th FSW meeting, we'll downselect m30ml for architecture modeling needs for now. Will likely want to visit SysML v2 for a future release