bluuebunny/crossref_metadata_2025_split huggingface dataset:
A New Horizon for Healthcare Delivery: A System of Systems Perspective and Governing Proposition
Authors: Mogahed Mohamed , Mansouri Mo 
Published: September 2024

AbstractThe healthcare system is grappling with inherent challenges, functioning akin to a fragmented cottage‐like industry, leading to significant cost implications and compromised care quality. This paper employs a systematic approach to scrutinize the Healthcare Delivery System (HDS) comprehensively, categorizing it as a Collaborative System of Systems (SoS), where multiple independent systems operate collectively, maintaining individual autonomy. Through a detailed examination, we identify the Collaborative SoS nature of the current healthcare system as the primary cause of its fragmentation. We address a gap in the current literature on the characteristics of SoS, focusing on the often‐overlooked aspect of dependence and exploring why constituent systems collaborate to achieve common objectives. Then, we propose a hybrid SoS model where an external governing entity at the national level assumes the authority to determine objectives and drivers for the healthcare SoS. We contend that effective SoS governance is indispensable for addressing systemic issues, providing necessary coordination, allocating resources, establishing policies, fostering sustainable change, and ensuring a well‐organized and efficient healthcare system.
An Agent‐Based Ontology to Support Modeling of Socio‐Technical Systems‐of‐Systems
Authors: Axelsson Jakob 
Published: September 2024

AbstractSystems‐of‐systems are characterized by the independence of their constituent elements. Such an element is usually socio‐technical, comprising technology, humans, or organizations. To capture its independence, it needs to be viewed as an intelligent agent that relies on an internal model of the world for its decision‐making. Hence, a system‐of‐systems model will include multiple agents that inside themselves contain different models of the same system‐of‐systems. Describing these overlapping subjective models and their usage by the agents is essential to properly understand the resulting behavior of the overall system‐of‐systems. Current modeling practices are not well suited for dealing with this, and the paper therefore outlines an ontology that makes the agents and their internal models more explicit. The paper also discusses the implications such models have on systems engineering practices and how they address known system‐of‐systems engineering pain points.
Darth Vader's Secret Weapon: Implementing Mission Engineering with UAF
Authors: Gagliardi Matthew , Hause Matthew C , Martin James N , Phillips Mark A 
Published: September 2024

AbstractWhen planning and conducting a Mission Engineering (ME) study, it is important to have a complete, correct, and coherent model of the mission architecture. The Unified Architecture Framework (UAF) has been found to be effective for this purpose. The OUSD (R&E) Mission Integration office is exploring how to use UAF for their ME architectures. This paper will explore some of the required modeling features and constructs that will enable this to occur. The paper “Implementing Mission Engineering with UAF” was presented at a previous conference and this paper will expand on that presentation and will discuss additional work that has been accomplished since then. This paper will also explore the proposed extensions for UAF to better support ME. We created a prototype model using the Battle of Hoth from Star Wars as a proof of concept for these modeling extensions and used the process and ME concepts defined in the Mission Engineering Guide (MEG). Since then there have been several concepts that were explored such as compatibility with the Model‐Based Acquisition (MBAcq) approach, recent initiatives from the Office of the Assistant Secretary of Defense for Mission Capabilities, Enterprise Systems Engineering (ESE) process and methods, detailed resource engagement, use of different modeling languages (e.g., Systems Modeling Language (SysML), SysML v2 and UAF v2), Effects and Outcomes, variety of measures, additional attributes/stereotypes such as differentiation between enemy/friendly/neutral ‐ Blue Force, Red Force, etc., provenance/confidence of enemy resources, and so forth. This paper will summarize the research and modeling done to date and explore these additional concepts as well as new ideas introduced in the MEG v2.
Human Frailties: Springboard to Increased Systems Engineering Influence
Authors: Arnold Eileen Patrice , McKinney Dorothy 
Published: September 2024

