Product Velocity is a new approach that enables companies to learn faster, make decisions more quickly, and deliver results.
Agility Requirements Attack security Architecture Automotive Barcamp Digital transformation Eclipse GfSE Hardware Innovation Integration Communication Complexity Conferences Artificial intelligence MBSE Modeling Traceability Openness PLM Product development Processes Quality ReConf Interface Semiant Security Software SpaceX Standards SysML SysML v2 Systems thinking Systems Engineering TdSE Tim Weilkiens Traceability Transformation Trends UML Video Christmas Further training Tools
The Single Responsibility Principle (SRP) is the principle of clear responsibility. At first glance, it seems simple, but the details are fascinating. This principle provides an initial rule on how a system should be divided into subsystems.
This series of articles deals with a widespread problem in the development of embedded systems: A lot of development there is currently still procedural, not object-oriented. There are reasons for this: Some are justified, others perhaps not. The fact is, however, that object-oriented development for embedded systems is possible and in many cases even recommended. In this series of articles...
At the end of the year, Carsten Pitz comments on the state of affairs in the SE community. Is the SE community really as closed as Carsten makes it out to be? Feel free to discuss in the comments! The article is a little provocative, but still fits in well with the festive season.
This guest article by Carsten Pitz is the fourth part on the topic of long-term support. In the first part, Carsten describes the development of a documentation system, in the second part how the wrong start can quickly lead to problems, and in the third part we looked at the human aspects. This part now deals with a concrete concept, the transformation.
This guest article by Carsten Pitz is the third part on the topic of long-term support. In the first part, Carsten describes the development of a documentation system, and in the second part, how the wrong start can quickly lead to problems. But so far he has only said how NOT to do it. But how do you do it right? This series of articles has led to several discussions between...
This guest article by Carsten Pitz is the second part on the topic of long-term support. In the first part, Carsten describes the development of a documentation system. Although it was not initially conceived as such, it became clear over time that the system would have to be available for decades. Enjoy reading the second part.
Long-term care is particularly problematic in aviation, where a product has to be maintained for up to 100 years: Century support!
The numbers 1, 3, and 7 reflect important heuristics that play an almost magical role in systems engineering.
Even though I really appreciate open source and Eclipse, my experience with Papyrus has been rather mixed so far. However, it has been several years since I was allowed to use the tool in a project. In this respect, I find the discussions with Carsten Pitz about Papyrus very exciting, as he actively uses Papyrus in projects. Carsten...
Today's article was written by Carsten Pitz, who went from simple programming to object orientation and finally ended up in systems engineering, and has gained a lot of experience in MBSE in particular. Carsten will be publishing guest articles on SE-Trends approximately every 4-6 weeks. In today's article, he introduces himself and explains how he got there in the first place,...
Unfortunately this website uses cookies! The website also works without cookies, but then you won't be able to watch videos or leave comments. You can decide for yourself what you allow. Data protection comes first - we promise!
