The Velocity Loop: A DevOps-inspired model for physical products
The Velocity Loop is a DevOps-inspired model for cyber-physical products that supports Product Velocity.
SysML v2: A four-page overview for practitioners
This 4-page overview of SysML v2 shows the metamodel, methodology, structure and behavior. Also available as a free PDF download.
The 175 flow principles: Why product development is often slower than necessary
Reinertsen's 175 flow principles are laws that can drastically accelerate product velocity.
The best SysML v2 Cheat Sheets!
Cheat sheets help you to be more productive at work. When learning a new notation such as SysML v2, here are a few good ones.
5 categories: A pragmatic guide to classifying development projects
This article presents 5 categories for classifying products in order to speed up their development.
Why interface specifications must be accessible
Good and precise interface specifications can drastically reduce integration problems by bringing stakeholders on board.
Zero Trust Security: What if the ESP32 really had a backdoor
Zero Trust Security guarantees security. This cannot prevent hardware backdoors, but it can limit the damage.
From hardware to software: HAL as a central element for black box modeling
To effectively develop systems from hardware and software, we need HAL as an abstraction for black box modeling.
Spaghetti modeling with MBSE: Not like this!
Spaghetti modeling is a common mistake when using MBSE. This checklist helps to avoid mistakes.
SysML: Avoid spaghetti models with the right package structure
It is amazing how quickly the number of elements in a system model grows. It is therefore essential to structure them correctly from the outset. Otherwise we quickly end up with "spaghetti models". This refers to models that look like a ball of spaghetti and are therefore difficult to understand. But almost all modeling languages, including SysML, give us...
Allocation: Linking behavior and structure in SysML
Two key aspects of MBSE are the modeling of behavior and structure. With SysML, the structure is modeled with blocks and the behavior with activities. Allocation is the process of linking behavior and structure. Here is a small example.
The 2 biggest pitfalls when assigning IDs
IDs, or identifiers, are everywhere. In systems engineering, we work with IDs that uniquely identify requirements. In PLM, we have part numbers. But we also deal with IDs outside our area of expertise: Websites have URLs, or now URIs (the I stands for "identifier"). Books have an ISDN. And places have addresses. Identifiers...
