Early in a system's life cycle, a system's behavior is typically partially specified using scenarios, invariants, and temporal properties. These specifications prohibit or require certain behaviors, while leaving other behaviors uncategorized into either of those. Engineers refine the specification by eliciting more requirements to finally arrive at a complete behavioral description. Partial-behavior models have been utilized as a formal foundation for capturing partial system specifications. Mapping the requirements to partial behavior models enables automated analyses (e.g., requirements consistency checking) and helps to elicit new requirements. Under the current practices, software systems are reasoned about and their behavior specified exclusively at the system level, disregarding of the fact that a system typically consists of interacting components. However, exclusively refining a behavior specification at the system-level runs the risk of arriving at an inconsistent specification, i.e. one that is not realizable as a composition of the system's components. To address this problem, we propose a framework that provides the lacking support: a newly specified requirement implicitly refines the system's underlying partial behavior model; our framework maps the new requirement to components by automatically distributing the system model refinements to the components' underlying models. By doing so, our framework prevents requirements inconsistencies and helps to identify further necessary requirements. We discuss the framework's soundness and correctness, and demonstrate its features on a case study previously used in related literature.
{"title":"Distributing refinements of a system-level partial behavior model","authors":"Ivo Krka, N. Medvidović","doi":"10.1109/RE.2013.6636707","DOIUrl":"https://doi.org/10.1109/RE.2013.6636707","url":null,"abstract":"Early in a system's life cycle, a system's behavior is typically partially specified using scenarios, invariants, and temporal properties. These specifications prohibit or require certain behaviors, while leaving other behaviors uncategorized into either of those. Engineers refine the specification by eliciting more requirements to finally arrive at a complete behavioral description. Partial-behavior models have been utilized as a formal foundation for capturing partial system specifications. Mapping the requirements to partial behavior models enables automated analyses (e.g., requirements consistency checking) and helps to elicit new requirements. Under the current practices, software systems are reasoned about and their behavior specified exclusively at the system level, disregarding of the fact that a system typically consists of interacting components. However, exclusively refining a behavior specification at the system-level runs the risk of arriving at an inconsistent specification, i.e. one that is not realizable as a composition of the system's components. To address this problem, we propose a framework that provides the lacking support: a newly specified requirement implicitly refines the system's underlying partial behavior model; our framework maps the new requirement to components by automatically distributing the system model refinements to the components' underlying models. By doing so, our framework prevents requirements inconsistencies and helps to identify further necessary requirements. We discuss the framework's soundness and correctness, and demonstrate its features on a case study previously used in related literature.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"120 1","pages":"72-81"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"78557993","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}
Requirements engineers often have to develop software for regulated domains. These regulations often contain cross-references to other laws. Cross-references can introduce exceptions or definitions, constrain existing requirements, or even conflict with other compliance requirements. To develop compliant software, requirements engineers must understand the impact these cross-references have on their software. In this paper, we present an empirical study in which we measure the ability of software practitioners to classify cross-references using our previously developed cross-reference taxonomy. We discover that software practitioners are not well equipped to understand the impact of cross-references on their software.
{"title":"An empirical investigation of software engineers' ability to classify legal cross-references","authors":"J. C. Maxwell, A. Antón, J. Earp","doi":"10.1109/RE.2013.6636702","DOIUrl":"https://doi.org/10.1109/RE.2013.6636702","url":null,"abstract":"Requirements engineers often have to develop software for regulated domains. These regulations often contain cross-references to other laws. Cross-references can introduce exceptions or definitions, constrain existing requirements, or even conflict with other compliance requirements. To develop compliant software, requirements engineers must understand the impact these cross-references have on their software. In this paper, we present an empirical study in which we measure the ability of software practitioners to classify cross-references using our previously developed cross-reference taxonomy. We discover that software practitioners are not well equipped to understand the impact of cross-references on their software.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"33 1","pages":"24-31"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"76202466","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}
For many software projects, keeping requirements on track needs an effective and efficient path from data to decision. Visual analytics creates such a path that enables the human to extract insights by interacting with the relevant information. While various requirements visualization techniques exist, few have produced end-to-end values to practitioners. In this paper, we advance the literature on visual requirements analytics by characterizing its key components and relationships. This allows us to not only assess existing approaches, but also create tool enhancements in a principled manner. We evaluate our enhanced tool supports through a case study where massive, heterogeneous, and dynamic requirements are processed, visualized, and analyzed. In particular, our study illuminates how increased interactivity of requirements visualization could lead to actionable decisions.
{"title":"Keeping requirements on track via visual analytics","authors":"Nan Niu, S. Reddivari, Zhangji Chen","doi":"10.1109/RE.2013.6636720","DOIUrl":"https://doi.org/10.1109/RE.2013.6636720","url":null,"abstract":"For many software projects, keeping requirements on track needs an effective and efficient path from data to decision. Visual analytics creates such a path that enables the human to extract insights by interacting with the relevant information. While various requirements visualization techniques exist, few have produced end-to-end values to practitioners. In this paper, we advance the literature on visual requirements analytics by characterizing its key components and relationships. This allows us to not only assess existing approaches, but also create tool enhancements in a principled manner. We evaluate our enhanced tool supports through a case study where massive, heterogeneous, and dynamic requirements are processed, visualized, and analyzed. In particular, our study illuminates how increased interactivity of requirements visualization could lead to actionable decisions.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"27 1","pages":"205-214"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"79664996","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}
Application distribution platforms - or app stores - such as Google Play or Apple AppStore allow users to submit feedback in form of ratings and reviews to downloaded applications. In the last few years, these platforms have become very popular to both application developers and users. However, their real potential for and impact on requirements engineering processes are not yet well understood. This paper reports on an exploratory study, which analyzes over one million reviews from the Apple AppStore. We investigated how and when users provide feedback, inspected the feedback content, and analyzed its impact on the user community. We found that most of the feedback is provided shortly after new releases, with a quickly decreasing frequency over time. Reviews typically contain multiple topics, such as user experience, bug reports, and feature requests. The quality and constructiveness vary widely, from helpful advices and innovative ideas to insulting offenses. Feedback content has an impact on download numbers: positive messages usually lead to better ratings and vice versa. Negative feedback such as shortcomings is typically destructive and misses context details and user experience. We discuss our findings and their impact on software and requirements engineering teams.
{"title":"User feedback in the appstore: An empirical study","authors":"Dennis Pagano, W. Maalej","doi":"10.1109/RE.2013.6636712","DOIUrl":"https://doi.org/10.1109/RE.2013.6636712","url":null,"abstract":"Application distribution platforms - or app stores - such as Google Play or Apple AppStore allow users to submit feedback in form of ratings and reviews to downloaded applications. In the last few years, these platforms have become very popular to both application developers and users. However, their real potential for and impact on requirements engineering processes are not yet well understood. This paper reports on an exploratory study, which analyzes over one million reviews from the Apple AppStore. We investigated how and when users provide feedback, inspected the feedback content, and analyzed its impact on the user community. We found that most of the feedback is provided shortly after new releases, with a quickly decreasing frequency over time. Reviews typically contain multiple topics, such as user experience, bug reports, and feature requests. The quality and constructiveness vary widely, from helpful advices and innovative ideas to insulting offenses. Feedback content has an impact on download numbers: positive messages usually lead to better ratings and vice versa. Negative feedback such as shortcomings is typically destructive and misses context details and user experience. We discuss our findings and their impact on software and requirements engineering teams.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"45 1","pages":"125-134"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"75736728","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}
Attempts to utilize information retrieval techniques to fully automate the creation of traceability links have been hindered by terminology mismatches between source and target artifacts. Therefore, current trace retrieval algorithms tend to produce imprecise and incomplete results. In this paper we address this mismatch by proposing an expert system which integrates a knowledge base of domain concepts and their relationships, a set of logic rules for defining relationships between artifacts based on these rules, and a process for mapping artifacts into a structure against which the rules can be applied. This paper lays down the core foundations needed to integrate an expert system into the automated tracing process. We construct a knowledge base and inference rules for part of a large industrial project in the transportation domain and empirically show that our approach significantly improves precision and recall of the generated trace links.
{"title":"Foundations for an expert system in domain-specific traceability","authors":"Jin Guo, J. Cleland-Huang, B. Berenbach","doi":"10.1109/RE.2013.6636704","DOIUrl":"https://doi.org/10.1109/RE.2013.6636704","url":null,"abstract":"Attempts to utilize information retrieval techniques to fully automate the creation of traceability links have been hindered by terminology mismatches between source and target artifacts. Therefore, current trace retrieval algorithms tend to produce imprecise and incomplete results. In this paper we address this mismatch by proposing an expert system which integrates a knowledge base of domain concepts and their relationships, a set of logic rules for defining relationships between artifacts based on these rules, and a process for mapping artifacts into a structure against which the rules can be applied. This paper lays down the core foundations needed to integrate an expert system into the automated tracing process. We construct a knowledge base and inference rules for part of a large industrial project in the transportation domain and empirically show that our approach significantly improves precision and recall of the generated trace links.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"9 1","pages":"42-51"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"76342769","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 an increasingly connected society and industry, our modern societal world and all industry sectors now increasingly depend on large-scale complex Systems of Systems (SoS). The emerging interdisciplinary area of SoS and Systems of Systems Engineering (SoSE) is largely driven by societal needs including public services such as health, transport, water, energy, food security, etc. The scale, complexities and challenges presented by SoS require us to go beyond traditional Requirements Engineering (RE) approaches. However, as is evident from publications in major Requirements Engineering conferences and journals, no significant effort has been expedited towards addressing specific RE issues for Systems of Systems Engineering. This panel explores key RE challenges in Systems of Systems Engineering, specifically, the areas in which the international RE community need to focus its research, and the approaches that are most likely to meet these challenges effectively. We first introduce Systems of Systems Engineering and outline key characteristics of SoS. We conclude by arguing that there is an urgent need for the global RE community to develop new ways of thinking, new capabilities and possibly a new science as a key mechanism for addressing requirements complexities posed by Systems of Systems.
由于社会和工业的联系日益紧密，我们的现代社会和所有工业部门现在越来越依赖于大规模复杂的系统系统(so)。SoS和系统工程系统(SoSE)的新兴跨学科领域在很大程度上是由社会需求驱动的，包括公共服务，如卫生、交通、水、能源、食品安全等。so的规模、复杂性和挑战要求我们超越传统的需求工程(RE)方法。然而，从主要需求工程会议和期刊的出版物中可以明显看出，没有显著的努力被加速到解决系统工程系统的具体RE问题。该小组探讨了系统工程系统中关键的可再生能源挑战，特别是国际可再生能源社区需要关注其研究的领域，以及最有可能有效地应对这些挑战的方法。我们首先介绍了系统工程的系统，并概述了系统系统的主要特征。我们的结论是，全球可再生能源社区迫切需要发展新的思维方式、新的能力和可能的新科学，作为解决由系统的系统(Systems of Systems)带来的需求复杂性的关键机制。
{"title":"Identifying top challenges for international research on requirements engineering for systems of systems engineering","authors":"Cornelius Ncube, Soo Ling Lim, H. Dogan","doi":"10.1109/RE.2013.6636746","DOIUrl":"https://doi.org/10.1109/RE.2013.6636746","url":null,"abstract":"Due to an increasingly connected society and industry, our modern societal world and all industry sectors now increasingly depend on large-scale complex Systems of Systems (SoS). The emerging interdisciplinary area of SoS and Systems of Systems Engineering (SoSE) is largely driven by societal needs including public services such as health, transport, water, energy, food security, etc. The scale, complexities and challenges presented by SoS require us to go beyond traditional Requirements Engineering (RE) approaches. However, as is evident from publications in major Requirements Engineering conferences and journals, no significant effort has been expedited towards addressing specific RE issues for Systems of Systems Engineering. This panel explores key RE challenges in Systems of Systems Engineering, specifically, the areas in which the international RE community need to focus its research, and the approaches that are most likely to meet these challenges effectively. We first introduce Systems of Systems Engineering and outline key characteristics of SoS. We conclude by arguing that there is an urgent need for the global RE community to develop new ways of thinking, new capabilities and possibly a new science as a key mechanism for addressing requirements complexities posed by Systems of Systems.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"36 1","pages":"342-344"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"73865014","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 mini-tutorial will provide an overview of one approach to a requirements management (RM) tool evaluation. The guidance will focus on how this evaluation process and results can be adapted to work in any organization. Finally, the mini-tutorial concludes with the major challenges organizations face in implementing RM tools and suggestions to overcome them.
{"title":"Winning the hidden battle: Requirements tool selection and adoption","authors":"J. Beatty","doi":"10.1109/RE.2013.6636753","DOIUrl":"https://doi.org/10.1109/RE.2013.6636753","url":null,"abstract":"This mini-tutorial will provide an overview of one approach to a requirements management (RM) tool evaluation. The guidance will focus on how this evaluation process and results can be adapted to work in any organization. Finally, the mini-tutorial concludes with the major challenges organizations face in implementing RM tools and suggestions to overcome them.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"40 1","pages":"364-365"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"79633340","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 innovation potential of niche communities often remains inaccessible to service providers due to a lack of awareness and effective negotiation between these two groups. Requirements Bazaar, a browser-based social software for Social Requirements Engineering (SRE), aims at bringing together communities and service providers into such a negotiation process. Communities should be supported to express and trace their requirements and eventually receive a realization. Service providers should be supported in discovering relevant innovative requirements to maximize impact with a realization. In this paper we present Requirements Bazaar with focus on four aspects: requirements specification, a workflow for co-creation, workspace integration and personalizable requirements prioritization.
{"title":"Requirements Bazaar: Social requirements engineering for community-driven innovation","authors":"D. Renzel, Malte Behrendt, R. Klamma, M. Jarke","doi":"10.1109/RE.2013.6636738","DOIUrl":"https://doi.org/10.1109/RE.2013.6636738","url":null,"abstract":"The innovation potential of niche communities often remains inaccessible to service providers due to a lack of awareness and effective negotiation between these two groups. Requirements Bazaar, a browser-based social software for Social Requirements Engineering (SRE), aims at bringing together communities and service providers into such a negotiation process. Communities should be supported to express and trace their requirements and eventually receive a realization. Service providers should be supported in discovering relevant innovative requirements to maximize impact with a realization. In this paper we present Requirements Bazaar with focus on four aspects: requirements specification, a workflow for co-creation, workspace integration and personalizable requirements prioritization.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"19 1","pages":"326-327"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"78764810","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}
Developing global markets offer companies new opportunities to manufacture and sell information technology (IT) products in ways unforeseen by current laws and regulations. This innovation leads to changing requirements due to changes in product features, laws, or the locality where the product is sold or manufactured. To help developers rationalize these changes, we introduce a preliminary framework and method that can be used by requirements engineers and their legal teams to identify relevant legal requirements and trace changes in requirements coverage. The framework includes a method to translate IT regulations into a legal requirements coverage model used to make coverage assertions about existing or planned IT systems. We evaluated the framework in a case study using three IT laws: California's Confidentiality of Medical Records Act, the U.S. Health Information Portability and Accountability Act (HIPAA) and amendments from the Health Information Technology for Economic and Clinical Health (HITECH) Act, and the India 2011 Information Technology Rules. Further, we demonstrate the framework using three scenarios: new product features are proposed; product-related services are outsourced abroad; and regulations change to address changes in the market.
{"title":"Assessing regulatory change through legal requirements coverage modeling","authors":"David G. Gordon, T. Breaux","doi":"10.1109/RE.2013.6636714","DOIUrl":"https://doi.org/10.1109/RE.2013.6636714","url":null,"abstract":"Developing global markets offer companies new opportunities to manufacture and sell information technology (IT) products in ways unforeseen by current laws and regulations. This innovation leads to changing requirements due to changes in product features, laws, or the locality where the product is sold or manufactured. To help developers rationalize these changes, we introduce a preliminary framework and method that can be used by requirements engineers and their legal teams to identify relevant legal requirements and trace changes in requirements coverage. The framework includes a method to translate IT regulations into a legal requirements coverage model used to make coverage assertions about existing or planned IT systems. We evaluated the framework in a case study using three IT laws: California's Confidentiality of Medical Records Act, the U.S. Health Information Portability and Accountability Act (HIPAA) and amendments from the Health Information Technology for Economic and Clinical Health (HITECH) Act, and the India 2011 Information Technology Rules. Further, we demonstrate the framework using three scenarios: new product features are proposed; product-related services are outsourced abroad; and regulations change to address changes in the market.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"11 1","pages":"145-154"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"82620158","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}
Reuse is a powerful tool for improving the productivity of software development. The paper puts forward arguments in favor of generic requirements reuse rooted in the vision that effectiveness requires a focus on coordinated composition of reusable artifacts across the whole software development life cycle. A survey of publications on requirements reuse from the International Requirements Engineering (RE) Conference series determines the research landscape in this area over the last twenty years, assessing the hypothesis that there is no or little research reported at RE about generic reuse of requirements models that spans the software development life cycle. The paper then outlines, for the RE community, a research agenda associated with the presented vision for such an approach to requirements reuse that builds on concern-orientation, i.e., the ability to modularize and compose important requirements concerns throughout the software development life cycle, and model-engineering principles. In addition, early research results are briefly presented that illustrate favorably the feasibility of such an approach.
{"title":"A vision for generic concern-oriented requirements reusere@21","authors":"G. Mussbacher, J. Kienzle","doi":"10.1109/RE.2013.6636724","DOIUrl":"https://doi.org/10.1109/RE.2013.6636724","url":null,"abstract":"Reuse is a powerful tool for improving the productivity of software development. The paper puts forward arguments in favor of generic requirements reuse rooted in the vision that effectiveness requires a focus on coordinated composition of reusable artifacts across the whole software development life cycle. A survey of publications on requirements reuse from the International Requirements Engineering (RE) Conference series determines the research landscape in this area over the last twenty years, assessing the hypothesis that there is no or little research reported at RE about generic reuse of requirements models that spans the software development life cycle. The paper then outlines, for the RE community, a research agenda associated with the presented vision for such an approach to requirements reuse that builds on concern-orientation, i.e., the ability to modularize and compose important requirements concerns throughout the software development life cycle, and model-engineering principles. In addition, early research results are briefly presented that illustrate favorably the feasibility of such an approach.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":"2013 1","pages":"238-249"},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"73872055","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
扫码关注我们
求助内容：
应助结果提醒方式：