{"id":10029,"date":"2018-06-28T00:01:07","date_gmt":"2018-06-28T04:01:07","guid":{"rendered":"https:\/\/blog.zuken.com\/?p=10029"},"modified":"2025-02-21T10:55:11","modified_gmt":"2025-02-21T10:55:11","slug":"systems-engineering-customer-voice","status":"publish","type":"post","link":"https:\/\/www.zuken.com\/en\/blog\/systems-engineering-customer-voice\/","title":{"rendered":"Why Systems Engineering is the Voice of the Customer"},"content":{"rendered":"
\"Enrique
Enrique Krajmalnik, CTO of No Magic, delivering ZIW 2018’s keynote<\/figcaption><\/figure>\n

We broke new ground for many attendees by opening our Zuken Innovation World Americas 2018<\/a> conference with a keynote on Model-Based Systems Engineering (MBSE). We were fortunate to have an expert in the field speak: Enrique Krajmalnik, CTO of No Magic, an industry leader in MBSE.<\/p>\n

Systems Engineering has been around for a while, but the practice of model-based systems engineering is gaining adoption in many business sectors. Some engineering teams are practicing MBSE, while others are moving more slowly toward adoption. With this in mind, Enrique offered his perspective on how the field has developed to the current day, and hinted at how he saw the future. Let me share some of my takeaways with you.<\/p>\n

1. \u201cSystems engineering is the voice of the customer\u201d<\/h3>\n

I was surprised by one of Enrique\u2019s opening comments \u2013 \u201cSystems Engineering is the voice of the customer\u201d. We often hear that product marketing is the voice of the customer, but as I delve deeper into the system model construction, I get it. The requirements, structure and behavior defined in the model are the first representation of the new product. The first interpretation of the customer\u2019s needs as an engineering representation is done by the systems engineers. That is notable.<\/p>\n

2. Complexity is driving the transition to MBSE<\/h3>\n

According to Enrique, those same systems engineers are using documents to define products\/systems of growing complexity. It is recognized that this growing complexity, coupled with the documents approach, is creating serious defects early in the product lifecycle. So complexity is pushing us to transition from document-based design to a model-based design process. MBSE is supported by standards and offers graphical modeling, analysis, verification and validation. This is all based on the SysML language. Another good take-away.<\/p>\n

3. Models need to be integrated into an implementation process<\/h3>\n

As systems engineers and companies adopt MBSE practices, there is a need to integrate the models into an implementation process. Enrique pointed to two areas where active integration is taking place:<\/p>\n