AbstractOne responsibility of systems engineers is to improve the quality of project decision‐making. Systems engineers often struggle to deal effectively with key decision‐makers who ignore critically important information. It is easy to bemoan human limitations, but in this paper, we advocate something different: using human frailties for constructive purposes. We believe that it is possible to leverage human frailties to ethically increase the influence that systems engineers have on key decision‐makers. Advertisers have been using human frailties for their own purposes for centuries, and we think it is time for systems engineers to capitalize on strategies advertisers and other influencers use successfully. In this paper, we identify the human frailties which have the greatest potential leverage to increase the influence systems engineers can have on key decision‐makers and suggest specific strategies and tactics systems engineers can use to increase their positive impact.
Introduction of Systems Engineering practices in a Product Lifecycle Management (PLM) course for master students
Authors: Sutinen Krister 
Published: September 2024

AbstractThis paper presents how a model‐based system engineering approach was used to introduce to master students the strength of and the challenges with a Product Lifecycle Management (PLM) system. The students were introduced to use various authoring applica?ons to build the product content to be managed by a PLM system.
Model‐Based Switching Costs
Authors: Zhu Haifeng , Hemenway Joseph M. , Wang Grant , Agarwal Naval K. 
Published: September 2024

AbstractIn product development, rarely a product is developed from scratch. In many cases, a product is developed from a prior design or several prior designs. The associated development cost is actually a switching cost (or some called reuse cost), representing the cost incurred from developing the product from prior designs. So far, no proven works in switching cost estimation were found for products developed using MBSE (Model‐Based Systems Engineering). Today, MBSE is being widely adopted. It is important to develop switching cost estimation methods that leverage models and support model‐based development needs. This paper, per the best of our knowledge, is among the firsts that developed switching cost methods for MBSE. Our work identifies different use case scenarios/phases in an MBSE development cycle, and provides corresponding switching cost estimation methods, laying down the fundamental methodology for the model‐based switching cost estimations. Using SysML, an example use case of derivative airplane electrical power system is used to demonstrate the effectiveness of our methods.
LEVERAGING MBSE USAGE THROUGH MODEL CHECKERS
Authors: MASSON Davy , Olejarz Lucas 
Published: September 2024

AbstractSystem modeling is an essential part of the systems engineering process, helping with the design, analysis, and communication of complex systems. The usage of modeling languages like SysML and UML has become increasingly prevalent in this domain. To ensure the “3C” of validation of these models (correctness, completeness and consistency), model checkers play an important aspect.This paper discusses the role of model checkers in the validation of system models, and their importance in adopting MBSE approach with a quick benefit to system engineers. Different possible implementations are presented including one based on an ontology able to take advantage of semantic analyses. Finally, in order to deal with the number of issues due to the complexity of our models, we suggest correcting them regarding the goal of the model and the project milestones. This last point implies the need of an issue acknowledgement feature making it possible to justify the temporary or definitive rejection of these issues.
Requirement Discovery Using Embedded Knowledge Graph with ChatGPT
Authors: VanGundy Braxton , Phojanamongkolkij Nipa , Brown Barclay , Polavarapu Ramana , Bonner Joshua 
Published: September 2024

AbstractThe field of Advanced Air Mobility (AAM) is witnessing a transformation with innovations such as electric aircraft and increasingly automated airspace operations. Within AAM, the Urban Air Mobility (UAM) concept focuses on providing air‐taxi services in densely populated urban areas. This research introduces the utilization of Large Language Models (LLMs), such as OpenAI's GPT‐4, to enhance the UAM Requirement discovery process.This study explores two distinct approaches to leverage LLMs in the context of UAM Requirement discovery. The first approach evaluates the LLM's ability to provide responses without relying on additional outside systems, such as a relational or graph database. Instead, a vector store provides relevant information to the LLM based on the user's question, a process known as Retrieval Augmented Generation (RAG). The second approach integrates the LLM with a graph database. The LLM acts as an intermediary between the user and the graph database, translating user questions into cypher queries for the database and database responses into human‐readable answers for the user. Our team implemented and tested both solutions to analyze requirements within a UAM dataset. This paper will talk about our approaches, implementations, and findings related to both approaches.
Outcomes and Perspectives from the 4th ESA ModelBased Space Systems and Software Engineering Workshop (MBSE2023) on reducing the gap between model‐based systems engineering and domain‐specific approaches
Authors: Christofi Nikolena , Fischer Nils , Chami Mohammad , Horvath Akos , Jung Andreas , De Roquemaurel Marie , Dissaux Pierre , Morlet Catherine , Maleki Elaheh , Verhoef Marcel 
Published: September 2024

