Pub Date : 2023-05-01DOI: 10.1109/sesos59159.2023.00017
{"title":"SESoS 2023 Workshop Organizers","authors":"","doi":"10.1109/sesos59159.2023.00017","DOIUrl":"https://doi.org/10.1109/sesos59159.2023.00017","url":null,"abstract":"","PeriodicalId":431555,"journal":{"name":"2023 IEEE/ACM 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems (SESoS)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124285787","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2023-05-01DOI: 10.1109/SESoS59159.2023.00010
Fang Hou, Floris M. Jansen, A. D. Vries, S. Jansen
Software selection is a critical part of any software engineering project, as projects depend on a rich ecosystem of components and frameworks. Software engineers always find it challenging to select a trustworthy software product despite the availability of a large number of software selection tools. This study explores the trust factors in open-source and closed software selection from a practitioner’s perspective, to gain insight into perceptions of software trust. To this aim, we conducted semi-structured interviews with 24 software practitioners from different businesses, including 12 experts in open-source software selection and 12 experts in closed software selection. By summarizing we found: (1) software selection is affected by three categories of factors, being technical, organizational, and structural assurance factors; (2) the most important factors are technical factors and organizational factors; and (3) software selection process and trust factors differ depending on the project risk tolerance. In addition, we compared the trust factors derived from the interviews with those found in the literature. Our findings revealed that there is a difference between the two.
{"title":"The Role of Software Trust in Selection of Open-Source and Closed Software","authors":"Fang Hou, Floris M. Jansen, A. D. Vries, S. Jansen","doi":"10.1109/SESoS59159.2023.00010","DOIUrl":"https://doi.org/10.1109/SESoS59159.2023.00010","url":null,"abstract":"Software selection is a critical part of any software engineering project, as projects depend on a rich ecosystem of components and frameworks. Software engineers always find it challenging to select a trustworthy software product despite the availability of a large number of software selection tools. This study explores the trust factors in open-source and closed software selection from a practitioner’s perspective, to gain insight into perceptions of software trust. To this aim, we conducted semi-structured interviews with 24 software practitioners from different businesses, including 12 experts in open-source software selection and 12 experts in closed software selection. By summarizing we found: (1) software selection is affected by three categories of factors, being technical, organizational, and structural assurance factors; (2) the most important factors are technical factors and organizational factors; and (3) software selection process and trust factors differ depending on the project risk tolerance. In addition, we compared the trust factors derived from the interviews with those found in the literature. Our findings revealed that there is a difference between the two.","PeriodicalId":431555,"journal":{"name":"2023 IEEE/ACM 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems (SESoS)","volume":"2402 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127478720","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2023-05-01DOI: 10.1109/SESoS59159.2023.00005
Mateus Molina, T. Treichel
This paper presents an approach to integrating Asset Administration Shells (AASs) and Model-based systems engineering (MBSE) to meet the stricter demands of Industry 4.0 plants. This integration can enable a system to gather and analyze real-world data as well as to update the system model, leading to prolonged model lifetime and increased utility. The proposed solution is a library developed using MATLAB/Simulink and BaSyx APIs, which provides a block that encapsulates the communication interface with a submodel stored inside a BaSyx AAS server. The authors used a hydraulic press simulation to validate the proposed solution and demonstrate how it can be used to implement condition monitoring capabilities.
{"title":"Achieving Interoperability with MBSE and Asset Administration Shells: Integration of MATLAB/Simulink and BaSyx","authors":"Mateus Molina, T. Treichel","doi":"10.1109/SESoS59159.2023.00005","DOIUrl":"https://doi.org/10.1109/SESoS59159.2023.00005","url":null,"abstract":"This paper presents an approach to integrating Asset Administration Shells (AASs) and Model-based systems engineering (MBSE) to meet the stricter demands of Industry 4.0 plants. This integration can enable a system to gather and analyze real-world data as well as to update the system model, leading to prolonged model lifetime and increased utility. The proposed solution is a library developed using MATLAB/Simulink and BaSyx APIs, which provides a block that encapsulates the communication interface with a submodel stored inside a BaSyx AAS server. The authors used a hydraulic press simulation to validate the proposed solution and demonstrate how it can be used to implement condition monitoring capabilities.","PeriodicalId":431555,"journal":{"name":"2023 IEEE/ACM 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems (SESoS)","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129567671","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2023-05-01DOI: 10.1109/SESoS59159.2023.00007
P. Arantes, Felipe Soupinski, A. Fontão
Software Ecosystems (SECO) depend on platforms that serve as environments for developers’ interaction. The SECO may die when the organization that owns the platform does not support the synergy between organizational goals and developers’ expectations. The death results in the suspension of vital activities, such as code development and maintenance, impacting developers who lose work, learning, and experience gained. On the other hand, the responsible corporation loses resources invested in SECO. These signs indicate a SECO death is an important event for the community and should be analyzed. This paper reports a GitHub (GH) study focusing on three web SECOs: AngularJS, PhantomJS, and MomentJS. We analyze metrics based on developer community engagement and collaboration to understand what happens in these SECOs before, during, and after the platform’s death. From the search questions, we found some directions: Users’ recruitment and permanence: Without management and engagement, communities get out of SECOS a few years after your entry, so methods to control and organize the community are needed. Community relationships: The community needs engagement to strengthen and maintain your relationships. Some types of programs are useful methods to engage and encourage users to collaborate between them.
{"title":"Social Networks during Software Ecosystems’ Death","authors":"P. Arantes, Felipe Soupinski, A. Fontão","doi":"10.1109/SESoS59159.2023.00007","DOIUrl":"https://doi.org/10.1109/SESoS59159.2023.00007","url":null,"abstract":"Software Ecosystems (SECO) depend on platforms that serve as environments for developers’ interaction. The SECO may die when the organization that owns the platform does not support the synergy between organizational goals and developers’ expectations. The death results in the suspension of vital activities, such as code development and maintenance, impacting developers who lose work, learning, and experience gained. On the other hand, the responsible corporation loses resources invested in SECO. These signs indicate a SECO death is an important event for the community and should be analyzed. This paper reports a GitHub (GH) study focusing on three web SECOs: AngularJS, PhantomJS, and MomentJS. We analyze metrics based on developer community engagement and collaboration to understand what happens in these SECOs before, during, and after the platform’s death. From the search questions, we found some directions: Users’ recruitment and permanence: Without management and engagement, communities get out of SECOS a few years after your entry, so methods to control and organize the community are needed. Community relationships: The community needs engagement to strengthen and maintain your relationships. Some types of programs are useful methods to engage and encourage users to collaborate between them.","PeriodicalId":431555,"journal":{"name":"2023 IEEE/ACM 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems (SESoS)","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124922535","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：