Multidisciplinary knowledge and exchange of information are two of the most important aspects of complex system design within digital engineering and model-based systems engineering (MBSE) environments. The next generation of systems modeling language, SysML v2, developed by the Object Management Group, improves the implementation and maturation of model-based approaches. This article focuses on using SysML v2 to model reusable parameterized templates for nonfunctional requirements, referred to as -ilities, to address how they can be treated with the same rigor as functional requirements and mapped directly and explicitly from the requirements engineering phase within digital engineering and MBSE environments. The selected set of -ilities are safety, human system integration, and cybersecurity. The rationale for this selection is based on past studies that have documented the need to evaluate safety risks that involve humans in the loop and cybersecurity considerations. The metamodel design uses SysML v2 syntax to compile general characteristics for -ilities, with an application to a digital twin complex system architecture model to demonstrate an instantiation within Digital Engineering and MBSE environments. The resulting metamodel is composed of SysML v2 parameterized requirements constructs, notations for analysis and verification, and relationships that can be generalized to other -ilities with implementation steps aligned with ISO/IEC/IEEE 29148, the standard for systems and software requirements engineering. These contributions lower the barrier of adoption for SysMLv2, support the standard and consistent modeling within the MBSE domain, and advance multidisciplinary analysis.
Pacifique Munezero, Holly A. H. Handley· IEEE Open Journal of Systems...· 0 citations
The intent of this paper publication is to address Software (SW) Safety Architecture Analysis and to provide an approach for conducting the architecture analysis Level of Rigor task utilizing software architecture patterns. While there are many architecture analysis techniques commonly used in practice today (e.g., Architecture Tradeoff Analysis Method (ATAM), Software Architecture Analysis Method (SAAM), Scenario based Architecture Level UsabiliTy Analysis (SALUTA), etc.), they seem to concentrate on the architecture of the system rather than the structure of the system’s software. By analyzing software architecture patterns, the safety practitioner can pay close attention to the true architecture of the software. The methodology described within further details the safety concerns associated with each of the patterns. The general safety concerns are stability/robustness, data handling, maintainability, testability, and security. Each of these concerns are broken down to more specificity in the brief. By identifying the software architecture pattern(s) employed in a system and understanding the safety concerns and potential mitigations, system safety practitioners have a basis for an in-depth, repeatable software architecture analysis methodology.
Myesha Dabney, Carla Adams, LaTasha Bagby et al.· Journal of System Safety· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.