Proving Interoperability Earlier in Integration

Large systems require integration. Why? Because building large systems requires a huge team. A huge team operates efficiently by breaking a problem down into pieces that can be purchased or developed. At some point, those pieces must be brought back together. In project planning, I have seen projects show a roadmap of all the pieces […]

Read more Like this post3

Signals vs Object Flows

CONSTRAIN YOUR DESIGN BY CHOICE, NOT BY CHANCE Jim Albers, Albers Aerospace Engineering Solutions When designing a system with SysML, some choices have non-intuitive implications and consequences. For example: should inter-component interfaces be modeled using Pins and Object Flows, or using Ports with Flow Properties that pass Signals? And as a corollary, do the exchanges […]

Read more Like this post4

MBSE-enabled, tailored processes

What would an incremental, benefits-based view of MBSE look like? A program manager could select & prioritize the benefits that are needed from MBSE and require only the activities which have been determined to provide value. These benefits are not aspirations, they are the deliverables and capabilities that result from disciplined systems engineering activities. MBSE […]

Read more Like this post2
Close
Go top