A Unified Requirements‐Architecture System Model—Development and Empirical Evaluation
Fuente:
Wiley Open Access
Guardado en:
| Autores principales: | , , |
|---|---|
| Formato: | Artículo Open Access |
| Publicado: |
Wiley
2025
|
| Materias: | |
| Acceso en línea: | |
| Etiquetas: |
Agregar Etiqueta
Sin Etiquetas, Sea el primero en etiquetar este registro!
|
| _version_ | 1867014923812339712 |
|---|---|
| author | Liat Katzir Shahaf Rocker Yoel Dov Dori |
| author_facet | Liat Katzir Shahaf Rocker Yoel Dov Dori Liat Katzir Shahaf Rocker Yoel Dov Dori |
| collection | Wiley Open Access |
| contents | A Unified Requirements‐Architecture System Model—Development and Empirical Evaluation Liat Katzir Shahaf Rocker Yoel Dov Dori Systems Engineering ABSTRACT Moving systems engineering's center of gravity from text documents to digital models, model‐based system engineering (MBSE) facilitates collaboration, reduces errors, and improves system understanding, but systems engineers often face challenges when they start working with MBSE, as they need to consider and model textual requirements as a basis for the system architecture. Synchronizing requirements with the system model can address critical questions, such as which requirements are assigned and covered in the system model, what effort is required to meet these requirements, how to manage changes to requirements, and how to effectively trace them in the system. Object Process Methodology (OPM, ISO 19450) is an MBSE language and methodology for modeling systems, which encapsulates function, structure, and behavior within a single model. The research goal is to expand the MBSE methodology by modeling requirements that are linked to system model artifacts. The objective is minimizing misunderstandings between stakeholders’ text‐based requirements and the engineered model while improving the ability to track changes in requirements and artifacts. An OPM‐based model, OPM‐R, which unifies system requirements and architecture, was developed and evaluated through (1) interviews with seven experts who compared the current text‐based approach and the proposed one based on the requirements of three test system models and (2) a researcher diary. Findings indicate that OPM‐R is preferred over the text‐based approach, as it reduces misunderstandings and gaps in requirements, enhancing the ability to trace coverage of system artifacts and track changes in requirements. 10.1002/sys.70035 http://creativecommons.org/licenses/by/4.0/ |
| doi_str_mv | 10.1002/sys.70035 |
| format | Artículo Open Access |
| id | wiley_oa_10_1002_sys_70035 |
| institution | Wiley Open Access |
| license_str_mv | http://creativecommons.org/licenses/by/4.0/ |
| publishDate | 2025 |
| publisher | Wiley |
| record_format | wiley_oa |
| spellingShingle | A Unified Requirements‐Architecture System Model—Development and Empirical Evaluation Liat Katzir Shahaf Rocker Yoel Dov Dori Systems Engineering A Unified Requirements‐Architecture System Model—Development and Empirical Evaluation Liat Katzir Shahaf Rocker Yoel Dov Dori Systems Engineering ABSTRACT Moving systems engineering's center of gravity from text documents to digital models, model‐based system engineering (MBSE) facilitates collaboration, reduces errors, and improves system understanding, but systems engineers often face challenges when they start working with MBSE, as they need to consider and model textual requirements as a basis for the system architecture. Synchronizing requirements with the system model can address critical questions, such as which requirements are assigned and covered in the system model, what effort is required to meet these requirements, how to manage changes to requirements, and how to effectively trace them in the system. Object Process Methodology (OPM, ISO 19450) is an MBSE language and methodology for modeling systems, which encapsulates function, structure, and behavior within a single model. The research goal is to expand the MBSE methodology by modeling requirements that are linked to system model artifacts. The objective is minimizing misunderstandings between stakeholders’ text‐based requirements and the engineered model while improving the ability to track changes in requirements and artifacts. An OPM‐based model, OPM‐R, which unifies system requirements and architecture, was developed and evaluated through (1) interviews with seven experts who compared the current text‐based approach and the proposed one based on the requirements of three test system models and (2) a researcher diary. Findings indicate that OPM‐R is preferred over the text‐based approach, as it reduces misunderstandings and gaps in requirements, enhancing the ability to trace coverage of system artifacts and track changes in requirements. 10.1002/sys.70035 http://creativecommons.org/licenses/by/4.0/ |
| title | A Unified Requirements‐Architecture System Model—Development and Empirical Evaluation |
| topic | Systems Engineering |
| url | https://incose.onlinelibrary.wiley.com/doi/10.1002/sys.70035 |