Replies: 1 comment 1 reply
-
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
SAF makes the approach to structure MBSE work in to plannable parts - the Viewpoints.
We have reasoning why a viewpoint should be used (the concerns) and this can be used to plan the MBSE effort.
The information "which viewpoints to model" is currently not captured in the model, we don't have a viewpoint for this. The VP should capture which viewpoints to model, and also an estimate about the amount of model elements. E.g. for the System Usecase VP an estimate about the number of unique System Use Cases, and unique System Context Elements could be recorded.
For users, it might be also helpful, if the "way through the viewpoints" could be specified. We don't have a viewpoint for this, either.
Of course the actual content in a project is dependent from the "Engineering Story" of the project.
See Bärentango for one of the engineering stories we told at TdSE.
Perhaps it would be a good idea to support closing this open loop, i.e. by enabling SAF users to measure, if things are going along the plan.
IMO, that would mean to
This is not an elaborated concept- but i want to trigger the discussion.
What do you think ?
What are your experiences with model metrics, what did work, what didn't?
Please contribute to this metrics discussion, @GfSE/saf !
Beta Was this translation helpful? Give feedback.
All reactions