Systems engineering is often ineffective in development environments where large, complex, brownfield systems of systems are evolved through parallel development of new capabilities in response to external, time-sensitive requirements. This paper defines a conceptual framework to improve that effectiveness and better integrate the systems engineering and software engineering processes. The framework is based on a services approach to systems engineering and the use of kanban techniques to schedule scarce enterprise systems engineering resources across multiple related systems and software development projects. The framework also addresses the differing value of work items to multiple stakeholders in the scheduling and coordination processes. Models and simulations are being used to capture, refine and validate the framework prior to in vivo experimentation.
{"title":"Improving systems engineering effectiveness in rapid response development environments","authors":"R. Turner, R. Madachy, Dan Ingold, J. Lane","doi":"10.5555/2664360.2664373","DOIUrl":"https://doi.org/10.5555/2664360.2664373","url":null,"abstract":"Systems engineering is often ineffective in development environments where large, complex, brownfield systems of systems are evolved through parallel development of new capabilities in response to external, time-sensitive requirements. This paper defines a conceptual framework to improve that effectiveness and better integrate the systems engineering and software engineering processes. The framework is based on a services approach to systems engineering and the use of kanban techniques to schedule scarce enterprise systems engineering resources across multiple related systems and software development projects. The framework also addresses the differing value of work items to multiple stakeholders in the scheduling and coordination processes. Models and simulations are being used to capture, refine and validate the framework prior to in vivo experimentation.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"41 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126936460","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225977
Pongtip Aroonvatanaporn, S. Koolmanojwong, B. Boehm
Team synchronization and stabilization are essential - especially for large software projects. However, often little is done to assess and reduce the uncertainties and knowledge gaps that exist within the project. As the project progresses through its life cycle, the team can gain more information about the project and team's capabilities. These necessary data can be obtained through performing assessments on the team and project. As these assessments procedures are often complex, discouraging, and difficult to analyze, an effective framework and tool support can greatly enhance the process. Hence, with improved assessment methods, software project teams can quickly gather the necessary data, determine the actions to improve performance, and result in an improved project outcome in the end. The COnstructive Team Improvement Process MOdel (COTIPMO) is a framework developed to effectively improve team synchronization and stabilization as well as project effort estimation and scoping by enabling software development teams to quickly track project progress, continuously assess team performance, and make adjustments to the project estimates as necessary.
{"title":"COTIPMO: A COnstructive Team Improvement Process MOdel","authors":"Pongtip Aroonvatanaporn, S. Koolmanojwong, B. Boehm","doi":"10.1109/ICSSP.2012.6225977","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225977","url":null,"abstract":"Team synchronization and stabilization are essential - especially for large software projects. However, often little is done to assess and reduce the uncertainties and knowledge gaps that exist within the project. As the project progresses through its life cycle, the team can gain more information about the project and team's capabilities. These necessary data can be obtained through performing assessments on the team and project. As these assessments procedures are often complex, discouraging, and difficult to analyze, an effective framework and tool support can greatly enhance the process. Hence, with improved assessment methods, software project teams can quickly gather the necessary data, determine the actions to improve performance, and result in an improved project outcome in the end. The COnstructive Team Improvement Process MOdel (COTIPMO) is a framework developed to effectively improve team synchronization and stabilization as well as project effort estimation and scoping by enabling software development teams to quickly track project progress, continuously assess team performance, and make adjustments to the project estimates as necessary.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"74 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122221838","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225962
J. Alegría, M. Bastarrica
Software product quality and project productivity require defining suitable software process models. The best process depends on the circumstances where it is applied. Typically, a process engineer tailors a specific process for each project or each project type from an organizational software process model. Frequently, tailoring is performed in an informal and reactive fashion, which is expensive, unrepeatable and error prone. Trying to deal with this challenge, we have built CASPER, a meta-process for defining adaptable software process models. This paper presents CASPER illustrating it using the ISPW-6 process. CASPER meta-process allows producing project specific processes in a planned way using four software process principles and a set of process practices that enable a feasible production strategy. According to its application to a canonical case, this paper concludes that CASPER enables a practical technique for tailoring a software process model.
{"title":"Building software process lines with CASPER","authors":"J. Alegría, M. Bastarrica","doi":"10.1109/ICSSP.2012.6225962","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225962","url":null,"abstract":"Software product quality and project productivity require defining suitable software process models. The best process depends on the circumstances where it is applied. Typically, a process engineer tailors a specific process for each project or each project type from an organizational software process model. Frequently, tailoring is performed in an informal and reactive fashion, which is expensive, unrepeatable and error prone. Trying to deal with this challenge, we have built CASPER, a meta-process for defining adaptable software process models. This paper presents CASPER illustrating it using the ISPW-6 process. CASPER meta-process allows producing project specific processes in a planned way using four software process principles and a set of process practices that enable a feasible production strategy. According to its application to a canonical case, this paper concludes that CASPER enables a practical technique for tailoring a software process model.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131157696","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225960
J. Snygg, Mira Kajko-Mattson, E. Hammargren
Organizations need guidance on how to efficiently manage emergency software problems. Such guidance, however, is available in only one process model today, CM3: Emergency Problem Management. In this paper, we compare CM3: Emergency Problem Management with an industrial software emergency process model. Our comparison results lead to the extensions of CM3: Emergency Problem Management with a pre-alert phase and a co-ordination of the management of emergency software problems with a crisis management process.
{"title":"Comparing two software emergency process models","authors":"J. Snygg, Mira Kajko-Mattson, E. Hammargren","doi":"10.1109/ICSSP.2012.6225960","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225960","url":null,"abstract":"Organizations need guidance on how to efficiently manage emergency software problems. Such guidance, however, is available in only one process model today, CM3: Emergency Problem Management. In this paper, we compare CM3: Emergency Problem Management with an industrial software emergency process model. Our comparison results lead to the extensions of CM3: Emergency Problem Management with a pre-alert phase and a co-ordination of the management of emergency software problems with a crisis management process.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"165 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122863602","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225973
Jürgen Münch
Software process simulation has been evolved towards a mature technology for analyzing the behavior of software processes: Methods for systematically developing simulators exist, tools for modeling and execution are available, models for nearly all kinds of processes have been created, and empirical evidence on the accuracy of many models has been gathered. However, software process simulation is still waiting for a breakthrough success. Although simulation is a technology that has been successfully established in many domains, software process simulation is not widely used in software engineering practice. Should we pivot or persevere? This article argues that it is necessary to use a rigorous approach for discovering “customers” of process simulators and finding out what they consider to be value. One mechanism to do this is to apply so-called “validated learning”, i.e., to apply an actionable learning approach to identify what is relevant and what is irrelevant by systematically testing value hypotheses. Doing this promises that simulation efforts can be concentrated on value-creation and that wrong avenues can be avoided. Besides this, the article sketched prerequisites and lessons learned that need to be considered when applying simulators in practice as well as upcoming opportunities for making software process simulation a success.
{"title":"Evolving process simulators by using validated learning","authors":"Jürgen Münch","doi":"10.1109/ICSSP.2012.6225973","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225973","url":null,"abstract":"Software process simulation has been evolved towards a mature technology for analyzing the behavior of software processes: Methods for systematically developing simulators exist, tools for modeling and execution are available, models for nearly all kinds of processes have been created, and empirical evidence on the accuracy of many models has been gathered. However, software process simulation is still waiting for a breakthrough success. Although simulation is a technology that has been successfully established in many domains, software process simulation is not widely used in software engineering practice. Should we pivot or persevere? This article argues that it is necessary to use a rigorous approach for discovering “customers” of process simulators and finding out what they consider to be value. One mechanism to do this is to apply so-called “validated learning”, i.e., to apply an actionable learning approach to identify what is relevant and what is irrelevant by systematically testing value hypotheses. Doing this promises that simulation efforts can be concentrated on value-creation and that wrong avenues can be avoided. Besides this, the article sketched prerequisites and lessons learned that need to be considered when applying simulators in practice as well as upcoming opportunities for making software process simulation a success.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"144 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131902155","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225954
Komlan Akpédjé Kedji, Rédouane Lbath, B. Coulette, M. Nassar, Laurent Baresse, F. Racaru
Software engineering projects are highly collaborative. Existing tools designed to support collaboration usually provide some specific service, and integration with other tools using data and events. However, Process-Centered Software Engineering Environments have traditionally been designed with different assumptions. The process is usually considered as the central aspect of the software project, and used as a center of control. As a result, great emphasis has been placed on the ability of PSEEs to invoke other tools, or use data generated by other tools. However, the integration in the other direction, that is, the ability of other tools to query the data managed by PSEEs (the process model), and hook into their extensions points, has been largely ignored, as it is not compatible with the vision of the PSEE as the central orchestrator of project support tools. We argue that this view has hindered the widespread adoption of process-based collaboration support tools by incurring too much adoption and switching costs, and propose a new process-based collaboration support architecture, backed by a process metamodel, which can easily be integrated with existing tools.
{"title":"Supporting collaborative development using process models: An integration-focused approach","authors":"Komlan Akpédjé Kedji, Rédouane Lbath, B. Coulette, M. Nassar, Laurent Baresse, F. Racaru","doi":"10.1109/ICSSP.2012.6225954","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225954","url":null,"abstract":"Software engineering projects are highly collaborative. Existing tools designed to support collaboration usually provide some specific service, and integration with other tools using data and events. However, Process-Centered Software Engineering Environments have traditionally been designed with different assumptions. The process is usually considered as the central aspect of the software project, and used as a center of control. As a result, great emphasis has been placed on the ability of PSEEs to invoke other tools, or use data generated by other tools. However, the integration in the other direction, that is, the ability of other tools to query the data managed by PSEEs (the process model), and hook into their extensions points, has been largely ignored, as it is not compatible with the vision of the PSEE as the central orchestrator of project support tools. We argue that this view has hindered the widespread adoption of process-based collaboration support tools by incurring too much adoption and switching costs, and propose a new process-based collaboration support architecture, backed by a process metamodel, which can easily be integrated with existing tools.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"45 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127838027","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225970
L. Osterweil
This talk explores the application of software engineering tools, technologies, and approaches to developing and continuously improving systems by focusing on the systems' processes. The systems addressed are those that are complex coordinations of the efforts of humans, hardware devices, and software subsystems, where humans are on the “inside”, playing critical roles in the functioning of the system and its processes. The talk suggests that in such cases, the collection of processes that use the system is tantamount to being the system itself, suggesting that improving the system's processes amounts to improving the system. Examples of systems from a variety of different domains that have been addressed and improved in this way will be presented and explored. The talk will suggest some additional untried software engineering ideas that seem promising as vehicles for supporting system development and improvement, and additional system domains that seem ripe for the application of this kind of software-based process technology. The talk will emphasize that these applications of software engineering approaches to systems has also had the desirable effect of adding to our understandings of software engineering. These understandings have created a software engineering research agenda that is complementary to, and synergistic with, agendas for applying software engineering to system development and improvement.
{"title":"System processes are software too","authors":"L. Osterweil","doi":"10.1109/ICSSP.2012.6225970","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225970","url":null,"abstract":"This talk explores the application of software engineering tools, technologies, and approaches to developing and continuously improving systems by focusing on the systems' processes. The systems addressed are those that are complex coordinations of the efforts of humans, hardware devices, and software subsystems, where humans are on the “inside”, playing critical roles in the functioning of the system and its processes. The talk suggests that in such cases, the collection of processes that use the system is tantamount to being the system itself, suggesting that improving the system's processes amounts to improving the system. Examples of systems from a variety of different domains that have been addressed and improved in this way will be presented and explored. The talk will suggest some additional untried software engineering ideas that seem promising as vehicles for supporting system development and improvement, and additional system domains that seem ripe for the application of this kind of software-based process technology. The talk will emphasize that these applications of software engineering approaches to systems has also had the desirable effect of adding to our understandings of software engineering. These understandings have created a software engineering research agenda that is complementary to, and synergistic with, agendas for applying software engineering to system development and improvement.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114342985","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225964
Paula Monteiro, Pedro Borges, R. J. Machado, Pedro Ribeiro
Software projects are always increasing their complexity. The complexity of projects arises due to the increased sophistication of software applications and of their implemented features. However, most of the projects are developed by small organizations. Since these companies have a reduced dimension, the number of individuals that constitute each software development teams will also be significantly reduced. This paper describes a Rational Unified Process (RUP) configuration composed by a reduced set of RUP roles. This configuration may easily be adopted by a small software development team during the project execution period. Additionally, we have characterized each role in this reduced model by identifying the corresponding activities in charge and by creating individual sheets detailing their responsibilities. An initial assessment of the effectiveness of this RUP configuration was performed using CMMI-DEV maturity level 2 (ML2) as a reference model.
{"title":"A reduced set of RUP roles to small software development teams","authors":"Paula Monteiro, Pedro Borges, R. J. Machado, Pedro Ribeiro","doi":"10.1109/ICSSP.2012.6225964","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225964","url":null,"abstract":"Software projects are always increasing their complexity. The complexity of projects arises due to the increased sophistication of software applications and of their implemented features. However, most of the projects are developed by small organizations. Since these companies have a reduced dimension, the number of individuals that constitute each software development teams will also be significantly reduced. This paper describes a Rational Unified Process (RUP) configuration composed by a reduced set of RUP roles. This configuration may easily be adopted by a small software development team during the project execution period. Additionally, we have characterized each role in this reduced model by identifying the corresponding activities in charge and by creating individual sheets detailing their responsibilities. An initial assessment of the effectiveness of this RUP configuration was performed using CMMI-DEV maturity level 2 (ML2) as a reference model.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125208202","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225953
Xiang Zhao, L. Osterweil
This paper presents the definition of a process for performing rework, and a tool that executes the process in order to support humans seeking help in being sure that they are carrying out rework completely and correctly. The process definition treats rework as the reinstantiation of previously-performed activities in new contexts, which requires the careful specification and management of the values of the artifacts that comprise key process execution history and contextual information. The rework tool exploits access to this information to provide human reworkers with guidance about the rework tasks to be done and with context and history information expected to be useful in guiding superior rework decisions. The paper presents a detailed example of the use of the process and tool in supporting a particular kind of rework, namely the refactoring of the design of an Object-Oriented program.
{"title":"An approach to modeling and supporting the rework process in refactoring","authors":"Xiang Zhao, L. Osterweil","doi":"10.1109/ICSSP.2012.6225953","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225953","url":null,"abstract":"This paper presents the definition of a process for performing rework, and a tool that executes the process in order to support humans seeking help in being sure that they are carrying out rework completely and correctly. The process definition treats rework as the reinstantiation of previously-performed activities in new contexts, which requires the careful specification and management of the values of the artifacts that comprise key process execution history and contextual information. The rework tool exploits access to this information to provide human reworkers with guidance about the rework tasks to be done and with context and history information expected to be useful in guiding superior rework decisions. The paper presents a detailed example of the use of the process and tool in supporting a particular kind of rework, namely the refactoring of the design of an Object-Oriented program.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130353020","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 : 2012-06-02DOI: 10.1109/ICSSP.2012.6225979
He Zhang, G. Klein, M. Staples, June Andronick, Liming Zhu, Rafal Kolanski
The L4.verified project successfully completed a large-scale machine-checked formal verification at the code level of the functional correctness of the seL4 operating system microkernel. The project applied a middle-out process, which is significantly different from conventional software development processes. This paper reports a simulation model of this process; it is the first simulation model of a formal verification process. The model aims to support further understanding and investigation of the dynamic characteristics of the process and to support planning and optimization of future process enactment. We based the simulation model on a descriptive process model and information from project logs, meeting notes, and version control data over the project's history. Simulation results from the initial version of the model show the impact of complex coupling among the activities and artifacts, and frequent parallel as well as iterative work during execution. We examine some possible improvements on the formal verification process in light of the simulation results.
{"title":"Simulation modeling of a large-scale formal verification process","authors":"He Zhang, G. Klein, M. Staples, June Andronick, Liming Zhu, Rafal Kolanski","doi":"10.1109/ICSSP.2012.6225979","DOIUrl":"https://doi.org/10.1109/ICSSP.2012.6225979","url":null,"abstract":"The L4.verified project successfully completed a large-scale machine-checked formal verification at the code level of the functional correctness of the seL4 operating system microkernel. The project applied a middle-out process, which is significantly different from conventional software development processes. This paper reports a simulation model of this process; it is the first simulation model of a formal verification process. The model aims to support further understanding and investigation of the dynamic characteristics of the process and to support planning and optimization of future process enactment. We based the simulation model on a descriptive process model and information from project logs, meeting notes, and version control data over the project's history. Simulation results from the initial version of the model show the impact of complex coupling among the activities and artifacts, and frequent parallel as well as iterative work during execution. We examine some possible improvements on the formal verification process in light of the simulation results.","PeriodicalId":166836,"journal":{"name":"2012 International Conference on Software and System Process (ICSSP)","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132942727","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
扫码关注我们
求助内容：
应助结果提醒方式：