{"title":"The impact of system representation choices on architecting insights","authors":"Anthony Hennig, Z. Szajnfarber","doi":"10.1002/sys.21673","DOIUrl":null,"url":null,"abstract":"Systems engineers regularly rely on analysis of early design artifacts like system architecture representations to predict system performance, lifecycle costs, and development schedules, and to support design decision‐making. Recent recognition of challenges in this type of measurement has led to a heightened focus on developing better metrics. Less attention has been paid to the system representations upon which all subsequent analysis is performed. With this study, we demonstrate that choices about how to represent the system can explain variation in measurement, even holding metrics constant. This is important because most of these representation choices remain unarticulated in current practice. To do this, we conduct a controlled experiment where we experimentally manipulated the Design Structure Matrix (DSM) architecture representation of nine crowdsourced robotic arm designs and compared the value and relative ranks of their modularity and complexity. We found statistically significant changes in both value and rank, attributable to differences in choices in the system representation. The direction and magnitude of these changes also differed across modularity and complexity. In addition, some underlying designs seemed to be more robust to representation changes. This suggests an interaction between representation, design, and lifecycle properties. These results emphasize the importance of developing standard guidelines for how to represent system architectures and better documenting their use.","PeriodicalId":54439,"journal":{"name":"Systems Engineering","volume":null,"pages":null},"PeriodicalIF":1.6000,"publicationDate":"2023-03-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Systems Engineering","FirstCategoryId":"5","ListUrlMain":"https://doi.org/10.1002/sys.21673","RegionNum":3,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q4","JCRName":"ENGINEERING, INDUSTRIAL","Score":null,"Total":0}
引用次数: 0
Abstract
Systems engineers regularly rely on analysis of early design artifacts like system architecture representations to predict system performance, lifecycle costs, and development schedules, and to support design decision‐making. Recent recognition of challenges in this type of measurement has led to a heightened focus on developing better metrics. Less attention has been paid to the system representations upon which all subsequent analysis is performed. With this study, we demonstrate that choices about how to represent the system can explain variation in measurement, even holding metrics constant. This is important because most of these representation choices remain unarticulated in current practice. To do this, we conduct a controlled experiment where we experimentally manipulated the Design Structure Matrix (DSM) architecture representation of nine crowdsourced robotic arm designs and compared the value and relative ranks of their modularity and complexity. We found statistically significant changes in both value and rank, attributable to differences in choices in the system representation. The direction and magnitude of these changes also differed across modularity and complexity. In addition, some underlying designs seemed to be more robust to representation changes. This suggests an interaction between representation, design, and lifecycle properties. These results emphasize the importance of developing standard guidelines for how to represent system architectures and better documenting their use.
期刊介绍:
Systems Engineering is a discipline whose responsibility it is to create and operate technologically enabled systems that satisfy stakeholder needs throughout their life cycle. Systems engineers reduce ambiguity by clearly defining stakeholder needs and customer requirements, they focus creativity by developing a system’s architecture and design and they manage the system’s complexity over time. Considerations taken into account by systems engineers include, among others, quality, cost and schedule, risk and opportunity under uncertainty, manufacturing and realization, performance and safety during operations, training and support, as well as disposal and recycling at the end of life. The journal welcomes original submissions in the field of Systems Engineering as defined above, but also encourages contributions that take an even broader perspective including the design and operation of systems-of-systems, the application of Systems Engineering to enterprises and complex socio-technical systems, the identification, selection and development of systems engineers as well as the evolution of systems and systems-of-systems over their entire lifecycle.
Systems Engineering integrates all the disciplines and specialty groups into a coordinated team effort forming a structured development process that proceeds from concept to realization to operation. Increasingly important topics in Systems Engineering include the role of executable languages and models of systems, the concurrent use of physical and virtual prototyping, as well as the deployment of agile processes. Systems Engineering considers both the business and the technical needs of all stakeholders with the goal of providing a quality product that meets the user needs. Systems Engineering may be applied not only to products and services in the private sector but also to public infrastructures and socio-technical systems whose precise boundaries are often challenging to define.