AbstractIn the context of its initiative to promote the adoption of model‐based approaches in the development of present and upcoming missions, the European Space Agency (ESA) organised this year its annual workshop on Model‐Based Space Systems and Software Engineering (MBSE2023) at its European Space Research and Technology Centre (ESTEC) premises. The aim of this year's workshop was to investigate how the model‐based systems engineering community could contribute to bridging the gap with domain‐specific model‐based approaches used in subsystem design. The World Café Method was used to facilitate the group discussions, the outcomes of which are summarized and presented in this paper.
Configuration Management of Sets of Links in a Federated Tool Environment
Authors: D'Souza Adriana , Hetherington David , Kulcsár Géza , Orozco Bryan , Przybyło Aleksander , Ráth István 
Published: September 2024

AbstractIn the era of document‐centric systems engineering, large organizations developing complex systems had practical methods of associating drawings, specifications, requirements and other information with each other. Mostly these evolved methods involved part numbers and drawing numbers, although sometimes the methods included mundane techniques such as storing drawings in specific drawers in specific filing cabinets. These manual methods were very labor intensive, did not handle changes gracefully, and were somewhat error prone. As computer software and modeling tools began to displace paper drawings and filing cabinets, a “connect and forget” style of linking evolved. We can see this sort of thinking in the relationships in UML and SysML, but also in other places such as the use of Universally unique identifiers (UUIDs) in the XMI file format underlying UML/SysML, the relationships in DOORS and related requirements tools, as well as the original architecture of OSLC which depended on URIs embedded in design artifacts to establish relationships. While these “click to connect” features provided increased convenience compared to the previous manual numbering approaches, these “hard‐coded” links have introduced a new set of problems. The root of most of the new problems comes in the difficulty of managing this sort of extremely large set of direct links as configuration items in their own right. In a larger system, this sort of link set quickly grows to thousands or even millions of links. Managing change, modularity, variants, subsystem reuse, and so on all become very difficult in the presence of such a large, unplanned, and uncontrolled link set. In this paper, we will review the different approaches to creating and managing such sets of links and provide a concise best practices recommendation for the configuration management of such sets of links.
EVALUATING AUTOMOTIVE SPICE® AS PROCESS REQUIREMENTS
Authors: Frank Jan 
Published: September 2024

AbstractSoftware and Systems engineering projects in the Automotive industry are often mandated to develop according to the Automotive SPICE® standard. Despite a highly qualified workforce, many projects or organizations fail to implement compliant processes. This paper reinterprets the Automotive SPICE® standard, viewing its base practices as process requirements. Using a set of quality criteria for requirements, the subsequent evaluation of base practices for quality results in an aggregate and individual analysis of the ASPICE base practices. The analyses reveal, amongst others, deficiencies in the aspects of singularity, unambiguity, and reasoning structure. The paper proposes a public, collaborative effort to enrich the requirements with purpose, detail, and structure.
A Configuration Management Strategy for Modelbased Product Line Engineering in Aircraft Systems Development
Authors: Epp Jordan , Robert Thomas , Ruch Olivier , Olechowski Alison 
Published: September 2024

