The relationships and the features of integration between Enterprise ProcessMonitoring and Controlling System (EPMCS) and Enterprise Process Related Applications (EPRA) wereanalyzed. An integration architecture center...The relationships and the features of integration between Enterprise ProcessMonitoring and Controlling System (EPMCS) and Enterprise Process Related Applications (EPRA) wereanalyzed. An integration architecture centered on EPMCS was presented, in which there were fourlayers to connect from EPMCS to EPRA: EPMCS, application integration layer, transport layer andEPRA, and there were four layers used to etstablish integration: presentation layer, function layer,data layer and system layer. The frameworks to connect EPMCS and EPRA were designed, thatEnterprise-Independent Model (EIM), Enterprise-Specific Model (ESM) and meta-model to describe thesetwo models were defined. The method to integrate data based on XML was designed to exchange datafrom EPMCS to EPRA according to the mapping between EIM and ESM. The approches are suitable forintegrating EPMCS and systems in Product Data Management (PDM), project management and enterprisebusiness management.展开更多
The layered software architecture is the model commonly adopted for the development of information systems since it favors the modularity and the scalability of the systems. On the other hand, the emergence of model e...The layered software architecture is the model commonly adopted for the development of information systems since it favors the modularity and the scalability of the systems. On the other hand, the emergence of model engineering aims to raise the level of abstraction to allow developers to reason on models, and less in code. The research question is to combine the two approaches to facilitate the work of developers. The proposal resulting from this study is based on a set of concepts defined using the UML profiles. These concepts include services, business components, and data persistence. Then the Kruchten model is adopted to represent the development cycle according to several views, each view being represented by UML diagrams derived from the previously defined profiles. Finally, rules are available for checking inter-view consistency, from refinement to code generation. The result is a step towards the definition of a domain specific ADL and a development process as much as it includes the expected characteristics of such a language, namely: the fundamental concepts, the support tools and the multiview development.展开更多
文摘The relationships and the features of integration between Enterprise ProcessMonitoring and Controlling System (EPMCS) and Enterprise Process Related Applications (EPRA) wereanalyzed. An integration architecture centered on EPMCS was presented, in which there were fourlayers to connect from EPMCS to EPRA: EPMCS, application integration layer, transport layer andEPRA, and there were four layers used to etstablish integration: presentation layer, function layer,data layer and system layer. The frameworks to connect EPMCS and EPRA were designed, thatEnterprise-Independent Model (EIM), Enterprise-Specific Model (ESM) and meta-model to describe thesetwo models were defined. The method to integrate data based on XML was designed to exchange datafrom EPMCS to EPRA according to the mapping between EIM and ESM. The approches are suitable forintegrating EPMCS and systems in Product Data Management (PDM), project management and enterprisebusiness management.
文摘The layered software architecture is the model commonly adopted for the development of information systems since it favors the modularity and the scalability of the systems. On the other hand, the emergence of model engineering aims to raise the level of abstraction to allow developers to reason on models, and less in code. The research question is to combine the two approaches to facilitate the work of developers. The proposal resulting from this study is based on a set of concepts defined using the UML profiles. These concepts include services, business components, and data persistence. Then the Kruchten model is adopted to represent the development cycle according to several views, each view being represented by UML diagrams derived from the previously defined profiles. Finally, rules are available for checking inter-view consistency, from refinement to code generation. The result is a step towards the definition of a domain specific ADL and a development process as much as it includes the expected characteristics of such a language, namely: the fundamental concepts, the support tools and the multiview development.
