The increasing entwinement of products and services in combined offers – so called Product-Service Systems (PSS) – leads to various requirements regarding the modelling of those systems. Due to these requirements, software support is needed for customer-specific configuration of complex PSS. To provide such software a formal description of the structure of products and services is required. Furthermore, complex logical interdependencies between products and services need to be described. Based on an existing service modelling notation the following paper develops a holistic notation for PSS. To describe the interdependencies within PSS, dependency rules are formally specified.
{"title":"Formal Modelling of Components and Dependencies for Configuring Product-Service-Systems","authors":"Stephan Klingner, Michael Becker","doi":"10.18417/emisa.7.1.3","DOIUrl":"https://doi.org/10.18417/emisa.7.1.3","url":null,"abstract":"The increasing entwinement of products and services in combined offers – so called Product-Service Systems (PSS) – leads to various requirements regarding the modelling of those systems. Due to these requirements, software support is needed for customer-specific configuration of complex PSS. To provide such software a formal description of the structure of products and services is required. Furthermore, complex logical interdependencies between products and services need to be described. Based on an existing service modelling notation the following paper develops a holistic notation for PSS. To describe the interdependencies within PSS, dependency rules are formally specified.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114065158","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}
IT service providers are increasingly urged to stringently align their service portfolio with the IT support of their customers’ business processes. Consequently, both IT expenses and its strategic contribution to value creation are expected to become subject to heightened transparency. Yet, in order to allow for standardised on-demand service request processing within the meaning of IT industrialisation, these services appear too adapted to individual customer needs, particularly as they are subject to continuous changes in business requirements. In order to address this issue, a three-phase procedural model of IT service agreement configuration is introduced: IT services thus remain transformable and configurable via predefined complementary services which are selected by configuring a customer’s individual service directory. In addition, the reutilisation of modular commitments in order to compose service specifications aims to maintain standardised IT operations. Serving as a procedural reference model, these configuration phases are introduced in detail regarding activities, roles, techniques and data structure as developed and implemented in Action Research cooperation with two IT providers.
{"title":"Balancing Customer Requirements and IT Service Standardisation - A Procedural Reference Model for Individualised IT Service Agreement Configurations","authors":"Henrik Brocke, Falk Uebernickel, W. Brenner","doi":"10.18417/emisa.6.2.1","DOIUrl":"https://doi.org/10.18417/emisa.6.2.1","url":null,"abstract":"IT service providers are increasingly urged to stringently align their service portfolio with the IT support of their customers’ business processes. Consequently, both IT expenses and its strategic contribution to value creation are expected to become subject to heightened transparency. Yet, in order to allow for standardised on-demand service request processing within the meaning of IT industrialisation, these services appear too adapted to individual customer needs, particularly as they are subject to continuous changes in business requirements. In order to address this issue, a three-phase procedural model of IT service agreement configuration is introduced: IT services thus remain transformable and configurable via predefined complementary services which are selected by configuring a customer’s individual service directory. In addition, the reutilisation of modular commitments in order to compose service specifications aims to maintain standardised IT operations. Serving as a procedural reference model, these configuration phases are introduced in detail regarding activities, roles, techniques and data structure as developed and implemented in Action Research cooperation with two IT providers.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"48 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129119640","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}
Integrated process support is highly desirable in environments where data related to a particular business process are scattered over distributed, heterogeneous information systems. A business process monitoring component is a much-needed module in order to provide an integrated view on all these process data. Regarding process visualisation and process data integration, access control (AC) issues are very important but also quite complex to be addressed. A major problem arises from the fact that the involved information systems are usually based on heterogeneous AC components. For several reasons, the only feasible way to tackle the problem of AC at the process monitoring level is to define access rights for the process monitoring component, hence getting rid of the burden to map access rights from the information system level. This paper presents the Proviado process visualisation framework and discusses requirements for AC in process monitoring, which we derived from our case studies in the automotive domain. It then presents alternative approaches for AC: the view-based and the object-based approach. The latter is retained, and a core AC model is proposed for the definition of access rights that meet the derived requirements. AC mechanisms provided within the core model are key ingredients for the definition of model extensions.
{"title":"The Proviado Access Control Model for Business Process Monitoring Components","authors":"M. Reichert, Sarita Bassil, R. Bobrik, T. Bauer","doi":"10.18417/emisa.5.3.4","DOIUrl":"https://doi.org/10.18417/emisa.5.3.4","url":null,"abstract":"Integrated process support is highly desirable in environments where data related to a particular business process are scattered over distributed, heterogeneous information systems. A business process monitoring component is a much-needed module in order to provide an integrated view on all these process data. Regarding process visualisation and process data integration, access control (AC) issues are very important but also quite complex to be addressed. A major problem arises from the fact that the involved information systems are usually based on heterogeneous AC components. For several reasons, the only feasible way to tackle the problem of AC at the process monitoring level is to define access rights for the process monitoring component, hence getting rid of the burden to map access rights from the information system level. This paper presents the Proviado process visualisation framework and discusses requirements for AC in process monitoring, which we derived from our case studies in the automotive domain. It then presents alternative approaches for AC: the view-based and the object-based approach. The latter is retained, and a core AC model is proposed for the definition of access rights that meet the derived requirements. AC mechanisms provided within the core model are key ingredients for the definition of model extensions.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"31 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2010-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127634351","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}
Sören Balko, A. T. Hofstede, A. Barros, M. Rosa, M. Adams
Vendors provide reference process models as consolidated, off-the-shelf solutions to capture best practices in a given industry domain. Customers can then adapt these models to suit their specific requirements. Traditional process flexibility approaches facilitate this operation, but do not fully address it as they do not sufficiently take controlled change guided by vendors’ reference models into account. This tension between the customer’s freedom of adapting reference models, and the ability to incorporate with relatively low effort vendor-initiated reference model changes, thus needs to be carefully balanced. This paper introduces process extensibility as a new paradigm for customising reference processes and managing their evolution over time. Process extensibility mandates a clear recognition of the different responsibilities and interests of reference model vendors and consumers, and is concerned with keeping the effort of customer-side reference model adaptations low while allowing sufficient room for model change.
{"title":"Business Process Extensibility","authors":"Sören Balko, A. T. Hofstede, A. Barros, M. Rosa, M. Adams","doi":"10.18417/emisa.5.3.1","DOIUrl":"https://doi.org/10.18417/emisa.5.3.1","url":null,"abstract":"Vendors provide reference process models as consolidated, off-the-shelf solutions to capture best practices in a given industry domain. Customers can then adapt these models to suit their specific requirements. Traditional process flexibility approaches facilitate this operation, but do not fully address it as they do not sufficiently take controlled change guided by vendors’ reference models into account. This tension between the customer’s freedom of adapting reference models, and the ability to incorporate with relatively low effort vendor-initiated reference model changes, thus needs to be carefully balanced. This paper introduces process extensibility as a new paradigm for customising reference processes and managing their evolution over time. Process extensibility mandates a clear recognition of the different responsibilities and interests of reference model vendors and consumers, and is concerned with keeping the effort of customer-side reference model adaptations low while allowing sufficient room for model change.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2010-07-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122460550","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 architecture frameworks sometimes provide an additional architectural layer between business-oriented artefact types (e.g., business processes, organizational units) and technical artefact types (e.g., software components, data structures). This "integration" or "alignment" layer is intended to bridge the gap, which results from different life cycles, different ownerships, and other sources of IT/business misalignment. The development of specific models and artefact types on the integration layer is in its early stage. Existing methods for information systems design constitute a first starting point. However, most of them lack a clear differentiation between the integration layer and the software layer and therefore cannot be reused as-is. This paper contributes to the research of design methods, models, and artefact type specifications for the integration layer. The focus lies primarily on the alignment of organizational architecture and structural software architecture, two important components of enterprise architecture. A comparison of organizational and software architecture design methods yields that both types of structures are usually constructed according to different design criteria so that un-aligned architectures result. Traditional integration artefacts, such as "logical" applications, which specify coherent areas of ownership over software artefacts, are too closely linked to actual software system structures and therefore usually fail in aligning with the organizational architecture. It is argued in this paper that instead, integration artefacts should be much more decoupled from actual software structures.
{"title":"On the Interplay of Organizational Architecture and Software Architecture","authors":"Wojciech Ganczarski, R. Winter","doi":"10.18417/emisa.3.1.3","DOIUrl":"https://doi.org/10.18417/emisa.3.1.3","url":null,"abstract":"Enterprise architecture frameworks sometimes provide an additional architectural layer between business-oriented artefact types (e.g., business processes, organizational units) and technical artefact types (e.g., software components, data structures). This \"integration\" or \"alignment\" layer is intended to bridge the gap, which results from different life cycles, different ownerships, and other sources of IT/business misalignment. The development of specific models and artefact types on the integration layer is in its early stage. Existing methods for information systems design constitute a first starting point. However, most of them lack a clear differentiation between the integration layer and the software layer and therefore cannot be reused as-is. This paper contributes to the research of design methods, models, and artefact type specifications for the integration layer. The focus lies primarily on the alignment of organizational architecture and structural software architecture, two important components of enterprise architecture. A comparison of organizational and software architecture design methods yields that both types of structures are usually constructed according to different design criteria so that un-aligned architectures result. Traditional integration artefacts, such as \"logical\" applications, which specify coherent areas of ownership over software artefacts, are too closely linked to actual software system structures and therefore usually fail in aligning with the organizational architecture. It is argued in this paper that instead, integration artefacts should be much more decoupled from actual software structures.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116034627","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}
A code multiplexing transmitting apparatus spread-spectrum modulates transmission data of a plurality of channels by spreading codes that differ from one another, combines the spread-spectrum signals of each of the channels and transmits the resultant spread-spectrum modulated signal. A spread-spectrum modulating unit for each channel includes a phase shifter for shifting, by a predetermined angle channel by channel, the phase of a position vector of the spread-spectrum modulated signal of each channel. As the result of such phase control, the phases of pilot signal portions of the spread-spectrum modulated signals of the respective channels are shifted relative to one another so that the peak values of the code-multiplexed signal can be suppressed.
{"title":"Classification of Enterprise Architecture - An Exploratory Analysis","authors":"Stephan Aier, Christian Riege, R. Winter","doi":"10.18417/emisa.3.1.2","DOIUrl":"https://doi.org/10.18417/emisa.3.1.2","url":null,"abstract":"A code multiplexing transmitting apparatus spread-spectrum modulates transmission data of a plurality of channels by spreading codes that differ from one another, combines the spread-spectrum signals of each of the channels and transmits the resultant spread-spectrum modulated signal. A spread-spectrum modulating unit for each channel includes a phase shifter for shifting, by a predetermined angle channel by channel, the phase of a position vector of the spread-spectrum modulated signal of each channel. As the result of such phase control, the phases of pilot signal portions of the spread-spectrum modulated signals of the respective channels are shifted relative to one another so that the peak values of the code-multiplexed signal can be suppressed.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"68 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-02-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133770636","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 architecture is gaining acceptance as an approach to manage change and foster IT/business alignment by (1) propagating strategy and process changes to the software and infrastructure level, by (2) supporting consistent business transformation enabled by technology innovations, and by (3) decoupling business-oriented and technology-oriented architectures. Due to constant change in business as well as in technology, enterprise architecture management is a permanent process rather than a one-time effort. To keep enterprise architecture models up-to-date, a well-engineered maintenance concept including processes, roles and schedules is needed. This paper discusses the shortcomings of existing approaches to enterprise architecture model maintenance, proposes a federated approach, and reports on its implementation at a large financial service provider.
{"title":"A Federated Approach to Enterprise Architecture Model Maintenance","authors":"R. Fischer, Stephan Aier, R. Winter","doi":"10.18417/emisa.2.2.2","DOIUrl":"https://doi.org/10.18417/emisa.2.2.2","url":null,"abstract":"Enterprise architecture is gaining acceptance as an approach to manage change and foster IT/business alignment by (1) propagating strategy and process changes to the software and infrastructure level, by (2) supporting consistent business transformation enabled by technology innovations, and by (3) decoupling business-oriented and technology-oriented architectures. Due to constant change in business as well as in technology, enterprise architecture management is a permanent process rather than a one-time effort. To keep enterprise architecture models up-to-date, a well-engineered maintenance concept including processes, roles and schedules is needed. This paper discusses the shortcomings of existing approaches to enterprise architecture model maintenance, proposes a federated approach, and reports on its implementation at a large financial service provider.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134296380","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}
F. Arbab, F. S. Boer, M. Bonsangue, M. Lankhorst, H. Proper, Leendert van der Torre
The diversity of architectural models in enterprise architecture poses a problem to their integration. Without such integration the effectiveness of these models in the process of architecting enterprises diminishes. In this paper we make a distinction between three classes of models. We will illustrate how the distinctions can be used for model integration within the architectural approach. Symbolic models express properties of architec-tures of systems, semantic models interpret the symbols used in symbolic models, and subjective models are purposely abstracted conceptions of a domain. Building on results obtained in the ArchiMate project, we il-lustrate how symbolic models can be integrated using an architectural language, how integrated models can be updated using the distinction between symbolic models and their visualization, and how semantic models can be integrated using a new kind of enterprise analysis called semantic analysis.
{"title":"Integrating Architectural Models - Symbolic, Semantic and Subjective Models in Enterprise Architecture","authors":"F. Arbab, F. S. Boer, M. Bonsangue, M. Lankhorst, H. Proper, Leendert van der Torre","doi":"10.18417/emisa.2.1.4","DOIUrl":"https://doi.org/10.18417/emisa.2.1.4","url":null,"abstract":"The diversity of architectural models in enterprise architecture poses a problem to their integration. Without such integration the effectiveness of these models in the process of architecting enterprises diminishes. In this paper we make a distinction between three classes of models. We will illustrate how the distinctions can be used for model integration within the architectural approach. Symbolic models express properties of architec-tures of systems, semantic models interpret the symbols used in symbolic models, and subjective models are purposely abstracted conceptions of a domain. Building on results obtained in the ArchiMate project, we il-lustrate how symbolic models can be integrated using an architectural language, how integrated models can be updated using the distinction between symbolic models and their visualization, and how semantic models can be integrated using a new kind of enterprise analysis called semantic analysis.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"68 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-06-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124562405","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 20 workflow patterns proposed by van der Aalst et al. provide a comprehensive benchmark for comparing process modelling languages. In this article, we discuss workflow pattern support of Event-Driven Process Chains (EPCs). Building on this analysis, we propose three extensions to EPCs in order to provide for workflow pattern support. These are the introduction of the so-called empty connector; inclusion of multiple instantiation concepts; and a cancellation construct. As both the latter are inspired by YAWL, we refer to this new class of EPCs as Yet Another Event-driven Process Chain (yEPC). Furthermore, we sketch how a transformation to YAWL can be used to specify the semantics of yEPCs.
van der Aalst等人提出的20种工作流模式为比较流程建模语言提供了一个全面的基准。在本文中，我们将讨论事件驱动流程链(epc)的工作流模式支持。在此分析的基础上，我们建议对epc进行三种扩展，以提供工作流模式支持。这些都是介绍所谓的空连接器;包含多个实例化概念;还有一个消去结构。由于后者都受到了YAWL的启发，我们将这类新的epc称为另一个事件驱动流程链(yEPC)。此外，我们概述了如何使用到YAWL的转换来指定yepc的语义。
{"title":"Yet Another Event-driven Process Chain - Modelling Workflow Patterns with yEPCs","authors":"J. Mendling, G. Neumann, Markus Nüttgens","doi":"10.18417/emisa.1.1.1","DOIUrl":"https://doi.org/10.18417/emisa.1.1.1","url":null,"abstract":"The 20 workflow patterns proposed by van der Aalst et al. provide a comprehensive benchmark for comparing process modelling languages. In this article, we discuss workflow pattern support of Event-Driven Process Chains (EPCs). Building on this analysis, we propose three extensions to EPCs in order to provide for workflow pattern support. These are the introduction of the so-called empty connector; inclusion of multiple instantiation concepts; and a cancellation construct. As both the latter are inspired by YAWL, we refer to this new class of EPCs as Yet Another Event-driven Process Chain (yEPC). Furthermore, we sketch how a transformation to YAWL can be used to specify the semantics of yEPCs.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"119 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133237931","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}
In this paper we analyse the conceptualisation of modelling methods. Thereby we understand, how the components of a specifi c implementation platform support the design of modelling methods. For this purpose we use the ADOxx meta modelling platform and investigate, how four selected functionalities of enterprise information systems for supporting user interaction, process-based optimisation, interfaces to other systems, and complex analyses are realised. We discuss these four functionalities by reverting to excerpts of the visual representation of modelling methods from the areas of requirements engineering, business process management, e-learning, and enterprise architecture management. This permits us to highlight the interdependencies between the modelling language, the modelling procedure, mechanisms and algorithms and the functionalities of the underlying technical platform that have to be taken into account during the conceptualisation.
{"title":"On the Conceptualisation of Modelling Methods Using the ADOxx Meta Modelling Platform","authors":"Hans-Georg Fill, D. Karagiannis","doi":"10.18417/emisa.8.1.1","DOIUrl":"https://doi.org/10.18417/emisa.8.1.1","url":null,"abstract":"In this paper we analyse the conceptualisation of modelling methods. Thereby we understand, how the components of a specifi c implementation platform support the design of modelling methods. For this purpose we use the ADOxx meta modelling platform and investigate, how four selected functionalities of enterprise information systems for supporting user interaction, process-based optimisation, interfaces to other systems, and complex analyses are realised. We discuss these four functionalities by reverting to excerpts of the visual representation of modelling methods from the areas of requirements engineering, business process management, e-learning, and enterprise architecture management. This permits us to highlight the interdependencies between the modelling language, the modelling procedure, mechanisms and algorithms and the functionalities of the underlying technical platform that have to be taken into account during the conceptualisation.","PeriodicalId":186216,"journal":{"name":"Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model.","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115663261","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
扫码关注我们
求助内容：
应助结果提醒方式：