AbstractAircraft systems development is complex and time‐consuming. Model‐based Product Line Engineering (MBPLE) aims to reuse assets between projects to accelerate the development of systems at their early stage. Despite guidance from standards, MBPLE practitioners still face the challenge of deploying an appropriate configuration management strategy. This paper presents and demonstrates a configuration management strategy to support practitioners deploying MBPLE for aircraft systems development. We developed this strategy to comply with ISO/IEC 26580 and address pending standard ambiguities using best practices from product lines for systems, software, business processes, and systems of systems. The proposed strategy supports long‐term product line evolution, management of different asset types, and independent product environments.
MBSE for Real World Teams
Authors: Hetherington David , Hoehne Oliver , Roques Pascal , Kuriyama Junji , Nishimura Takashi 
Published: September 2024

AbstractWith the release of the OMG Systems Modeling Language (SysML) (Object Management Group, 2007) there was a surge of enthusiasm for model‐based systems engineering (MBSE). Expectations were high. Cumbersome, fragmented documents would be completely replaced by coherent, fully integrated models. The models would serve as the “Single Version of the Truth” (later transitioning to models being part of the “Authoratative Source of Truth”).While progress has been made, this utopian vision has largely failed to materialize. Certainly tool and language limitations have been a factor. However, the bigger factor in many communities has been human factors challenges. In our enthusiasm to propagate the MBSE vision, we forgot to perform the most basic systems engineering task: stakeholder analysis. This paper will introduce some of the basic human factors issues that were overlooked. The paper will then discuss three concrete cases in which a community was struggling with the abstract, radical change approach and how the teams involved have modified this approach and tooling to make it more practical and successful for those communities. Finally, the paper will conclude with some recommendations to consider when undertaking the introduction of MBSE methods in a new community.
OMG Standard to Extend SysML to Reliability Engineering
Authors: Hecht Myron , Juknevičius Tomas , Post Kyle , Armonas Andrius 
Published: September 2024

AbstractThis paper describes a Reliability Block Diagram (RBD) Library that has been added to the Risk Analysis and Assessment Modeling Language (RAAML) version 1.1, the Object Management Group (OMG) standard for safety and reliability extensions for SysML. A discussion of relevant reliability concepts is provided followed by a description of the RBD library. An example of the library using an example system is described, followed by plans for further reliability enhancements in future versions of RAAML.
Security Interpretations and Elaborations on Systems Engineering Principles
Authors: Winstead Mark 
Published: September 2024

AbstractINCOSE's Systems Engineering Vision 2035 includes thirty‐one mentions of security as part of the vision, including security to become as foundational a perspective to system design as performance and safety. INCOSE's Systems Engineering Principles technical product published a “first set of systems principles” (Watson, et al., 2022). This paper examines interpretations of these principles for security as captured in the vision and suggests modifications and possible additional principles to see security more integrated into the systems engineering process.
Systems Architecture Meta‐Model for the MagicGrid Framework
Authors: Aleksandraviciene Aiste , Strolia Zilvinas , Morkevicius Aurelijus 
Published: September 2024

AbstractAlthough Model‐Based Systems Engineering (MBSE) might be understood and applied across diverse communities and industries differently, its fundamental principles and practices described in INCOSE Systems Engineering Handbook, are common. It is known that successful application of MBSE is impossible without a tool, language, and method as well as harmony among these three. The de‐facto standard modeling language for MBSE is Systems Modeling Language (SysML). However, SysML is only a language, and it is not aligned with terminology systems engineers use daily in their work. This paper studies SysML as the standard language to model systems, and MagicGrid as the framework to bridge the gap between Systems Engineering (SE) terminology described in the INCOSE Systems Engineering Handbook and SysML specification. It proposes a new systems engineering meta‐model to describe a common SE terminology and bind it to the SysML concepts.
Clinical features and response to immune combinations in patients with renal cell carcinoma and sarcomatoid de‐differentiation (ARON‐1 study)
Authors: Ciccarese Chiara , Büttner Thomas , Cerbone Linda , Zampiva Ilaria , Monteiro Fernando Sabino M. , Basso Umberto , Pichler Martin , Vitale Maria Giuseppa , Fiala Ondrej , Roviello Giandomenico , Kopp Ray Manneh , Carrozza Francesco , Pichler Renate , Grillone Francesco , Calabuig Esther Pérez , Zeppellini Annalisa , Küronya Zsófia , Galli Luca , Facchini Gaetano , Sunela Kaisa , Mosca Alessandra , Molina‐Cerrillo Javier , Spinelli Gian Paolo , Ansari Jawaher , Scala Alessandro , Mollica Veronica , Grande Enrique , Buti Sebastiano , Kanesvaran Ravindran , Zakopoulou Roubini , Bamias Aristotelis , Rizzo Mimma , Massari Francesco , Iacovelli Roberto , Santoni Matteo 
Published: September 2024

