InsightPub Date : 2026-02-15DOI: 10.1002/inst.70030
Sophie Plazanet, Juan Navas
{"title":"Model-Based Systems Engineering as an Enabler of Agility","authors":"Sophie Plazanet, Juan Navas","doi":"10.1002/inst.70030","DOIUrl":"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}
InsightPub Date : 2026-02-15DOI: 10.1002/inst.70029
Barend Botha
{"title":"Functional-Outcomes Driven Tailoring in Modern Complex Engineered System Development","authors":"Barend Botha","doi":"10.1002/inst.70029","DOIUrl":"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}
InsightPub Date : 2026-02-15DOI: 10.1002/inst.70031
Richard Beasley
{"title":"What Is the Role of a Systems Engineer In an Engineering Organization?","authors":"Richard Beasley","doi":"10.1002/inst.70031","DOIUrl":"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}
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
