Jürgen Thanhofer-Pilisch, Alexander Lang, Michael Vierhauser, Rick Rabiser
Domain-specific languages (DSLs) are frequently used in software engineering. In contrast to general-purpose languages, DSLs are designed for a special purpose in a particular domain. Due to volatile user requirements and new technologies DSLs, similar to the software systems they describe or produce, are subject to continuous evolution. This work explores existing research on DSL evolution to summarize, structure and analyze this area of research, and to identify trends and open issues. We conducted a systematic mapping study and identified 98 papers as potentially relevant for our study. By applying inclusion and exclusion criteria we selected a set of 34 papers relevant for DSL evolution. We classified and analyzed these papers to create a map of the research field. We conclude that DSL evolution is a topic of increasing relevancy. However, research on language evolution so far did not focus much on the characteristics DSLs exhibit. Also, there are not many cross-references between our primary studies meaning researchers are often not aware of potentially useful work. Our study results help researchers and practitioners working on DSL-based approaches to get an overview of existing research on DSL evolution and open challenges.
{"title":"A Systematic Mapping Study on DSL Evolution","authors":"Jürgen Thanhofer-Pilisch, Alexander Lang, Michael Vierhauser, Rick Rabiser","doi":"10.1109/SEAA.2017.25","DOIUrl":"https://doi.org/10.1109/SEAA.2017.25","url":null,"abstract":"Domain-specific languages (DSLs) are frequently used in software engineering. In contrast to general-purpose languages, DSLs are designed for a special purpose in a particular domain. Due to volatile user requirements and new technologies DSLs, similar to the software systems they describe or produce, are subject to continuous evolution. This work explores existing research on DSL evolution to summarize, structure and analyze this area of research, and to identify trends and open issues. We conducted a systematic mapping study and identified 98 papers as potentially relevant for our study. By applying inclusion and exclusion criteria we selected a set of 34 papers relevant for DSL evolution. We classified and analyzed these papers to create a map of the research field. We conclude that DSL evolution is a topic of increasing relevancy. However, research on language evolution so far did not focus much on the characteristics DSLs exhibit. Also, there are not many cross-references between our primary studies meaning researchers are often not aware of potentially useful work. Our study results help researchers and practitioners working on DSL-based approaches to get an overview of existing research on DSL evolution and open challenges.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115266501","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}
The quality of mobile applications is one essential factor for their success because users often immediately discard applications with insufficient quality. In prior contributions, we presented FIT4Apps, a quality assurance method for mobile applications, which focuses inspections and tests on the development of mobile applications. We performed a two-step empirical evaluation of this method: a controlled experiment and a case study, which was performed as a post-mortem analysis. The empirical evaluation showed the applicability of FIT4Apps and demonstrated that it finds, respectively prevents, at least 75% more mobile-specific failures during development compared to state-of-the-practice approaches. This comprises failures revealed by testing or prevented by revealed requirements defects and leads to at least 85% less mobile-specific failures after the release of the mobile application. In our setting, the effort for applying FIT4Apps is less than 1% of the overall development effort for an iteration and may even save effort considering the benefits of earlier findings.
{"title":"Guiding Quality Assurance for Mobile Applications with FIT4Apps — A Two-Step Evaluation","authors":"Konstantin Holl, Frank Elberzhager","doi":"10.1109/SEAA.2017.12","DOIUrl":"https://doi.org/10.1109/SEAA.2017.12","url":null,"abstract":"The quality of mobile applications is one essential factor for their success because users often immediately discard applications with insufficient quality. In prior contributions, we presented FIT4Apps, a quality assurance method for mobile applications, which focuses inspections and tests on the development of mobile applications. We performed a two-step empirical evaluation of this method: a controlled experiment and a case study, which was performed as a post-mortem analysis. The empirical evaluation showed the applicability of FIT4Apps and demonstrated that it finds, respectively prevents, at least 75% more mobile-specific failures during development compared to state-of-the-practice approaches. This comprises failures revealed by testing or prevented by revealed requirements defects and leads to at least 85% less mobile-specific failures after the release of the mobile application. In our setting, the effort for applying FIT4Apps is less than 1% of the overall development effort for an iteration and may even save effort considering the benefits of earlier findings.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"85 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114439485","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}
The software ecosystem paradigm is a means for companies to obtain benefits by joining a network of partners that supply infrastructure, software and services for a shared market. In this paper, we analyse the relationships among partners participating in software ecosystems by means of established power theories. We report the findings of a multiple case study of two software ecosystems formed by small-to-medium enterprises. Our main contribution is to investigate the role of power in software ecosystems by describing how companies exercise coercive, expert, legitimate, referent and reward power. In addition, we explore how power-balancing operations can lead these partnerships to thrive and sustain the evolution of software ecosystems.
{"title":"The Dynamics of Power in Software Ecosystems: Insights from a Multiple Case Study","authors":"G. Santos, C. Alves","doi":"10.1109/SEAA.2017.51","DOIUrl":"https://doi.org/10.1109/SEAA.2017.51","url":null,"abstract":"The software ecosystem paradigm is a means for companies to obtain benefits by joining a network of partners that supply infrastructure, software and services for a shared market. In this paper, we analyse the relationships among partners participating in software ecosystems by means of established power theories. We report the findings of a multiple case study of two software ecosystems formed by small-to-medium enterprises. Our main contribution is to investigate the role of power in software ecosystems by describing how companies exercise coercive, expert, legitimate, referent and reward power. In addition, we explore how power-balancing operations can lead these partnerships to thrive and sustain the evolution of software ecosystems.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"32 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132943064","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}
Due to C's overwhelming dominance in industry, reactive embedded applications usually rely on conventional sequential programming. Adopted approaches favor event-driven paradigms which prevent function-oriented code decomposition in particular. This encourages the violation of fundamental software engineering principles. The reactive programming paradigm is proposed as a general solution. However, most reactive languages cannot keep up with C's practical advantages. It appears, that the subfamily of synchronous languages provides promising features but real-world deployments and evaluations are rarely reported in literature. On this account, we make two major contributions in this paper. First, we elaborate how the lack of function-oriented software decomposition manifests in a real-life industrial application. Second, we provide a corresponding re-implementation which illustrates the deployment and discusses the gained engineering benefits provided by the third-party, synchronous-reactive programming language Céu. We believe that our work generally reveals a practicable way of improving embedded software quality in industrial applications.
{"title":"Function-Oriented Decomposition for Reactive Embedded Software","authors":"Matthias Terber","doi":"10.1109/SEAA.2017.42","DOIUrl":"https://doi.org/10.1109/SEAA.2017.42","url":null,"abstract":"Due to C's overwhelming dominance in industry, reactive embedded applications usually rely on conventional sequential programming. Adopted approaches favor event-driven paradigms which prevent function-oriented code decomposition in particular. This encourages the violation of fundamental software engineering principles. The reactive programming paradigm is proposed as a general solution. However, most reactive languages cannot keep up with C's practical advantages. It appears, that the subfamily of synchronous languages provides promising features but real-world deployments and evaluations are rarely reported in literature. On this account, we make two major contributions in this paper. First, we elaborate how the lack of function-oriented software decomposition manifests in a real-life industrial application. Second, we provide a corresponding re-implementation which illustrates the deployment and discusses the gained engineering benefits provided by the third-party, synchronous-reactive programming language Céu. We believe that our work generally reveals a practicable way of improving embedded software quality in industrial applications.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132740140","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}
Grace Kamulegeya, R. Hebig, I. Hammouda, M. Chaudron, Raymond Mugwanya
Context: Software startups need to tackle a lot of challenges as they grow. Therefore, reoccurring strategies are applied that can be captured in form of patterns. Objectives: While more and more of these patterns are published, we aimed to discover to what degree they are applied within different regions of the world. Method: We studied the cases of 7 software startups within 2 incubation hubs in Uganda, by performing qualitative interviews. We focused on 5 patterns from diverse areas of concerns to analyze whether the Ugandan startups' strategies match these patterns. Results: For most of the patterns we found matches. However, in some cases the startups strategies are only partially described by the known pattern. Conclusion: The findings indicate that startup patterns can often be transferred from countries such as Switzerland and Finland to Uganda. we also found some variations from the known patterns in the contexts and solutions applied in Ugandan startups.
{"title":"Exploring the Applicability of Software Startup Patterns in the Ugandan Context","authors":"Grace Kamulegeya, R. Hebig, I. Hammouda, M. Chaudron, Raymond Mugwanya","doi":"10.1109/SEAA.2017.41","DOIUrl":"https://doi.org/10.1109/SEAA.2017.41","url":null,"abstract":"Context: Software startups need to tackle a lot of challenges as they grow. Therefore, reoccurring strategies are applied that can be captured in form of patterns. Objectives: While more and more of these patterns are published, we aimed to discover to what degree they are applied within different regions of the world. Method: We studied the cases of 7 software startups within 2 incubation hubs in Uganda, by performing qualitative interviews. We focused on 5 patterns from diverse areas of concerns to analyze whether the Ugandan startups' strategies match these patterns. Results: For most of the patterns we found matches. However, in some cases the startups strategies are only partially described by the known pattern. Conclusion: The findings indicate that startup patterns can often be transferred from countries such as Switzerland and Finland to Uganda. we also found some variations from the known patterns in the contexts and solutions applied in Ugandan startups.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"27 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128439660","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}
O. E. Adali, N. Alpay Karagoz, Z. Gurel, Touseef Tahir, Çigdem Gencel
Good planning and managing software test process require accurate estimation of software test effort. This becomes particularly significant when validation and verification activities are to be performed by an independent organization. This study presents a systematic literature review and a follow up industrial survey, which was performed to investigate the state of the art on software test effort estimation and the current practice of software industry in Turkey. The results showed that only few of the methods and metrics discussed in the literature are used by the industry. Furthermore, industrial participants have a general opinion that these methods could be improved by making use of additional metrics. Hence, there is a significant need for collaborative studies between industry and academia.
{"title":"Software Test Effort Estimation: State of the Art in Turkish Software Industry","authors":"O. E. Adali, N. Alpay Karagoz, Z. Gurel, Touseef Tahir, Çigdem Gencel","doi":"10.1109/SEAA.2017.72","DOIUrl":"https://doi.org/10.1109/SEAA.2017.72","url":null,"abstract":"Good planning and managing software test process require accurate estimation of software test effort. This becomes particularly significant when validation and verification activities are to be performed by an independent organization. This study presents a systematic literature review and a follow up industrial survey, which was performed to investigate the state of the art on software test effort estimation and the current practice of software industry in Turkey. The results showed that only few of the methods and metrics discussed in the literature are used by the industry. Furthermore, industrial participants have a general opinion that these methods could be improved by making use of additional metrics. Hence, there is a significant need for collaborative studies between industry and academia.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"96 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131507759","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}
J. Klünder, Carolin Unger-Windeler, Fabian Kortum, K. Schneider
Information sharing in teams is one of the most important aspects of successful software development. For instance, requirements, design decisions and guidelines need to be communicated with the whole team or with specific team members. For information exchange, communication is mandatory. Meetings are an effective way to communicate with many team members. Hence, much information can be shared during team meetings. But meeting and communication behavior may vary. During the project, the team members get to know the others more and more. This has an influence on the chosen ways of information sharing and hence changes communication behavior.We are interested in analyzing the influence of meetings on team-internal communication and collaboration. To analyze collaboration, we consider a measure of indirections representing used communication channels and the perceived communication intensity between each of the team members. In a study with 65 students across eight development teams, we examine how intensively team members used various communication channels and if there is a change in communication and meeting behavior over time.In our study, the communication behavior becomes increasingly effective during the development process and the number of team meetings decreases in the course of the project. Moreover, the teams decentralize their communication behavior during project progress. According to our results, there is no cause for concern if there are less or shorter meetings at the end than at the beginning of a project.
{"title":"Team Meetings and Their Relevance for the Software Development Process Over Time","authors":"J. Klünder, Carolin Unger-Windeler, Fabian Kortum, K. Schneider","doi":"10.1109/SEAA.2017.57","DOIUrl":"https://doi.org/10.1109/SEAA.2017.57","url":null,"abstract":"Information sharing in teams is one of the most important aspects of successful software development. For instance, requirements, design decisions and guidelines need to be communicated with the whole team or with specific team members. For information exchange, communication is mandatory. Meetings are an effective way to communicate with many team members. Hence, much information can be shared during team meetings. But meeting and communication behavior may vary. During the project, the team members get to know the others more and more. This has an influence on the chosen ways of information sharing and hence changes communication behavior.We are interested in analyzing the influence of meetings on team-internal communication and collaboration. To analyze collaboration, we consider a measure of indirections representing used communication channels and the perceived communication intensity between each of the team members. In a study with 65 students across eight development teams, we examine how intensively team members used various communication channels and if there is a change in communication and meeting behavior over time.In our study, the communication behavior becomes increasingly effective during the development process and the number of team meetings decreases in the course of the project. Moreover, the teams decentralize their communication behavior during project progress. According to our results, there is no cause for concern if there are less or shorter meetings at the end than at the beginning of a project.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"63 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115942452","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}
Enterprise Resource Planning (ERP) systems are large scale integrated systems covering most of the business processes of an enterprise. ERP projects differ from software projects with customization, modification, integration and data conversion phases. Most of the time effort and time estimations are performed in an ad-hoc fashion in ERP projects and as a result they frequently suffer from time and budget overruns. Although there is no consensus on a methodology to estimate size, effort and cost of ERP projects there are various research studies in the field. The purpose of this paper is to review the literature on effort estimation methods for ERP projects, their validations and limitations. The systematic literature review used online journal indexes between January 2000 and December 2016. Studies focusing on effort estimation for ERP projects were selected. Two reviewers assessed all studies and 41 were shortlisted. In most of the studies, cost factors for ERP projects were investigated and validated. Our findings showed that effort estimation methods have mostly used function points as an input. Validations of these methods were mostly done by using history-based validation approaches.
{"title":"Effort Estimation for ERP Projects — A Systematic Review","authors":"Neslihan Küçükates Ömüral, Onur Demirörs","doi":"10.1109/SEAA.2017.68","DOIUrl":"https://doi.org/10.1109/SEAA.2017.68","url":null,"abstract":"Enterprise Resource Planning (ERP) systems are large scale integrated systems covering most of the business processes of an enterprise. ERP projects differ from software projects with customization, modification, integration and data conversion phases. Most of the time effort and time estimations are performed in an ad-hoc fashion in ERP projects and as a result they frequently suffer from time and budget overruns. Although there is no consensus on a methodology to estimate size, effort and cost of ERP projects there are various research studies in the field. The purpose of this paper is to review the literature on effort estimation methods for ERP projects, their validations and limitations. The systematic literature review used online journal indexes between January 2000 and December 2016. Studies focusing on effort estimation for ERP projects were selected. Two reviewers assessed all studies and 41 were shortlisted. In most of the studies, cost factors for ERP projects were investigated and validated. Our findings showed that effort estimation methods have mostly used function points as an input. Validations of these methods were mostly done by using history-based validation approaches.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"61 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127130370","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}
Unit testing has been considered as having a key role in building high quality software, and therefore it has been widely used in practice. However, data on the relationship between unit testing and aspects of software quality remain scarce. A survey study with 235 survey responses from seven organizations was conducted in order to understand the correlation between practitioners' perception of code quality and unit testing practices. In addition, we conducted a case study in one of these organizations to investigate the correlation between unit test coverage and post-unit test defects. In both cases none or weak correlations were found. We recommend further research on the effectiveness of different testing practices in order to help practitioners to understand how to best allocate their resources to the testing chain.
{"title":"On the Relation Between Unit Testing and Code Quality","authors":"Lucas Gren, Vard Antinyan","doi":"10.1109/SEAA.2017.36","DOIUrl":"https://doi.org/10.1109/SEAA.2017.36","url":null,"abstract":"Unit testing has been considered as having a key role in building high quality software, and therefore it has been widely used in practice. However, data on the relationship between unit testing and aspects of software quality remain scarce. A survey study with 235 survey responses from seven organizations was conducted in order to understand the correlation between practitioners' perception of code quality and unit testing practices. In addition, we conducted a case study in one of these organizations to investigate the correlation between unit test coverage and post-unit test defects. In both cases none or weak correlations were found. We recommend further research on the effectiveness of different testing practices in order to help practitioners to understand how to best allocate their resources to the testing chain.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131311085","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}
Carlos Fernández-Sánchez, Hector Humanes, J. Garbajosa, Jessica Díaz
Technical debt monitoring is one of the activities that have to be performed in technical debt management. To do that, there are different techniques that can be used to estimate technical debt and different tools that implement those different techniques. This paper presents TEDMA Tool, a tool for monitoring technical debt over the software evolution and that it is open to integrate third party tools. TEDMA is based on the analysis of source code repositories and is useful for researching using empirical data extracted from software projects. Currently, it is been used to analyze big projects in the execution of several case studies. The expected evolution of TEDMA will make the tool useful for software development industry.
{"title":"An Open Tool for Assisting in Technical Debt Management","authors":"Carlos Fernández-Sánchez, Hector Humanes, J. Garbajosa, Jessica Díaz","doi":"10.1109/SEAA.2017.60","DOIUrl":"https://doi.org/10.1109/SEAA.2017.60","url":null,"abstract":"Technical debt monitoring is one of the activities that have to be performed in technical debt management. To do that, there are different techniques that can be used to estimate technical debt and different tools that implement those different techniques. This paper presents TEDMA Tool, a tool for monitoring technical debt over the software evolution and that it is open to integrate third party tools. TEDMA is based on the analysis of source code repositories and is useful for researching using empirical data extracted from software projects. Currently, it is been used to analyze big projects in the execution of several case studies. The expected evolution of TEDMA will make the tool useful for software development industry.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134291434","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
扫码关注我们
求助内容：
应助结果提醒方式：