Adoption of the most suitable requirements engineering (RE) process and selection of the most appropriate RE techniques for a given project are challenging issues for industry. In order to alleviate the problems, a framework for RE process development (FRERE) was developed based on our research in the last six years. The overall architecture of the framework and a brief case study are presented in the paper. The framework addresses several core issues of the RE process: engineering issues, domain issues, characteristics of the software project, and issues of conformity to software process standards. FRERE consists of three parts: (1) The RE process knowledge base (REPKB) which contains RE process knowledge, (2) methodologies which provide guidance to develop a customized software process model in an iterative way; and (3) assessment models which provide information about the suitability of the newly developed RE process model for the software project under development.
{"title":"A Framework for Requirements Engineering PRocess DEvelopment (FRERE)","authors":"Li Jiang, A. Eberlein","doi":"10.1109/ASWEC.2008.26","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.26","url":null,"abstract":"Adoption of the most suitable requirements engineering (RE) process and selection of the most appropriate RE techniques for a given project are challenging issues for industry. In order to alleviate the problems, a framework for RE process development (FRERE) was developed based on our research in the last six years. The overall architecture of the framework and a brief case study are presented in the paper. The framework addresses several core issues of the RE process: engineering issues, domain issues, characteristics of the software project, and issues of conformity to software process standards. FRERE consists of three parts: (1) The RE process knowledge base (REPKB) which contains RE process knowledge, (2) methodologies which provide guidance to develop a customized software process model in an iterative way; and (3) assessment models which provide information about the suitability of the newly developed RE process model for the software project under development.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"41 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114096765","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}
This paper addresses the influence the checklist based reading inspection technique has on a developer's ability to modify inspected code. Traditionally, inspections have been used to detect defects within the development life cycle. This research identified a correlation between the number of defects detected and the successful code extensions for new functionality unrelated to the defects. Participants reported that having completed a checklist inspection, modifying the code was easier because the inspection had given them an understanding of the code that would not have existed otherwise. The results also showed a significant difference in how developers systematically modified code after completing a checklist inspection when compared to those who had not performed a checklist inspection. This study has shown that applying software inspections for purposes other than defect detection include software understanding and comprehension.
{"title":"Checklist Based Reading's Influence on a Developer's Understanding","authors":"D. McMeekin, B. V. Konsky, E. Chang, D. Cooper","doi":"10.1109/ASWEC.2008.7","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.7","url":null,"abstract":"This paper addresses the influence the checklist based reading inspection technique has on a developer's ability to modify inspected code. Traditionally, inspections have been used to detect defects within the development life cycle. This research identified a correlation between the number of defects detected and the successful code extensions for new functionality unrelated to the defects. Participants reported that having completed a checklist inspection, modifying the code was easier because the inspection had given them an understanding of the code that would not have existed otherwise. The results also showed a significant difference in how developers systematically modified code after completing a checklist inspection when compared to those who had not performed a checklist inspection. This study has shown that applying software inspections for purposes other than defect detection include software understanding and comprehension.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128661922","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}
Component retrieval/discovery is a well-established research direction in Software Engineering. With the surge of Service-Oriented Architecture (SOA), service discovery has become increasingly crucial. However, the public UDDI Business Registry - the primary service discovery mechanism over the Internet - has been shut down permanently since 2006. Moreover, keyword-based service discovery is insufficient in coping with complex discovery requirements posed by modern software developers. In this paper, we propose an empirical semantic- based Web service discovery approach. It provides an automatic Web service discovery mechanism that can locate relevant Web services based on concepts rather than keywords. The major contribution of this paper is three fold. First we articulate three requirements that software developers often raise during the component/service development and discovery process. Next, we propose the application of Latent Semantic Analysis into the area of Web services discovery. To our best knowledge, little work has been done in this area which leverages concept-based Information Retrieval models in service discovery. Last, we provide a proof-of-concept system prototype that can suffice three specific requirements of semantic service discovery.
{"title":"An Empirical Approach for Semantic Web Services Discovery","authors":"Chen Wu, E. Chang, A. Aitken","doi":"10.1109/ASWEC.2008.52","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.52","url":null,"abstract":"Component retrieval/discovery is a well-established research direction in Software Engineering. With the surge of Service-Oriented Architecture (SOA), service discovery has become increasingly crucial. However, the public UDDI Business Registry - the primary service discovery mechanism over the Internet - has been shut down permanently since 2006. Moreover, keyword-based service discovery is insufficient in coping with complex discovery requirements posed by modern software developers. In this paper, we propose an empirical semantic- based Web service discovery approach. It provides an automatic Web service discovery mechanism that can locate relevant Web services based on concepts rather than keywords. The major contribution of this paper is three fold. First we articulate three requirements that software developers often raise during the component/service development and discovery process. Next, we propose the application of Latent Semantic Analysis into the area of Web services discovery. To our best knowledge, little work has been done in this area which leverages concept-based Information Retrieval models in service discovery. Last, we provide a proof-of-concept system prototype that can suffice three specific requirements of semantic service discovery.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125754936","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}
Software theft is a threat for companies that consider code as a core asset. A birthmark can help to prove software theft by identifying intrinsic properties of a program. Two programs with the same birthmark are likely to share a common origin. In this paper, we propose a novel dynamic birthmark. Using a dynamic program slicing tool with the given input, a union of k-gram instruction-sequence sets denoted as birthmark is used to identify a program uniquely. To evaluate the strength of the birthmarking technique, we compare static k-gram based software birthmark with dynamic approach from similarity with academic obfuscation tools. The result shows that the new birthmark provides both high credibility and resilience. In particular, it proves that the dynamic birthmark is more resilient to semantics-preserving transformations than the static k-gram birthmark.
{"title":"Dynamic K-Gram Based Software Birthmark","authors":"Yameng Bai, Xingming Sun, Guang Sun, Xiaohong Deng, Xiaoming Zhou","doi":"10.1109/ASWEC.2008.21","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.21","url":null,"abstract":"Software theft is a threat for companies that consider code as a core asset. A birthmark can help to prove software theft by identifying intrinsic properties of a program. Two programs with the same birthmark are likely to share a common origin. In this paper, we propose a novel dynamic birthmark. Using a dynamic program slicing tool with the given input, a union of k-gram instruction-sequence sets denoted as birthmark is used to identify a program uniquely. To evaluate the strength of the birthmarking technique, we compare static k-gram based software birthmark with dynamic approach from similarity with academic obfuscation tools. The result shows that the new birthmark provides both high credibility and resilience. In particular, it proves that the dynamic birthmark is more resilient to semantics-preserving transformations than the static k-gram birthmark.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"104 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126056954","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}
Software process modeling has become an essential technique for managing software development processes. However, purely quantitative process modeling requires a detailed understanding and accurate measurement of software process, which relies on reliable and precise history data. This paper presents a semi-quantitative process modeling approach to model and manage software development processes. It allows for the existence of uncertainty and contingency during software development, and facilitates a manager's qualitative and quantitative estimates and assessments of process progress. We demonstrate its value and flexibility by developing semi-quantitative models of the test-and-fix process of incremental software development. Results conclude that the semi-quantitative process modeling approach can support process or project management activities, including estimating, planning, tracking and decision making throughout the software development cycle.
{"title":"Semi-quantitative Modeling for Managing Software Development Processes","authors":"He Zhang, J. Keung, B. Kitchenham, D. R. Jeffery","doi":"10.1109/ASWEC.2008.50","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.50","url":null,"abstract":"Software process modeling has become an essential technique for managing software development processes. However, purely quantitative process modeling requires a detailed understanding and accurate measurement of software process, which relies on reliable and precise history data. This paper presents a semi-quantitative process modeling approach to model and manage software development processes. It allows for the existence of uncertainty and contingency during software development, and facilitates a manager's qualitative and quantitative estimates and assessments of process progress. We demonstrate its value and flexibility by developing semi-quantitative models of the test-and-fix process of incremental software development. Results conclude that the semi-quantitative process modeling approach can support process or project management activities, including estimating, planning, tracking and decision making throughout the software development cycle.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"149 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124162423","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}
Budget and schedule savings are the driving factors for the adoption of commercial-off-the-shelf (COTS) software components by software development organizations. The reliance on COTS components has lead to component-based development (CBD) software systems and introduced changes to the software development process and hence software project management responsibilities and roles. This paper introduces a general framework discussion of essential management aspects for CBD, focusing on COTS. Particularly, stakeholders, requirements, component selection and architecture management issues are discussed from different angles. Some CBD management guidelines and best practices for these aspects are outlined in the conclusion. In addition, CBD management challenges are drawn along with some suggestions in the conclusion section.
{"title":"Commercial-Off-The-Shelf Software Development Framework","authors":"Basem Suleiman","doi":"10.1109/ASWEC.2008.73","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.73","url":null,"abstract":"Budget and schedule savings are the driving factors for the adoption of commercial-off-the-shelf (COTS) software components by software development organizations. The reliance on COTS components has lead to component-based development (CBD) software systems and introduced changes to the software development process and hence software project management responsibilities and roles. This paper introduces a general framework discussion of essential management aspects for CBD, focusing on COTS. Particularly, stakeholders, requirements, component selection and architecture management issues are discussed from different angles. Some CBD management guidelines and best practices for these aspects are outlined in the conclusion. In addition, CBD management challenges are drawn along with some suggestions in the conclusion section.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"36 2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129960008","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}
This paper describes the use of ontologies in different aspects of software engineering. This use of ontologies varies from support for software developers at multiple sites to the use of an ontology to provide semantics in different categories of software, particularly on the Web. The world's first and only software engineering ontology and a project management ontology in conjunction with a domain ontology are used to provide support for software development that is taking place at multiple sites. Ontologies are used to provide semantics to deal with heterogeneity in the representation of multiple information sources, enable the selection and composition of web services and grid resources, provide the shared knowledge base for multiagent systems, provide semantics and structure for trust and reputation systems and privacy based systems and codification of shared knowledge within different domains in business, science, manufacturing, engineering and utilities. They, therefore, bring a new paradigm to software engineering through the use of semantics as a central mechanism which will revolutionize the way software is developed and consumed in the future leading to the development of software as a service bringing about the dawn of software engineering 2.0.
{"title":"Ontology-Based Software Engineering- Software Engineering 2.0","authors":"T. Dillon, E. Chang, P. Wongthongtham","doi":"10.1109/ASWEC.2008.77","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.77","url":null,"abstract":"This paper describes the use of ontologies in different aspects of software engineering. This use of ontologies varies from support for software developers at multiple sites to the use of an ontology to provide semantics in different categories of software, particularly on the Web. The world's first and only software engineering ontology and a project management ontology in conjunction with a domain ontology are used to provide support for software development that is taking place at multiple sites. Ontologies are used to provide semantics to deal with heterogeneity in the representation of multiple information sources, enable the selection and composition of web services and grid resources, provide the shared knowledge base for multiagent systems, provide semantics and structure for trust and reputation systems and privacy based systems and codification of shared knowledge within different domains in business, science, manufacturing, engineering and utilities. They, therefore, bring a new paradigm to software engineering through the use of semantics as a central mechanism which will revolutionize the way software is developed and consumed in the future leading to the development of software as a service bringing about the dawn of software engineering 2.0.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"390 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131943416","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}
Recent advances in wireless technology have enabled the development of low-cost wireless solutions capable of robust and reliable communication within application areas such as wireless networking, wireless sensor networks, and asset tracking. For the oil & gas industry, utilizing this technology will lead to reduced operating costs and enable new applications. There are several challenges related to the introduction of wireless technology in the oil & gas industry. Primarily, wireless devices have to execute software implementations of complex network algorithms with real-time requirements on embedded platforms with limited resources and low-power requirements. Further, how to enable the monitoring and control applications of the wireless solutions to be managed and operated by technical personnel who do not necessarily have extensive knowledge of the underlying wireless technology. And finally, wireless systems should seamlessly integrate with already existing IT infrastructure and user applications. In this paper, issues related to these challenges are investigated.
{"title":"Layered Software Challenge of Wireless Technology in the Oil & Gas Industry","authors":"Stig Petersen, Simon Carlsen, A. Skavhaug","doi":"10.1109/ASWEC.2008.76","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.76","url":null,"abstract":"Recent advances in wireless technology have enabled the development of low-cost wireless solutions capable of robust and reliable communication within application areas such as wireless networking, wireless sensor networks, and asset tracking. For the oil & gas industry, utilizing this technology will lead to reduced operating costs and enable new applications. There are several challenges related to the introduction of wireless technology in the oil & gas industry. Primarily, wireless devices have to execute software implementations of complex network algorithms with real-time requirements on embedded platforms with limited resources and low-power requirements. Further, how to enable the monitoring and control applications of the wireless solutions to be managed and operated by technical personnel who do not necessarily have extensive knowledge of the underlying wireless technology. And finally, wireless systems should seamlessly integrate with already existing IT infrastructure and user applications. In this paper, issues related to these challenges are investigated.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130722863","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}
Group-based software engineering projects are an important part of computer science and information technology curricula. Fair assessment of individual contributions to group-based projects remains a challenging problem. Peer-based assessment, where students assess their fellow team members, is seen as one answer to this. In this paper we discuss the key aspects that need to be addressed in order to develop a successful peer assessment method. We propose a method for carrying out peer assessments for a large software engineering class. We briefly describe a Web-based tool that we have developed to support our method, and comment on our initial experiences in using the tool.
{"title":"Peer Assessment of Group-Based Software Engineering Projects","authors":"D. Hemer","doi":"10.1109/ASWEC.2008.8","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.8","url":null,"abstract":"Group-based software engineering projects are an important part of computer science and information technology curricula. Fair assessment of individual contributions to group-based projects remains a challenging problem. Peer-based assessment, where students assess their fellow team members, is seen as one answer to this. In this paper we discuss the key aspects that need to be addressed in order to develop a successful peer assessment method. We propose a method for carrying out peer assessments for a large software engineering class. We briefly describe a Web-based tool that we have developed to support our method, and comment on our initial experiences in using the tool.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116855275","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}
Teaching and learning for the degrees of Software Engineering(SE), Computer Science(CS), Information Technology (IT), Information Systems (IS) and Electronic Commerce (EC), with recent trends in Business IT, Management of Information Systems (MIS) or Information Communication Technology (ICT) and so forth are often confused by staff and students. These new disciplines, which have emerged over the last 30 years, strongly overlap each other. New disciplines like IS and EC are not clearly defined and are often confused with other related fields such as CS, CE and SE. The lack of standard curriculum amongst Australian IT, IS and EC programmes adds further confusion to the CS and SE programmes. Professional bodies such as IEEE, ACM, AIS and the like have been developing model curricula as a guide for universities that wish to obtain accreditation for their CS, SE and IT/IS courses. They normally make up core topics and a list of electives that are guided by intended SE, CS, IT, IS and EC career tracks. The purpose of this study is to perform a comparative analysis of USA, UK and Australian academic programmes against the proposed curriculum structure. It is envisage that the result of this study will provide a baseline in guiding curriculum evaluation and revision for Australian and international universities' computing and IT related courses. Education in the computing/IT related areas are currently facing the global challenges of declining interest, low student enrolment and the increasing demand of computing/IT skilled workers in industry and commerce. The disappearance of CS, SE, IS into Science, IT or Electrical Engineering add confusion for prospective students and industry employers. The disciplines of SE, CS, IT, IS and EC, are now facing the increasing challenges in survival, and they need to be clearly re-defining themselves in order to survive into the 2020s. This paper describes the issues and challenges in teaching and learning these disciplines and identifies the possible causes and possible sustainable solution for ICT educators.
{"title":"Issues and Challenges in Teaching SE, IT, IS and EC","authors":"K. Chin","doi":"10.1109/ASWEC.2008.79","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.79","url":null,"abstract":"Teaching and learning for the degrees of Software Engineering(SE), Computer Science(CS), Information Technology (IT), Information Systems (IS) and Electronic Commerce (EC), with recent trends in Business IT, Management of Information Systems (MIS) or Information Communication Technology (ICT) and so forth are often confused by staff and students. These new disciplines, which have emerged over the last 30 years, strongly overlap each other. New disciplines like IS and EC are not clearly defined and are often confused with other related fields such as CS, CE and SE. The lack of standard curriculum amongst Australian IT, IS and EC programmes adds further confusion to the CS and SE programmes. Professional bodies such as IEEE, ACM, AIS and the like have been developing model curricula as a guide for universities that wish to obtain accreditation for their CS, SE and IT/IS courses. They normally make up core topics and a list of electives that are guided by intended SE, CS, IT, IS and EC career tracks. The purpose of this study is to perform a comparative analysis of USA, UK and Australian academic programmes against the proposed curriculum structure. It is envisage that the result of this study will provide a baseline in guiding curriculum evaluation and revision for Australian and international universities' computing and IT related courses. Education in the computing/IT related areas are currently facing the global challenges of declining interest, low student enrolment and the increasing demand of computing/IT skilled workers in industry and commerce. The disappearance of CS, SE, IS into Science, IT or Electrical Engineering add confusion for prospective students and industry employers. The disciplines of SE, CS, IT, IS and EC, are now facing the increasing challenges in survival, and they need to be clearly re-defining themselves in order to survive into the 2020s. This paper describes the issues and challenges in teaching and learning these disciplines and identifies the possible causes and possible sustainable solution for ICT educators.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116887602","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
扫码关注我们
求助内容：
应助结果提醒方式：