AbstractMetastatic renal cell carcinoma (mRCC) carrying sarcomatoid features (sRCC) has aggressive biology and poor prognosis. First‐line immunotherapy (IO)‐based combinations have improved the outcome of clear cell RCC patients, including that of sRCC. Real‐world data confirming the adequate first‐line management of sRCC is largely lacking. We investigated the clinical features and the outcome of sRCC patients treated with IO‐based combinations within the ARON‐1 study population (NCT05287464). The primary objective was to define the incidence and baseline clinical characteristics of sRCC compared with non‐sRCC patients. The secondary objective was to describe the outcome of sRCC patients based on type of first‐line treatment (IO + IO vs. IO + tyrosin kinase inhibitor [TKI]). We identified 1362 mRCC patients with IMDC intermediate or poor risk, 226 sRCC and 1136 non‐sRCC. These two subgroups did not differ in terms of baseline characteristics. The median overall survival (OS) was 26.8 months (95%CI 21.6–44.2) in sRCC and 35.3 months (95%CI 30.2–40.4) in non‐sRCC patients (p = .013). The median progression‐free survival (PFS) was longer in non‐sRCC patients compared to sRCC (14.5 vs. 12.3 months, p = .064). In patients treated with first‐line IO + TKI the median OS was 34.4 months compared to 26.4 months of those who received IO + IO (p = .729). The median PFS was 12.4 months with IO + TKI and 12.3 months with IO + IO (p = .606). In conclusion, we confirm that sRCC are aggressive tumors with poor prognosis. IO‐based combinations improve survival outcomes of sRCC patients, regardless from the type of strategy (IO + IO versus IO + TKI) adopted.
Breast cancer survival analysis in the Republic of Mauritius by age, stage at diagnosis and molecular subtype: A retrospective cohort study
Authors: Koon Sun Pat Marvin , Manraj Meera , Manraj Shyam 
Published: September 2024

AbstractBreast cancer is by far the leading cancer both in terms of incidence and mortality in the Republic of Mauritius, a Small Island Developing State (SIDS). However, few studies assessed its survival by age, stage at diagnosis and molecular subtype. We identified 1399 breast cancer cases newly diagnosed between 2017 and 2020 at the Central Health Laboratory, Victoria Hospital. Cancers were categorized into five molecular subtypes: (1) luminal A, (2) luminal B Her2 negative, (3) luminal B Her2 positive, (4) Her2 enriched and (5) Triple negative. The net 1 and 3‐year survival were estimated for different age groups, staging at time of diagnosis and molecular subtype. We also estimated the excess hazards using a multivariate Cox proportional hazards model. While early stage at diagnosis (stage 1 [44.4%] and stage 2 [20.1%]) were most common compared to late presentation (Stage 3 [25.4%] and stage 4 [10.1%]), luminal B Her2 negative (36.7%) was the most frequent molecular subtype. The net 1‐ and 3‐year breast cancer survival rates were 93.9% (92.3–95.4) and 83.4% (80.4–86.4), respectively. Breast cancer three‐year survival rates were poorest among the youngest patients (<50 years), 77.1% (70.7–83.5), those diagnosed with stage 4 (28.5% [17.1–39.9]) and cancer with a triple negative molecular subtype (71.3% [63.3–79.3]). Emphasis on a national breast cancer screening programme, down staging breast cancer at diagnosis and systematic molecular subtyping of all breast tissues could be pivotal in improving breast cancer survival outcomes in the Republic of Mauritius.