利用 UAF 建立企业软件模型

Matthew Hause, Lars-Olof Kihlström
{"title":"利用 UAF 建立企业软件模型","authors":"Matthew Hause,&nbsp;Lars-Olof Kihlström","doi":"10.1002/iis2.13280","DOIUrl":null,"url":null,"abstract":"<p>Systems and Software Engineers often have an uneasy relationship. The job of the systems engineer is to work with the stakeholders to define a set of requirements that meet their needs. These are then allocated to various solution spaces such as electronic hardware, mechanical, procedural, and software among others. For many systems, the functional requirements are almost exclusively software requirements. Correspondingly, as an increasing amount of project manpower, schedule time, and budget are allocated to software, it becomes increasingly important that systems and software engineers communicate effectively. The Systems Modeling Language (SysML) has helped in this regard in that it can provide executable behavioral models with precise semantics to express software requirements in a model. These models define “What is required” without overly constraining the implementation. In addition, SysML can be used to define performance constraints, required concurrency, hardware memory and processor budgets, interfaces, safety critical requirements, etc. These aspects are essential for software engineers to understand the constraints and limitations of their environment. At the System of Systems (SoS)/Enterprise level, defining software/systems employs a similar pattern, but at a higher level of abstraction. In the Unified Architecture Framework, capabilities are defined for the enterprise, with systems and software allocated to realize the capabilities. In the same way that capabilities depend on one another, the implementing systems and software interact to support each other. In the past, enterprise software would be modeled as residing in mainframes in a federated software pattern. Modern software can be modeled throughout the enterprise in a distributed network that can adapt to the changing needs of the enterprise to do load leveling, dynamic and late binding, reconfiguration, and reallocation of hardware resources as necessary. If the domain includes the Industrial Internet of Things (IIOT), then deployment could include edge devices, embedded software, Programmable Logic Controllers (PLC), PCs, servers, cloud computing, and of course mainframes. The Object management Group (OMG) Data Distribution Services (DDS) standard enables these capabilities across these devices in a universal format implemented by multiple vendors. However, before this complex system of systems can be implemented, it must first be architected and designed to ensure that it will be fit for purpose both now and as the complex system of systems expands and evolves. This paper will examine the aspects of modeling software in the UAF, and how it can help guide enterprise and system and software architecture.</p>","PeriodicalId":100663,"journal":{"name":"INCOSE International Symposium","volume":"34 1","pages":"2452-2475"},"PeriodicalIF":0.0000,"publicationDate":"2024-09-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Modeling Enterprise Software with UAF\",\"authors\":\"Matthew Hause,&nbsp;Lars-Olof Kihlström\",\"doi\":\"10.1002/iis2.13280\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"<p>Systems and Software Engineers often have an uneasy relationship. The job of the systems engineer is to work with the stakeholders to define a set of requirements that meet their needs. These are then allocated to various solution spaces such as electronic hardware, mechanical, procedural, and software among others. For many systems, the functional requirements are almost exclusively software requirements. Correspondingly, as an increasing amount of project manpower, schedule time, and budget are allocated to software, it becomes increasingly important that systems and software engineers communicate effectively. The Systems Modeling Language (SysML) has helped in this regard in that it can provide executable behavioral models with precise semantics to express software requirements in a model. These models define “What is required” without overly constraining the implementation. In addition, SysML can be used to define performance constraints, required concurrency, hardware memory and processor budgets, interfaces, safety critical requirements, etc. These aspects are essential for software engineers to understand the constraints and limitations of their environment. At the System of Systems (SoS)/Enterprise level, defining software/systems employs a similar pattern, but at a higher level of abstraction. In the Unified Architecture Framework, capabilities are defined for the enterprise, with systems and software allocated to realize the capabilities. In the same way that capabilities depend on one another, the implementing systems and software interact to support each other. In the past, enterprise software would be modeled as residing in mainframes in a federated software pattern. Modern software can be modeled throughout the enterprise in a distributed network that can adapt to the changing needs of the enterprise to do load leveling, dynamic and late binding, reconfiguration, and reallocation of hardware resources as necessary. If the domain includes the Industrial Internet of Things (IIOT), then deployment could include edge devices, embedded software, Programmable Logic Controllers (PLC), PCs, servers, cloud computing, and of course mainframes. The Object management Group (OMG) Data Distribution Services (DDS) standard enables these capabilities across these devices in a universal format implemented by multiple vendors. However, before this complex system of systems can be implemented, it must first be architected and designed to ensure that it will be fit for purpose both now and as the complex system of systems expands and evolves. This paper will examine the aspects of modeling software in the UAF, and how it can help guide enterprise and system and software architecture.</p>\",\"PeriodicalId\":100663,\"journal\":{\"name\":\"INCOSE International Symposium\",\"volume\":\"34 1\",\"pages\":\"2452-2475\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2024-09-07\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"INCOSE International Symposium\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://onlinelibrary.wiley.com/doi/10.1002/iis2.13280\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"INCOSE International Symposium","FirstCategoryId":"1085","ListUrlMain":"https://onlinelibrary.wiley.com/doi/10.1002/iis2.13280","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

摘要

系统工程师和软件工程师之间的关系往往并不融洽。系统工程师的工作是与利益相关者合作,确定一系列满足其需求的要求。然后将这些需求分配到不同的解决方案空间,如电子硬件、机械、程序和软件等。对于许多系统来说,功能需求几乎完全是软件需求。相应地,随着越来越多的项目人力、进度时间和预算被分配到软件上,系统工程师和软件工程师之间的有效沟通就变得越来越重要。系统建模语言(SysML)在这方面提供了帮助,因为它可以提供具有精确语义的可执行行为模型,在模型中表达软件需求。这些模型定义了 "需要什么",而不会过分限制实现。此外,SysML 还可用于定义性能约束、所需并发性、硬件内存和处理器预算、接口、安全关键要求等。这些方面对于软件工程师了解其环境的约束和限制至关重要。在系统(SoS)/企业层面,软件/系统的定义采用了类似的模式,但抽象程度更高。在统一架构框架中,为企业定义了能力,并分配了系统和软件来实现这些能力。与能力相互依赖的方式相同,实施系统和软件也是相互影响、相互支持的。过去,企业软件是以联合软件模式在大型机中驻留的。现代软件可以在整个企业的分布式网络中建模,这种网络可以适应企业不断变化的需求,在必要时进行负载均衡、动态和后期绑定、重新配置和重新分配硬件资源。如果领域包括工业物联网 (IIOT),那么部署可包括边缘设备、嵌入式软件、可编程逻辑控制器 (PLC)、个人电脑、服务器、云计算,当然还有大型机。对象管理组织(OMG)的数据分发服务(DDS)标准可使这些功能以通用格式跨越这些设备,并由多个供应商实施。然而,在实施这一复杂的系统之前,必须首先对其进行架构和设计,以确保其适用于当前以及复杂系统的扩展和发展。本文将探讨 UAF 中建模软件的各个方面,以及它如何帮助指导企业、系统和软件架构。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Modeling Enterprise Software with UAF

Systems and Software Engineers often have an uneasy relationship. The job of the systems engineer is to work with the stakeholders to define a set of requirements that meet their needs. These are then allocated to various solution spaces such as electronic hardware, mechanical, procedural, and software among others. For many systems, the functional requirements are almost exclusively software requirements. Correspondingly, as an increasing amount of project manpower, schedule time, and budget are allocated to software, it becomes increasingly important that systems and software engineers communicate effectively. The Systems Modeling Language (SysML) has helped in this regard in that it can provide executable behavioral models with precise semantics to express software requirements in a model. These models define “What is required” without overly constraining the implementation. In addition, SysML can be used to define performance constraints, required concurrency, hardware memory and processor budgets, interfaces, safety critical requirements, etc. These aspects are essential for software engineers to understand the constraints and limitations of their environment. At the System of Systems (SoS)/Enterprise level, defining software/systems employs a similar pattern, but at a higher level of abstraction. In the Unified Architecture Framework, capabilities are defined for the enterprise, with systems and software allocated to realize the capabilities. In the same way that capabilities depend on one another, the implementing systems and software interact to support each other. In the past, enterprise software would be modeled as residing in mainframes in a federated software pattern. Modern software can be modeled throughout the enterprise in a distributed network that can adapt to the changing needs of the enterprise to do load leveling, dynamic and late binding, reconfiguration, and reallocation of hardware resources as necessary. If the domain includes the Industrial Internet of Things (IIOT), then deployment could include edge devices, embedded software, Programmable Logic Controllers (PLC), PCs, servers, cloud computing, and of course mainframes. The Object management Group (OMG) Data Distribution Services (DDS) standard enables these capabilities across these devices in a universal format implemented by multiple vendors. However, before this complex system of systems can be implemented, it must first be architected and designed to ensure that it will be fit for purpose both now and as the complex system of systems expands and evolves. This paper will examine the aspects of modeling software in the UAF, and how it can help guide enterprise and system and software architecture.

求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信