首页 > 最新文献

Insight最新文献

英文 中文
Analyzing System Security Architecture in Concept Phase Using UAF Domains 基于UAF域的概念阶段系统安全体系结构分析
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70036
Juan José López García, Daniel Patrick Pereira

This paper presents combining MBSE (Model-Based System Engineering) and STPA (Systems-Theoretic Process Analysis) to mitigate security risks at an early stage of system development and to increase agility when developing or modifying architectures. The MBSE approach states that the systems development process should have a system model or a set of models as the unique source of truth. From the system model or a set of models, systems engineers of different specialties should be able to extract the information needed to perform their job. However, some specialties usually create their artefact apart from the model to perform the analysis, breaking the premises of MBSE to have a unique source of truth leading to out-of-date artefacts. This article proposes extending the Unified Architecture Framework (UAF) Profile (UAFP) to enable safety and security systems engineers to perform their analysis from the early stage of a system development process.

本文介绍了MBSE(基于模型的系统工程)和STPA(系统理论过程分析)的结合,以减轻系统开发早期阶段的安全风险,并增加开发或修改体系结构时的灵活性。MBSE方法指出,系统开发过程应该有一个系统模型或一组模型作为唯一的事实来源。从系统模型或一组模型中,不同专业的系统工程师应该能够提取执行其工作所需的信息。然而,一些专业通常会在模型之外创建他们的工件来执行分析,这打破了MBSE拥有唯一真实来源的前提,从而导致过时的工件。本文建议扩展统一架构框架(UAF)概要文件(UAFP),以使安全和安保系统工程师能够从系统开发过程的早期阶段执行他们的分析。
{"title":"Analyzing System Security Architecture in Concept Phase Using UAF Domains","authors":"Juan José López García,&nbsp;Daniel Patrick Pereira","doi":"10.1002/inst.70036","DOIUrl":"https://doi.org/10.1002/inst.70036","url":null,"abstract":"<div>\u0000 \u0000 <p>This paper presents combining MBSE (Model-Based System Engineering) and STPA (Systems-Theoretic Process Analysis) to mitigate security risks at an early stage of system development and to increase agility when developing or modifying architectures. The MBSE approach states that the systems development process should have a system model or a set of models as the unique source of truth. From the system model or a set of models, systems engineers of different specialties should be able to extract the information needed to perform their job. However, some specialties usually create their artefact apart from the model to perform the analysis, breaking the premises of MBSE to have a unique source of truth leading to out-of-date artefacts. This article proposes extending the Unified Architecture Framework (UAF) Profile (UAFP) to enable safety and security systems engineers to perform their analysis from the early stage of a system development process.</p>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"24-28"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"146224439","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
Model-Based Systems Engineering as an Enabler of Agility 基于模型的系统工程是敏捷的推动者
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70030
Sophie Plazanet, Juan Navas

Model-based systems engineering (MBSE) with agility can help systems engineering programs which deal with both increasing complexity and frequent changes in environment and usages, shorter time-to-market, uncertainty of the needs, and more sophisticated industrial schemes. Agile approaches originated in software engineering can be extended and tailored to a certain extent to complex systems engineering and particularly to MBSE. Main benefits of agility are provision of a minimum viable product as early as possible in the schedule, early capture of changes of needs, enabling to deliver a system answering to the real needs, and securing of the value proposal. It includes also potential reduction in rework of the final system through regular customer feedback throughout development (left shift for the defect correction with early exposure), and efficiency of the use of resources. Concerning MBSE, the use of models as a single source of truth for completeness and consistency is useful to share and secure the design by improving communication within engineering teams and the building and support of the development strategy, and to help to automate some tasks such as model exchange and synchronization. In addition to the benefits of each approach, combining them may help to:

  • Organize and synchronize the development and validation effort of one or multiple engineering teams.
  • Faster impact analysis including trade-off studies/options and hence a faster reaction to evolutions in expectations and constraints, that is, the agility of systems.
  • Show regularly “end to end” value to the customer and other stakeholders.
具有敏捷性的基于模型的系统工程(MBSE)可以帮助处理环境和使用中不断增加的复杂性和频繁变化、更短的上市时间、需求的不确定性以及更复杂的工业计划的系统工程程序。起源于软件工程的敏捷方法可以在一定程度上扩展和调整到复杂的系统工程,特别是MBSE。敏捷性的主要好处是尽可能早地在计划中提供最小可行产品,早期捕获需求变化,能够交付满足实际需求的系统,并确保价值建议。它还包括通过在整个开发过程中定期的客户反馈来减少最终系统的返工的潜在可能性(通过早期暴露进行缺陷纠正的左移),以及资源使用的效率。关于MBSE,使用模型作为完整性和一致性的单一事实来源,对于通过改进工程团队内部的通信以及开发策略的构建和支持来共享和保护设计是有用的,并且有助于自动化一些任务,例如模型交换和同步。除了每种方法的好处之外,将它们结合起来可能有助于:▪组织和同步一个或多个工程团队的开发和验证工作。▪更快的影响分析,包括权衡研究/选择,从而更快地对期望和约束的演变作出反应,即系统的敏捷性。▪定期向客户和其他利益相关者展示“端到端”价值。
{"title":"Model-Based Systems Engineering as an Enabler of Agility","authors":"Sophie Plazanet,&nbsp;Juan Navas","doi":"10.1002/inst.70030","DOIUrl":"https://doi.org/10.1002/inst.70030","url":null,"abstract":"<div>\u0000 \u0000 <p>Model-based systems engineering (MBSE) with agility can help systems engineering programs which deal with both increasing complexity and frequent changes in environment and usages, shorter time-to-market, uncertainty of the needs, and more sophisticated industrial schemes. Agile approaches originated in software engineering can be extended and tailored to a certain extent to complex systems engineering and particularly to MBSE. Main benefits of agility are provision of a minimum viable product as early as possible in the schedule, early capture of changes of needs, enabling to deliver a system answering to the real needs, and securing of the value proposal. It includes also potential reduction in rework of the final system through regular customer feedback throughout development (left shift for the defect correction with early exposure), and efficiency of the use of resources. Concerning MBSE, the use of models as a single source of truth for completeness and consistency is useful to share and secure the design by improving communication within engineering teams and the building and support of the development strategy, and to help to automate some tasks such as model exchange and synchronization. In addition to the benefits of each approach, combining them may help to:</p>\u0000 <p>\u0000 </p><ul>\u0000 \u0000 <li>▪ <b>Organize and synchronize</b> the development and validation effort of one or multiple engineering teams.</li>\u0000 \u0000 <li>▪ <b>Faster impact analysis</b> including trade-off studies/options and hence a <b>faster reaction to evolutions</b> in expectations and constraints, that is, the agility of systems.</li>\u0000 \u0000 <li>▪ <b>Show regularly “end to end” value</b> to the customer and other stakeholders.</li>\u0000 </ul>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"57-61"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"146680544","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
Integrating Loss-Driven Systems Engineering Activities 整合损失驱动系统工程活动
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70034
David Endler

Loss-driven systems engineering activities are key to realizing successful systems. At the same time, loss-driven systems engineering assessments are, in most cases, complex. In real life projects, integrating loss-driven systems engineering activities in the system development activities might be difficult. In some cases, there is a lack of understanding the activities' importance and sometimes there are organizational barriers. To overcome those barriers, we propose an approach based on widely accepted standards. The difficulty is most existing systems engineering standards poorly describe loss-driven systems engineering activities and how they integrate with traditional engineering activities. This paper provides an approach to successfully accomplish this integration. It is extremely important to involve loss-driven systems engineers in every life cycle phase. At the same time, achieving a common integrated approach understanding is necessary.

损失驱动的系统工程活动是实现成功系统的关键。同时,在大多数情况下,损失驱动的系统工程评估是复杂的。在实际的项目中,将损失驱动的系统工程活动集成到系统开发活动中可能是困难的。在某些情况下,缺乏对活动重要性的理解,有时存在组织障碍。为了克服这些障碍,我们提出了一种基于广泛接受的标准的方法。困难在于大多数现有的系统工程标准没有很好地描述损失驱动的系统工程活动以及它们如何与传统的工程活动集成。本文提供了一种成功完成这种集成的方法。在每一个生命周期阶段,都要让损耗驱动系统工程师参与进来,这是非常重要的。同时,实现对通用集成方法的理解是必要的。
{"title":"Integrating Loss-Driven Systems Engineering Activities","authors":"David Endler","doi":"10.1002/inst.70034","DOIUrl":"https://doi.org/10.1002/inst.70034","url":null,"abstract":"<div>\u0000 \u0000 <p>Loss-driven systems engineering activities are key to realizing successful systems. At the same time, loss-driven systems engineering assessments are, in most cases, complex. In real life projects, integrating loss-driven systems engineering activities in the system development activities might be difficult. In some cases, there is a lack of understanding the activities' importance and sometimes there are organizational barriers. To overcome those barriers, we propose an approach based on widely accepted standards. The difficulty is most existing systems engineering standards poorly describe loss-driven systems engineering activities and how they integrate with traditional engineering activities. This paper provides an approach to successfully accomplish this integration. It is extremely important to involve loss-driven systems engineers in every life cycle phase. At the same time, achieving a common integrated approach understanding is necessary.</p>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"14-18"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"146680562","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
Functional-Outcomes Driven Tailoring in Modern Complex Engineered System Development 现代复杂工程系统开发中的功能-结果驱动裁剪
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70029
Barend Botha

Modern engineered systems demand lifecycle strategies that are responsive, risk-aware, and aligned with evolving needs. Historically, systems engineering has been methodology-driven, with formal frameworks such as the V-Model or waterfall used to guide process rigor and governance. These methodologies provided structure and control, especially for large, safety-critical engineered programs. However, as systems have become more complex and adaptive, the limitations of rigid methodological adherence have become increasingly apparent. This article retraces the reasoning behind moving from methodology-driven to function-driven, to outcomes-focused, and finally to functionally enabled outcomes. It introduces the concept of functional-outcomes driven tailoring (FODT) as a unifying framework that drives lifecycle performance through functional alignment to mission outcomes.

现代工程系统要求生命周期策略是响应性的、风险意识的,并与不断变化的需求保持一致。从历史上看,系统工程一直是方法驱动的,使用正式的框架,如V-Model或瀑布,用于指导过程的严密性和治理。这些方法提供了结构和控制,特别是对于大型的、安全关键的工程项目。然而,随着系统变得更加复杂和适应性强,严格遵循方法的局限性变得越来越明显。本文追溯了从方法驱动到功能驱动,再到以结果为中心,最后到功能支持的结果背后的原因。它引入了功能-结果驱动裁剪(FODT)的概念,作为一个统一的框架,通过功能与任务结果的一致性来驱动生命周期性能。
{"title":"Functional-Outcomes Driven Tailoring in Modern Complex Engineered System Development","authors":"Barend Botha","doi":"10.1002/inst.70029","DOIUrl":"https://doi.org/10.1002/inst.70029","url":null,"abstract":"<div>\u0000 \u0000 <p>Modern engineered systems demand lifecycle strategies that are responsive, risk-aware, and aligned with evolving needs. Historically, systems engineering has been methodology-driven, with formal frameworks such as the V-Model or waterfall used to guide process rigor and governance. These methodologies provided structure and control, especially for large, safety-critical engineered programs. However, as systems have become more complex and adaptive, the limitations of rigid methodological adherence have become increasingly apparent. This article retraces the reasoning behind moving from methodology-driven to function-driven, to outcomes-focused, and finally to functionally enabled outcomes. It introduces the concept of functional-outcomes driven tailoring (FODT) as a unifying framework that drives lifecycle performance through functional alignment to mission outcomes.</p>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"7-13"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"146217253","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
What Is the Role of a Systems Engineer In an Engineering Organization? 系统工程师在工程组织中的角色是什么?
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70031
Richard Beasley

This article discusses the role of a “specialist” Systems Engineer inside an engineering focused on ensures the engineering parts integrate to achieve the objectives of the whole – and so is embedding a systems approach throughout the organization – trying to “make Systems Engineering the way engineering is done”. In this type of organization all engineers need systems engineering as a core skill (which is part of them becoming T-shaped“. The specialist Systems Engineer needs to be more π-shaped, with specialism in the systems approach used to inform and guide all the other disciplines which need to be integrated together. Since systems engineering is an integrating discipline the group of systems engineers must not become ”just another“ technical silo.

本文讨论了“专家”系统工程师在工程中的角色,重点是确保工程部分集成以实现整体目标-因此在整个组织中嵌入系统方法-试图“使系统工程成为完成工程的方式”。在这种类型的组织中,所有工程师都需要将系统工程作为核心技能(这是他们成为t型的一部分)。专业系统工程师需要更加π形,在系统方法方面具有专业性,用于通知和指导所有需要整合在一起的其他学科。因为系统工程是一个集成的学科,所以系统工程师团队不应该成为“另一个”技术竖井。
{"title":"What Is the Role of a Systems Engineer In an Engineering Organization?","authors":"Richard Beasley","doi":"10.1002/inst.70031","DOIUrl":"https://doi.org/10.1002/inst.70031","url":null,"abstract":"<div>\u0000 \u0000 <p>This article discusses the role of a “specialist” Systems Engineer inside an engineering focused on ensures the engineering parts integrate to achieve the objectives of the whole – and so is embedding a systems approach throughout the organization – trying to “make Systems Engineering the way engineering is done”. In this type of organization all engineers need systems engineering as a core skill (which is part of them becoming T-shaped“. The specialist Systems Engineer needs to be more π-shaped, with specialism in the systems approach used to inform and guide all the other disciplines which need to be integrated together. Since systems engineering is an integrating discipline the group of systems engineers must not become ”just another“ technical silo.</p>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"29-32"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"147320801","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
TNO-ESI – Systems Engineering Methodologies for Managing Complexity in the High-Tech Equipment Industry: Our Roadmap TNO-ESI -管理高科技设备行业复杂性的系统工程方法:我们的路线图
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70033
Wouter Leibbrandt, Jacco Wesselius, Frans Beenker

The high-tech equipment industry brings complex industrial products to the market with high speed, enhanced functionality, a better cost-performance ratio, and greater integration into customer workflows. Driven by digitalization, the complexity of these systems continues to grow steeply. To manage this complexity, continuous innovation in systems engineering methodologies is needed. TNO-ESI targets to 1) create impactful and industrially applicable systems engineering methodologies and 2) provide innovation support to the industry to get these applied in an industrial context. The ESI research program is defined through a roadmapping process that follows two tracks: a roadmap that maps industry needs and related research and development requirements and a roadmap that describes the developments in the expertise areas necessary for addressing these industry needs. In this paper, we describe the ESI mission, our way of working and activities, and explain the roadmapping process and the roadmaps.

高科技设备行业将复杂的工业产品以高速、增强的功能、更好的性价比和更大的集成到客户工作流程中推向市场。在数字化的推动下,这些系统的复杂性继续急剧增长。为了管理这种复杂性,需要在系统工程方法中不断创新。TNO-ESI的目标是:1)创建有影响力的、工业上适用的系统工程方法;2)为行业提供创新支持,使这些方法在工业环境中得到应用。ESI研究计划是通过一个路线图过程来定义的,该路线图遵循两条轨道:一个路线图描绘了行业需求和相关研发需求,一个路线图描述了解决这些行业需求所需的专业领域的发展。在本文中,我们描述了ESI的使命,我们的工作方式和活动,并解释了路线图的制定过程和路线图。
{"title":"TNO-ESI – Systems Engineering Methodologies for Managing Complexity in the High-Tech Equipment Industry: Our Roadmap","authors":"Wouter Leibbrandt,&nbsp;Jacco Wesselius,&nbsp;Frans Beenker","doi":"10.1002/inst.70033","DOIUrl":"https://doi.org/10.1002/inst.70033","url":null,"abstract":"<div>\u0000 \u0000 <p>The high-tech equipment industry brings complex industrial products to the market with high speed, enhanced functionality, a better cost-performance ratio, and greater integration into customer workflows. Driven by digitalization, the complexity of these systems continues to grow steeply. To manage this complexity, continuous innovation in systems engineering methodologies is needed. TNO-ESI targets to 1) create impactful and industrially applicable systems engineering methodologies and 2) provide innovation support to the industry to get these applied in an industrial context. The ESI research program is defined through a roadmapping process that follows two tracks: a roadmap that maps industry needs and related research and development requirements and a roadmap that describes the developments in the expertise areas necessary for addressing these industry needs. In this paper, we describe the ESI mission, our way of working and activities, and explain the roadmapping process and the roadmaps.</p>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"41-47"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"146217254","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
Modular Over-the-air Software Updates for Safety-critical Real-time Systems 安全关键实时系统的模块化无线软件更新
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70032
Domenik Helms, Patrick Uven, Kim Grüttner

Automotive software is undergoing a rapid change toward artificial intelligence and towards more and more connectedness with other systems. For both, an incremental design paradigm is desired, where the car's software is frequently updated after production but still can guarantee the highest automotive safety standards. We present a design flow and tool framework enabling a DevOps paradigm for automotive software development. DevOps means that software is developed in a continuous loop of development, deployment, usage in the field, collection of runtime data and feedback to the developers for the next design iteration. The software developers get support in defining, developing, and verifying new software functions based on the data gathered in the field by the previous software generation. The software developers can define contracts describing the time and resource assumptions on the integration environment and guarantees for other dependent software components in the system. These contracts allow a composition of software components and proof obligations to be discharged at design time through virtual integration testing and runtime through continuous monitoring of assumptions and guarantees on the software component's interfaces. An update package, consisting of the software component and its contracts, is then automatically created, transferred over the air, and deployed in the car. Monitors derived from the contracts allow for supervising the system's behavior, detecting failures at runtime, and annotating the situation to be included in a data collection, fueling the next design iteration.

汽车软件正经历着向人工智能和越来越多地与其他系统连接的快速变化。对于两者来说,都需要一种渐进式的设计范式,即汽车的软件在生产后经常更新,但仍然可以保证最高的汽车安全标准。我们提出了一个设计流程和工具框架,使汽车软件开发的DevOps范式成为可能。DevOps意味着软件是在开发、部署、现场使用、收集运行时数据和向开发人员反馈下一次设计迭代的连续循环中开发的。软件开发人员在定义、开发和验证基于上一代软件在该领域收集的数据的新软件功能方面得到支持。软件开发人员可以定义契约,描述对集成环境的时间和资源假设,以及对系统中其他相关软件组件的保证。这些契约允许软件组件的组合和证明义务在设计时通过虚拟集成测试和运行时通过对软件组件接口上的假设和保证的持续监控来实现。然后,由软件组件及其契约组成的更新包被自动创建,通过空中传输,并部署在汽车中。来自合同的监视器允许监督系统的行为,在运行时检测故障,并注释要包含在数据集合中的情况,为下一个设计迭代提供动力。
{"title":"Modular Over-the-air Software Updates for Safety-critical Real-time Systems","authors":"Domenik Helms,&nbsp;Patrick Uven,&nbsp;Kim Grüttner","doi":"10.1002/inst.70032","DOIUrl":"https://doi.org/10.1002/inst.70032","url":null,"abstract":"<div>\u0000 \u0000 <p>Automotive software is undergoing a rapid change toward artificial intelligence and towards more and more connectedness with other systems. For both, an incremental design paradigm is desired, where the car's software is frequently updated after production but still can guarantee the highest automotive safety standards. We present a design flow and tool framework enabling a DevOps paradigm for automotive software development. DevOps means that software is developed in a continuous loop of development, deployment, usage in the field, collection of runtime data and feedback to the developers for the next design iteration. The software developers get support in defining, developing, and verifying new software functions based on the data gathered in the field by the previous software generation. The software developers can define contracts describing the time and resource assumptions on the integration environment and guarantees for other dependent software components in the system. These contracts allow a composition of software components and proof obligations to be discharged at design time through virtual integration testing and runtime through continuous monitoring of assumptions and guarantees on the software component's interfaces. An update package, consisting of the software component and its contracts, is then automatically created, transferred over the air, and deployed in the car. Monitors derived from the contracts allow for supervising the system's behavior, detecting failures at runtime, and annotating the situation to be included in a data collection, fueling the next design iteration.</p>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"49-52"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"147275025","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
How Large Scale Agile Can Operate Systems Engineering in the Future 大规模敏捷如何在未来操作系统工程
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70037
Laurent Alt, Mikaël Le Mouëlli

The significant shift happening today towards more connected, more automated, and more autonomous systems is bringing software inside all systems, and at the same time agile practices. Our experience of large-scale agile deployments in companies building or operating complex systems in automotive and aerospace shows that, whereas both approaches can easily coexist in isolated teams within the same company, major problems arise when coordinating them at the leadership level, where they are perceived as antagonist, and create misalignments, friction and quality issues. In this article, we propose to describe why it is important to make agile and systems engineering work together, how to do it, and how this impacts how we see value, systems, digital twins, and leadership. The following concepts of the FuSE agile roadmaps are addressed:

  • ▪ Agility with long lead time components and dependencies
  • ▪ Agility across organizations boundaries
  • ▪ Orchestrating agile operations.
今天发生的重大转变是向更连接、更自动化和更自治的系统转变,这将软件引入所有系统,同时引入敏捷实践。我们在汽车和航空航天领域构建或操作复杂系统的公司中进行大规模敏捷部署的经验表明,尽管这两种方法可以在同一公司的孤立团队中轻松共存,但在领导层面协调它们时出现了主要问题,它们被视为对手,并造成不一致、摩擦和质量问题。在本文中,我们打算描述为什么让敏捷和系统工程一起工作很重要,如何做到这一点,以及这如何影响我们对价值、系统、数字孪生和领导力的看法。以下是FuSE敏捷路线图的概念:-具有长交付周期组件和依赖关系的敏捷性-跨组织边界的敏捷性-协调敏捷操作。
{"title":"How Large Scale Agile Can Operate Systems Engineering in the Future","authors":"Laurent Alt,&nbsp;Mikaël Le Mouëlli","doi":"10.1002/inst.70037","DOIUrl":"https://doi.org/10.1002/inst.70037","url":null,"abstract":"<div>\u0000 \u0000 <p>The significant shift happening today towards more connected, more automated, and more autonomous systems is bringing software inside all systems, and at the same time agile practices. Our experience of large-scale agile deployments in companies building or operating complex systems in automotive and aerospace shows that, whereas both approaches can easily coexist in isolated teams within the same company, major problems arise when coordinating them at the leadership level, where they are perceived as antagonist, and create misalignments, friction and quality issues. In this article, we propose to describe why it is important to make agile and systems engineering work together, how to do it, and how this impacts how we see value, systems, digital twins, and leadership. The following concepts of the FuSE agile roadmaps are addressed:</p>\u0000 <p>\u0000 </p><ul>\u0000 \u0000 <li>▪ Agility with long lead time components and dependencies</li>\u0000 \u0000 <li>▪ Agility across organizations boundaries</li>\u0000 \u0000 <li>▪ Orchestrating agile operations.</li>\u0000 </ul>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"53-56"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"146680431","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
Very Small Entities (VSEs): Outsourcing Risk to the Supply Chain Is Placing Systems Security Engineering on a Clay Foundation, but Playing Games May Help 非常小的实体(vse):外包给供应链的风险是把系统安全工程放在一个黏土的基础上,但玩游戏可能会有所帮助
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70038
Roar E. Georgsen, Geir M. Køien

This article addresses the inherent risk in a supply chain that comprises primarily Very Small Entities (VSE) with little to no security proficiency and limited resources and incentive to prioritize system security. In a globalized economy based on outsourcing and risk-sharing, most engineering activities occur in the smallest companies, even for large and complex projects. The Future of Systems Engineering initiative (FuSE) appropriately has agility at the core of its Systems Security Engineering (SSE) foundation concepts, and VSEs are by their very nature agile. However, the line between agility and chaos may be thin, and engineers at VSEs must often accept a level of restraint and rigidity beyond their comfort level to achieve functional agility. The primary challenge in VSEs is adding structure without the necessary resources to enforce compliance manually. We propose that VSE focus their initial efforts on FuSE SSE Foundation Concepts that play into their nature and strengths as dynamic human social activity systems. Improvements in security proficiency and stakeholder alignment do not necessarily require much formal structure, and digital tools combined with social strategies can add structure to a resource-constrained environment. Games can be excellent low-cost tools to provide structure while minimizing resistance, and Agile Model-Based Systems Engineering (AMBSE) using digital models can support automated enforcement. Here we use the card game Elevation of Privilege (EoP) as an example. Within the context of a SysML Threat Model integrated into a larger System Model, players naturally treat security requirements as traceable functional requirements. Automated model validation, re-usable components and patterns enforce a Zero-Trust architecture, a sufficiently formal trust model to provide evidence-based assurance, yet achievable for small companies with limited resources.

本文讨论了供应链中的固有风险,该供应链主要由非常小的实体(VSE)组成,这些实体几乎没有安全能力,并且资源有限,没有优先考虑系统安全性的动机。在基于外包和风险分担的全球化经济中,大多数工程活动发生在最小的公司中,即使是大型和复杂的项目。系统工程的未来计划(FuSE)恰当地将敏捷性作为其系统安全工程(SSE)基础概念的核心,而vse本质上是敏捷的。然而,敏捷性和混乱之间的界限可能很薄,vse的工程师必须经常接受一定程度的约束和刚性,以实现功能敏捷性。vse中的主要挑战是在没有必要的资源来手动执行遵从性的情况下添加结构。我们建议VSE将最初的努力集中在FuSE SSE基础概念上,这些概念可以发挥其作为动态人类社会活动系统的性质和优势。安全熟练程度和涉众一致性方面的改进并不一定需要太多的正式结构,与社交策略相结合的数字工具可以为资源受限的环境添加结构。游戏可以是提供结构的优秀低成本工具,同时将阻力降至最低,而使用数字模型的基于敏捷模型的系统工程(AMBSE)可以支持自动执行。这里我们以纸牌游戏《Elevation of Privilege》(EoP)为例。在将SysML威胁模型集成到更大的系统模型的上下文中,参与者自然会将安全需求视为可跟踪的功能需求。自动模型验证、可重用组件和模式强制实现零信任体系结构,这是一个足够正式的信任模型,可以提供基于证据的保证,但对于资源有限的小公司来说是可以实现的。
{"title":"Very Small Entities (VSEs): Outsourcing Risk to the Supply Chain Is Placing Systems Security Engineering on a Clay Foundation, but Playing Games May Help","authors":"Roar E. Georgsen,&nbsp;Geir M. Køien","doi":"10.1002/inst.70038","DOIUrl":"https://doi.org/10.1002/inst.70038","url":null,"abstract":"<div>\u0000 \u0000 <p>This article addresses the inherent risk in a supply chain that comprises primarily Very Small Entities (VSE) with little to no security proficiency and limited resources and incentive to prioritize system security. In a globalized economy based on outsourcing and risk-sharing, most engineering activities occur in the smallest companies, even for large and complex projects. The Future of Systems Engineering initiative (FuSE) appropriately has agility at the core of its Systems Security Engineering (SSE) foundation concepts, and VSEs are by their very nature agile. However, the line between agility and chaos may be thin, and engineers at VSEs must often accept a level of restraint and rigidity beyond their comfort level to achieve functional agility. The primary challenge in VSEs is adding structure without the necessary resources to enforce compliance manually. We propose that VSE focus their initial efforts on FuSE SSE Foundation Concepts that play into their nature and strengths as dynamic human social activity systems. Improvements in security proficiency and stakeholder alignment do not necessarily require much formal structure, and digital tools combined with social strategies can add structure to a resource-constrained environment. Games can be excellent low-cost tools to provide structure while minimizing resistance, and Agile Model-Based Systems Engineering (AMBSE) using digital models can support automated enforcement. Here we use the card game <i>Elevation of Privilege</i> (EoP) as an example. Within the context of a SysML Threat Model integrated into a larger System Model, players naturally treat security requirements as traceable functional requirements. Automated model validation, re-usable components and patterns enforce a Zero-Trust architecture, a sufficiently formal trust model to provide evidence-based assurance, yet achievable for small companies with limited resources.</p>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"19-23"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"146680545","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
Systems Skills … From Here to Diversity 系统技能:从这里到多样性
IF 1 4区 工程技术 Q4 INSTRUMENTS & INSTRUMENTATION Pub Date : 2026-02-15 DOI: 10.1002/inst.70035
Alan Harding

Competency, the ability to do things, is at the heart of how systems engineers realise successful systems. Over the years INCOSE and partners have codified what this means, initially in the INCOSE UK Competency Framework (INCOSE UK 2010) later adopted globally by INCOSE and used as the basis of the INCOSE Systems Engineering Competency Framework (INCOSE 2018) which, notably, included a new area of professional skills. This article considers competency from the perspective of Diversity, Equity, and Inclusion (referred to as DEI) using a variety of sources including the recently published INCOSE SE Vision 2035 (INCOSE 2022) and a variety of competency frameworks to offer a view of how the skills and competencies of systems engineers need to evolve in the future. Five new competencies are proposed, as are opportunities to improve the definitions of five more.

能力,做事的能力,是系统工程师实现成功系统的核心。多年来,INCOSE和合作伙伴已经将这一含义编入了法典,最初是在INCOSE英国能力框架(INCOSE UK 2010)中,后来被INCOSE在全球范围内采用,并作为INCOSE系统工程能力框架(INCOSE 2018)的基础,值得注意的是,该框架包括了一个新的专业技能领域。本文从多样性、公平性和包容性(称为DEI)的角度考虑了能力,使用了各种来源,包括最近出版的INCOSE SE愿景2035 (INCOSE 2022)和各种能力框架,以提供系统工程师的技能和能力在未来需要如何发展的观点。提出了五项新的能力,以及改进另外五项能力定义的机会。
{"title":"Systems Skills … From Here to Diversity","authors":"Alan Harding","doi":"10.1002/inst.70035","DOIUrl":"https://doi.org/10.1002/inst.70035","url":null,"abstract":"<div>\u0000 \u0000 <p>Competency, the ability to do things, is at the heart of how systems engineers realise successful systems. Over the years INCOSE and partners have codified what this means, initially in the INCOSE UK Competency Framework (INCOSE UK 2010) later adopted globally by INCOSE and used as the basis of the INCOSE Systems Engineering Competency Framework (INCOSE 2018) which, notably, included a new area of professional skills. This article considers competency from the perspective of Diversity, Equity, and Inclusion (referred to as DEI) using a variety of sources including the recently published INCOSE SE Vision 2035 (INCOSE 2022) and a variety of competency frameworks to offer a view of how the skills and competencies of systems engineers need to evolve in the future. Five new competencies are proposed, as are opportunities to improve the definitions of five more.</p>\u0000 </div>","PeriodicalId":13956,"journal":{"name":"Insight","volume":"29 1","pages":"33-40"},"PeriodicalIF":1.0,"publicationDate":"2026-02-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"146224440","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":4,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
期刊
Insight
全部 Acc. Chem. Res. ACS Applied Bio Materials ACS Appl. Electron. Mater. ACS Appl. Energy Mater. ACS Appl. Mater. Interfaces ACS Appl. Nano Mater. ACS Appl. Polym. Mater. ACS BIOMATER-SCI ENG ACS Catal. ACS Cent. Sci. ACS Chem. Biol. ACS Chemical Health & Safety ACS Chem. Neurosci. ACS Comb. Sci. ACS Earth Space Chem. ACS Energy Lett. ACS Infect. Dis. ACS Macro Lett. ACS Mater. Lett. ACS Med. Chem. Lett. ACS Nano ACS Omega ACS Photonics ACS Sens. ACS Sustainable Chem. Eng. ACS Synth. Biol. Anal. Chem. BIOCHEMISTRY-US Bioconjugate Chem. BIOMACROMOLECULES Chem. Res. Toxicol. Chem. Rev. Chem. Mater. CRYST GROWTH DES ENERG FUEL Environ. Sci. Technol. Environ. Sci. Technol. Lett. Eur. J. Inorg. Chem. IND ENG CHEM RES Inorg. Chem. J. Agric. Food. Chem. J. Chem. Eng. Data J. Chem. Educ. J. Chem. Inf. Model. J. Chem. Theory Comput. J. Med. Chem. J. Nat. Prod. J PROTEOME RES J. Am. Chem. Soc. LANGMUIR MACROMOLECULES Mol. Pharmaceutics Nano Lett. Org. Lett. ORG PROCESS RES DEV ORGANOMETALLICS J. Org. Chem. J. Phys. Chem. J. Phys. Chem. A J. Phys. Chem. B J. Phys. Chem. C J. Phys. Chem. Lett. Analyst Anal. Methods Biomater. Sci. Catal. Sci. Technol. Chem. Commun. Chem. Soc. Rev. CHEM EDUC RES PRACT CRYSTENGCOMM Dalton Trans. Energy Environ. Sci. ENVIRON SCI-NANO ENVIRON SCI-PROC IMP ENVIRON SCI-WAT RES Faraday Discuss. Food Funct. Green Chem. Inorg. Chem. Front. Integr. Biol. J. Anal. At. Spectrom. J. Mater. Chem. A J. Mater. Chem. B J. Mater. Chem. C Lab Chip Mater. Chem. Front. Mater. Horiz. MEDCHEMCOMM Metallomics Mol. Biosyst. Mol. Syst. Des. Eng. Nanoscale Nanoscale Horiz. Nat. Prod. Rep. New J. Chem. Org. Biomol. Chem. Org. Chem. Front. PHOTOCH PHOTOBIO SCI PCCP Polym. Chem.
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1