Wednesday 27 July 2022

V4.1.a.Rhp831.PreRelease (27-JUL-2022) - First version with business value profile (target for visio import)

First version with business value profile (target for visio import) plus some important tables views for showing traceability in the requirements, use case and feature function packages.

This is on Github here

V4.1.a.Rhp831.PreRelease (27-JUL-2022):

#533 17-JUL-2022: BusinessValue: Initial implementation of base Business Value profile utilizing the SysMLHelper metamodeling framework (F.J.Chadburn)

#534 17-JUL-2022: BusinessValue: Initial business value diagram strawman implementation (F.J.Chadburn)

#535 18-JUL-2022: BusinessValue: Tweaks to compartments and icons as a result of Visio import testing (F.J.Chadburn)

#536 18-JUL-2022: BusinessValue: Widen business value package to include queries, table views/layouts and matrix views/layouts {F.J.Chadburn)

#537 19-JUL-2022: BusinessValue: Differentiate Tier1, Tier2 and Tier3 goals with different colour icons {F.J.Chadburn)

#538 20-JUL-2022: ExecutableMBSE: Allow context diagram flows table to be scoped under signals package for better model segregation (F.J.Chadburn)

#539 20-JUL-2022: ExecutableMBSE: Fix the default prefix for simple requirement table rename in listerner to table view rather than tablel (F.J.Chadburn)

#540 21-JUL-2022: ExecutableMBSE: Added RequirementToFunctionBlockTable to right-click menu for requirements packages to enable coverage gaps to be identified (F.J.Chadburn)

#541 21-JUL-2022: ExecutableMBSE: Get listener to auto-set the initial scope for RequirementToFunctionBlockTable if owned by requirements package (F.J.Chadburn)

#542 22-JUL-2022: ExecutableMBSE: Automate steps in method to create a feature function package from right-clicking a use case (F.J.Chadburn)

#543 22-JUL-2022: ExecutableMBSE: Get function block creator on a right-click of requirement to use the requirement name rather than the text (F.J.Chadburn)

#544 26-JUL-2022: ExecutableMBSE: Allow flow input and flow output tools in the ibd - system diagram to ease subsystem to function wiring workflow (F.J.Chadburn)

#545 27-JUL-2022: ExecutableMBSE: Revert menus to standard rather than new term timing diagrams whilst toolbar issue for condition mark is resolved (F.J.Chadburn)

#546 27-JUL-2022: ExecutableMBSE: Allow timing diagram on system architecture/subsystem packages in addition to feature function package (F.J.Chadburn)

Tuesday 12 July 2022

V4.0.x.Rhp831.PreRelease (12-JUL-2022) - Miscellaneous tweaks and improvements added during training development

V4.0.x.Rhp831.PreRelease (12-JUL-2022) is in github here and contains:

#526 28-JUN-2022: ExecutableMBSE: Add a table view to menus to show traceability from use cases to requirements and vice versa (F.J.Chadburn)

#527 30-JUN-2022: ExecutableMBSE: Fix context diagram auto-creation to use lower case ctx - rather than CTX - (F.J.Chadburn)

#528 30-JUN-2022: ExecutableMBSE: Fix Context Diagram stereotype name so that new term is applied correctly during context package auto-creation (F.J.Chadburn)

#529 30-JUN-2022: ExecutableMBSE: When drawing a flow on context diagram ensure nested signal packages don't cause duplicate events in pull-down list (F.J.Chadburn)

#530 30-JUN-2022: ExecutableMBSE: Simple requirement table says its a layout when it's a view, doh, but fixed (F.J.Chadburn)

#531 03-JUL-2022: ExecutableMBSE: Allow for allocation of logical subsystems to/from physical subsystems (F.J.Chadburn)

#524 05-JUL-2022: ExecutableMBSE: Tweak naming of context diagram flow table to align with convention used for new tables (F.J.Chadburn)

The following video shows sample usage in an initial system context phase: