Diana Gómez, Juan Cubillos, Jairo Aponte, Edward Rojas
Effort estimation is fundamental for developing software projects and critical for their success. This paper focuses on how Colombian agile practitioners perform effort estimates in agile projects. For this purpose, we conducted an exploratory survey study that involved 60 respondents. The main findings are the following: (1) Agile practitioners prefer estimation techniques based on Expert Judgement. (2) Most of the respondents perceive that their estimates have a medium accuracy level. (3) The determining effort drivers are features of the project team and the software to be built. (4) The use of datasets for estimation is not common. (5) Most of the results of related studies are similar to ours, with differences in terms of the roles involved and the techniques used.
{"title":"Effort Estimation in Agile Software Development: The State of the Practice in Colombia","authors":"Diana Gómez, Juan Cubillos, Jairo Aponte, Edward Rojas","doi":"10.2139/ssrn.4149549","DOIUrl":"https://doi.org/10.2139/ssrn.4149549","url":null,"abstract":"Effort estimation is fundamental for developing software projects and critical for their success. This paper focuses on how Colombian agile practitioners perform effort estimates in agile projects. For this purpose, we conducted an exploratory survey study that involved 60 respondents. The main findings are the following: (1) Agile practitioners prefer estimation techniques based on Expert Judgement. (2) Most of the respondents perceive that their estimates have a medium accuracy level. (3) The determining effort drivers are features of the project team and the software to be built. (4) The use of datasets for estimation is not common. (5) Most of the results of related studies are similar to ours, with differences in terms of the roles involved and the techniques used.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114313659","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}
Clone detection provides insight about replicated fragments in a code base. With the rise of multi-language code bases, new techniques addressing cross-language code clone detection enable the analysis of polyglot systems. Such techniques have not yet been applied to the mobile apps’ domain, which are naturally polyglot. Native mobile app developers must synchronize their code base in at least two different programming languages. App synchronization is a difficult and time-consuming maintenance task, as features can rapidly diverge between platforms, and feature identification must be performed manually. Our goal is to provide an analysis framework to reduce the impact of app synchronization. A first step in this direction consists on a structural algorithm for cross-language clone detection exploiting the idea behind enriched concrete syntax trees. Such trees are used as a common intermediate representation built from programming languages’ grammars, to detect similarities between app code bases. Our technique finds code similarities with 79% precision for controlled tests where Type 1-3 clones are manually injected for the analysis of both single- and cross-language cases for Kotlin and Dart. We evaluate our tool on a corpus of 52 mobile apps identifying code similarities with a precision of 65% to 84% for the full application logic.
{"title":"Cross-language Clone Detection for Mobile Apps","authors":"Stephannie Jimenez, Gordana Rakic, Silvia Takahashi, Nicolás Cardozo","doi":"10.5753/cibse.2023.24696","DOIUrl":"https://doi.org/10.5753/cibse.2023.24696","url":null,"abstract":"Clone detection provides insight about replicated fragments in a code base. With the rise of multi-language code bases, new techniques addressing cross-language code clone detection enable the analysis of polyglot systems. Such techniques have not yet been applied to the mobile apps’ domain, which are naturally polyglot. Native mobile app developers must synchronize their code base in at least two different programming languages. App synchronization is a difficult and time-consuming maintenance task, as features can rapidly diverge between platforms, and feature identification must be performed manually. Our goal is to provide an analysis framework to reduce the impact of app synchronization. A first step in this direction consists on a structural algorithm for cross-language clone detection exploiting the idea behind enriched concrete syntax trees. Such trees are used as a common intermediate representation built from programming languages’ grammars, to detect similarities between app code bases. Our technique finds code similarities with 79% precision for controlled tests where Type 1-3 clones are manually injected for the analysis of both single- and cross-language cases for Kotlin and Dart. We evaluate our tool on a corpus of 52 mobile apps identifying code similarities with a precision of 65% to 84% for the full application logic.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"86 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126254298","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-04-24DOI: 10.5753/cibse.2023.24703
Ana J. Almeida, Jácome Cunha, J. Fernandes
Although remote work was already possible and used in some contexts, the COVID-19 pandemic made it normal and, in some situations, even mandatory. This was the case in Portugal and in particular in its software industry. Given this abrupt change in how we work, it became pressing to investigate the impacts of this profound change to remote work, so that we can cope with the potential negative consequences (professional, personal, etc.). Thus, the goal of this work is to study the impact of the referred change to remote work, due to the COVID-19 pandemic, on software professionals in Portugal. To achieve this goal, a survey was prepared and distributed via email, LinkedIn, and Instagram. In total, 176 valid answers were collected from software professionals working in Portugal from 38 different companies. After the performed statistical analysis on the targeted population and focusing on the 10 elaborated research questions, two major findings can be concluded with certainty: (i) having worked in a remote regime before the pandemic period has a strong relationship with a higher frequency of use of teleconference tools after this period, and (ii) participants who do not feel safe about coming back to a fully on-site regime are more likely to prefer a fully remote regime than the ones who feel safe, while the latter group is more likely to prefer a hybrid regime.
{"title":"Impact of remote work on Portuguese software professionals during the COVID-19 pandemic","authors":"Ana J. Almeida, Jácome Cunha, J. Fernandes","doi":"10.5753/cibse.2023.24703","DOIUrl":"https://doi.org/10.5753/cibse.2023.24703","url":null,"abstract":"Although remote work was already possible and used in some contexts, the COVID-19 pandemic made it normal and, in some situations, even mandatory. This was the case in Portugal and in particular in its software industry. Given this abrupt change in how we work, it became pressing to investigate the impacts of this profound change to remote work, so that we can cope with the potential negative consequences (professional, personal, etc.). Thus, the goal of this work is to study the impact of the referred change to remote work, due to the COVID-19 pandemic, on software professionals in Portugal. To achieve this goal, a survey was prepared and distributed via email, LinkedIn, and Instagram. In total, 176 valid answers were collected from software professionals working in Portugal from 38 different companies. After the performed statistical analysis on the targeted population and focusing on the 10 elaborated research questions, two major findings can be concluded with certainty: (i) having worked in a remote regime before the pandemic period has a strong relationship with a higher frequency of use of teleconference tools after this period, and (ii) participants who do not feel safe about coming back to a fully on-site regime are more likely to prefer a fully remote regime than the ones who feel safe, while the latter group is more likely to prefer a hybrid regime.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"202 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124001508","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-04-24DOI: 10.5753/cibse.2023.24707
A. Cordeiro
Experimentation in Software Engineering has increased in the last decades as a way to provide evidence on theories and technologies. In a controlled experiment life cycle, several artifacts are used/reused and even produced. Such artifacts are mostly in the form of data, which should favor the reproducibility of such experiments. In this context, reproducibility can be defined as the ability to reproduce a study. Different benefits, such as methodology and data reuse, can be achieved from this ability. Despite the recognized benefits, several challenges have been faced by researchers regarding the experiments’ reproducibility capability. To overcome them, we understand that Open Science practices, related to provenance, preservation, and curation, might aid in improving such a capability. Therefore, in this paper, we present the proposal for an open science-based Framework to deal with controlled experiment research artifacts towards making such experiments de facto reproducible. To do so, different models associated with open science practices are planned to be integrated into the Framework.
{"title":"Towards a Framework Based on Open Science Practices for Promoting Reproducibility of Software Engineering Controlled Experiments","authors":"A. Cordeiro","doi":"10.5753/cibse.2023.24707","DOIUrl":"https://doi.org/10.5753/cibse.2023.24707","url":null,"abstract":"Experimentation in Software Engineering has increased in the last decades as a way to provide evidence on theories and technologies. In a controlled experiment life cycle, several artifacts are used/reused and even produced. Such artifacts are mostly in the form of data, which should favor the reproducibility of such experiments. In this context, reproducibility can be defined as the ability to reproduce a study. Different benefits, such as methodology and data reuse, can be achieved from this ability. Despite the recognized benefits, several challenges have been faced by researchers regarding the experiments’ reproducibility capability. To overcome them, we understand that Open Science practices, related to provenance, preservation, and curation, might aid in improving such a capability. Therefore, in this paper, we present the proposal for an open science-based Framework to deal with controlled experiment research artifacts towards making such experiments de facto reproducible. To do so, different models associated with open science practices are planned to be integrated into the Framework.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"182 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132958953","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-04-24DOI: 10.5753/cibse.2023.24693
F. G. Rocha, M. S. Soares, Guillermo Rodríguez
Microservices emerged due to the massive adoption of cloud computing and the need to integrate legacy systems. However, there still needs to be a greater understanding of adopting a microservice-based architectural style. Besides, there is a need for guidelines to operationalize those microservices. We conducted a grey literature review to identify commonly used architectural patterns and how they are implemented following design patterns. We present two key contributions. Firstly, we identified four architectural patterns and 23 design patterns. Secondly, we identified a catalog of tools for implementing the main patterns adopted when using the microservices style. The Proxy and the SAGA patterns are the most used in communicating and linking data for services. Additionally, tools such as Kubernetes, Docker, and Amazon WS are the most used for implementing microservices and deploying them into containers.
{"title":"Patterns in Microservices-based Development: A Grey Literature Review","authors":"F. G. Rocha, M. S. Soares, Guillermo Rodríguez","doi":"10.5753/cibse.2023.24693","DOIUrl":"https://doi.org/10.5753/cibse.2023.24693","url":null,"abstract":"Microservices emerged due to the massive adoption of cloud computing and the need to integrate legacy systems. However, there still needs to be a greater understanding of adopting a microservice-based architectural style. Besides, there is a need for guidelines to operationalize those microservices. We conducted a grey literature review to identify commonly used architectural patterns and how they are implemented following design patterns. We present two key contributions. Firstly, we identified four architectural patterns and 23 design patterns. Secondly, we identified a catalog of tools for implementing the main patterns adopted when using the microservices style. The Proxy and the SAGA patterns are the most used in communicating and linking data for services. Additionally, tools such as Kubernetes, Docker, and Amazon WS are the most used for implementing microservices and deploying them into containers.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129105870","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-04-24DOI: 10.5753/cibse.2023.24697
Everton Cavalcante, T. Batista
Architectural smells are decisions made at the software architecture level, whether intentional or not, that may negatively impact the quality of a software system. In the literature, architectural smells are identified mainly by relying on the source code or other implementation artifacts. However, architectural smells could be detected at design time, even before employing implementation efforts and preventing them from being reflected at the system implementation. This research investigates how software architecture descriptions realized through architecture description languages (ADLs) can be used to identify architectural smells at design time. This work focuses on how architectural smells manifest and can be detected in SysADL, an ADL that allows describing both structure and behavior of software architectures using standardized diagrams from the OMG’s SysML language.
{"title":"Using Software Architecture Descriptions to Detect Architectural Smells at Design Time","authors":"Everton Cavalcante, T. Batista","doi":"10.5753/cibse.2023.24697","DOIUrl":"https://doi.org/10.5753/cibse.2023.24697","url":null,"abstract":"Architectural smells are decisions made at the software architecture level, whether intentional or not, that may negatively impact the quality of a software system. In the literature, architectural smells are identified mainly by relying on the source code or other implementation artifacts. However, architectural smells could be detected at design time, even before employing implementation efforts and preventing them from being reflected at the system implementation. This research investigates how software architecture descriptions realized through architecture description languages (ADLs) can be used to identify architectural smells at design time. This work focuses on how architectural smells manifest and can be detected in SysADL, an ADL that allows describing both structure and behavior of software architectures using standardized diagrams from the OMG’s SysML language.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"333 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114722004","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-04-24DOI: 10.5753/cibse.2023.24691
Fernanda Papa, Pablo Becker, L. Olsina
The present paper deals with an exploratory study on the terminological consistency of four selected project management glossaries. To systematically carry out the study, eight activities were established. Regarding the information consistency sub-characteristic, this work includes a comparison and analysis of both the syntactic and semantic consistency of the terms in the glossaries. To do this, nine terminological categories were conceived for the project area, in which, for each glossary, a given term is included in a category, considering the semantics intended in the definition of the term by the authors. This categorization of terms allows us to comparatively analyze syntactic and semantic similarities, and in turn consistencies and inconsistencies. As a final goal, this study will help us examine our previously developed project ontology and recommend adoptions and adaptations.
{"title":"Exploring Terminological Consistency of Project Management Glossaries","authors":"Fernanda Papa, Pablo Becker, L. Olsina","doi":"10.5753/cibse.2023.24691","DOIUrl":"https://doi.org/10.5753/cibse.2023.24691","url":null,"abstract":"The present paper deals with an exploratory study on the terminological consistency of four selected project management glossaries. To systematically carry out the study, eight activities were established. Regarding the information consistency sub-characteristic, this work includes a comparison and analysis of both the syntactic and semantic consistency of the terms in the glossaries. To do this, nine terminological categories were conceived for the project area, in which, for each glossary, a given term is included in a category, considering the semantics intended in the definition of the term by the authors. This categorization of terms allows us to comparatively analyze syntactic and semantic similarities, and in turn consistencies and inconsistencies. As a final goal, this study will help us examine our previously developed project ontology and recommend adoptions and adaptations.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126426896","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-04-24DOI: 10.5753/cibse.2023.24706
Larissa Mangolim Amaral, A. Brandão, F. Siqueira
Requirements languages are often defined as metamodels for the standardization of a system’s requirements specification. The unification of these metamodels benefits general analysis and interoperability between requirements models. Even tough some authors already discuss systematic composition approaches, this application for requirements languages’ metamodels is still little explored. Therefore, we applied non-domain-specific composition frameworks to create a unified metamodel for User Story and Use Case diagram by assessing common points in related work. This application enabled reducing the subjectivity of the requirements languages composition process but still strongly depended on human curation.
{"title":"Using Metamodel Composition to Unify User Story and Use Case Metamodels","authors":"Larissa Mangolim Amaral, A. Brandão, F. Siqueira","doi":"10.5753/cibse.2023.24706","DOIUrl":"https://doi.org/10.5753/cibse.2023.24706","url":null,"abstract":"Requirements languages are often defined as metamodels for the standardization of a system’s requirements specification. The unification of these metamodels benefits general analysis and interoperability between requirements models. Even tough some authors already discuss systematic composition approaches, this application for requirements languages’ metamodels is still little explored. Therefore, we applied non-domain-specific composition frameworks to create a unified metamodel for User Story and Use Case diagram by assessing common points in related work. This application enabled reducing the subjectivity of the requirements languages composition process but still strongly depended on human curation.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115240969","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-04-24DOI: 10.5753/cibse.2023.24695
Nicolas Robles, Nicolás Potes, Kelly Garcés, Javier Luis Cánovas Izquierdo, Jordi Cabot
The software industry is in continuous evolution, forcing developers to quickly adapt to new requirements to catch up with the latest trends. A clear example is the huge demand for web-based APIs to connect all kinds of services among them. Like any other piece of software, a Web API is continuously changing, and with each change, all client applications must evolve. This adaptation process is critical and essential for software developers. In this paper, we present an exploratory evaluation of the most common changes occurring during the evolution of REST APIs. We define a taxonomy of structural API changes, which we classify according to their impact on client-side software; and propose a repository mining process to identify these changes in real Web APIs. We apply this process to a large set of Azure APIs from APISGURU, a well-known Open Source API repository. Based on the analyzed dataset from APISGURU, we found that breaking changes tend to decrease when a new version of an API from this dataset is released. Other useful findings and insights are discussed throughout the article.
{"title":"Exploratory Analysis of the Structural Evolution of public REST APIs","authors":"Nicolas Robles, Nicolás Potes, Kelly Garcés, Javier Luis Cánovas Izquierdo, Jordi Cabot","doi":"10.5753/cibse.2023.24695","DOIUrl":"https://doi.org/10.5753/cibse.2023.24695","url":null,"abstract":"The software industry is in continuous evolution, forcing developers to quickly adapt to new requirements to catch up with the latest trends. A clear example is the huge demand for web-based APIs to connect all kinds of services among them. Like any other piece of software, a Web API is continuously changing, and with each change, all client applications must evolve. This adaptation process is critical and essential for software developers. In this paper, we present an exploratory evaluation of the most common changes occurring during the evolution of REST APIs. We define a taxonomy of structural API changes, which we classify according to their impact on client-side software; and propose a repository mining process to identify these changes in real Web APIs. We apply this process to a large set of Azure APIs from APISGURU, a well-known Open Source API repository. Based on the analyzed dataset from APISGURU, we found that breaking changes tend to decrease when a new version of an API from this dataset is released. Other useful findings and insights are discussed throughout the article.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115252248","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-04-24DOI: 10.5753/cibse.2023.24701
René Noël, José Ignacio Panach, Óscar Pastor
Model-driven techniques for designing strategically aligned information systems usually map the goals of multiple and competing actors to business process models through automatic model-to-model transformations and analysis. In previous work, we designed Stra2Bis, a method for designing strategically aligned business processes based on a different approach: mapping the business strategy and organisation structure into the business process model. Stra2Bis and goal-based techniques share an issue: only some organisational level elements actors directly affect the business domain and, thus, the business processes. In this article, we propose to extend Stra2Bis by adding concepts from Team Topologies, an approach for organising business and technology teams. Team Topologies help distinguish the business-relevant organisation units from other supporting units; we exploit these concepts to constrain the model-to-model mappings, avoiding unnecessary analysis and modelling outside the business domain. We formalise the approach by specifying the method's metamodel extension and redefining the model-to-model transformation guidelines. We also discuss how existing goal-based alignment frameworks can exploit this approach.
{"title":"Using Team Topologies in Model-Driven Strategic Alignment","authors":"René Noël, José Ignacio Panach, Óscar Pastor","doi":"10.5753/cibse.2023.24701","DOIUrl":"https://doi.org/10.5753/cibse.2023.24701","url":null,"abstract":"Model-driven techniques for designing strategically aligned information systems usually map the goals of multiple and competing actors to business process models through automatic model-to-model transformations and analysis. In previous work, we designed Stra2Bis, a method for designing strategically aligned business processes based on a different approach: mapping the business strategy and organisation structure into the business process model. Stra2Bis and goal-based techniques share an issue: only some organisational level elements actors directly affect the business domain and, thus, the business processes. In this article, we propose to extend Stra2Bis by adding concepts from Team Topologies, an approach for organising business and technology teams. Team Topologies help distinguish the business-relevant organisation units from other supporting units; we exploit these concepts to constrain the model-to-model mappings, avoiding unnecessary analysis and modelling outside the business domain. We formalise the approach by specifying the method's metamodel extension and redefining the model-to-model transformation guidelines. We also discuss how existing goal-based alignment frameworks can exploit this approach.","PeriodicalId":146286,"journal":{"name":"Conferencia Iberoamericana de Software Engineering","volume":"84 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2023-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115170342","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
扫码关注我们
求助内容：
应助结果提醒方式：