{"title":"实现互操作性的MDSOA","authors":"X. Larrucea, Gorka Benguria, Stefan Schuster","doi":"10.1109/ICCBSS.2007.21","DOIUrl":null,"url":null,"abstract":"Summary form only given. This poster presents an experience, on gathering business needs in business models adapted to the business expert language and translating these needs into a service oriented architecture (SOA) in a systematic way. The poster introduces the current situation highlighting three interoperability problems: (1) Organisations do not use a standard, unified and widely adopted business process definition language. Organisations want a common understanding of the process where they are involved from different perspectives; (2) Information systems are implemented to address specific requirements, ignoring future integration needs by using proprietary formats, and ad-hoc communication strategies and protocols; and (3) Information systems do not, clearly, support the business processes. There is a gap between business process models and their information systems implementations. The approach shown in this poster is based on the usage of the SOA paradigm from a model driven point of view: a model driven service oriented architecture (MDSOA) framework. Based on the MDA specification we have identified a metamodel for each of the three abstraction levels: (1) POP* (process, organisation, product) is selected as the metamodel to represent and exchange business processes. POP* is the unified enterprise modelling language (UEML) successor. POP* metamodel represents the starting point; (2) PIM4SOA (platform independent model for service oriented architecture) (Benguria et al., 2006) is a metamodel to represent service, process, information and quality of service elements; and (3) WSDL (Web service description language) and BPEL (business process execution language) are platform specific languages","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":"6 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"8","resultStr":"{\"title\":\"MDSOA for Achieving Interoperability\",\"authors\":\"X. Larrucea, Gorka Benguria, Stefan Schuster\",\"doi\":\"10.1109/ICCBSS.2007.21\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Summary form only given. This poster presents an experience, on gathering business needs in business models adapted to the business expert language and translating these needs into a service oriented architecture (SOA) in a systematic way. The poster introduces the current situation highlighting three interoperability problems: (1) Organisations do not use a standard, unified and widely adopted business process definition language. Organisations want a common understanding of the process where they are involved from different perspectives; (2) Information systems are implemented to address specific requirements, ignoring future integration needs by using proprietary formats, and ad-hoc communication strategies and protocols; and (3) Information systems do not, clearly, support the business processes. There is a gap between business process models and their information systems implementations. The approach shown in this poster is based on the usage of the SOA paradigm from a model driven point of view: a model driven service oriented architecture (MDSOA) framework. Based on the MDA specification we have identified a metamodel for each of the three abstraction levels: (1) POP* (process, organisation, product) is selected as the metamodel to represent and exchange business processes. POP* is the unified enterprise modelling language (UEML) successor. POP* metamodel represents the starting point; (2) PIM4SOA (platform independent model for service oriented architecture) (Benguria et al., 2006) is a metamodel to represent service, process, information and quality of service elements; and (3) WSDL (Web service description language) and BPEL (business process execution language) are platform specific languages\",\"PeriodicalId\":326403,\"journal\":{\"name\":\"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)\",\"volume\":\"6 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2007-02-26\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"8\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICCBSS.2007.21\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICCBSS.2007.21","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 8
摘要
只提供摘要形式。这张海报展示了一个经验,关于在适应业务专家语言的业务模型中收集业务需求,并以系统的方式将这些需求转换为面向服务的体系结构(SOA)。海报介绍了目前的情况,突出了三个互操作性问题:(1)组织没有使用标准、统一和广泛采用的业务流程定义语言。组织希望对从不同角度参与的过程有一个共同的理解;(2)信息系统的实现是为了满足特定的需求,而忽略了未来的集成需求,使用专有格式和自组织通信策略和协议;(3)信息系统显然不能支持业务流程。业务流程模型和它们的信息系统实现之间存在差距。这张海报中展示的方法是基于从模型驱动的角度对SOA范例的使用:模型驱动的面向服务的体系结构(MDSOA)框架。基于MDA规范,我们已经为三个抽象级别中的每一个定义了一个元模型:(1)选择POP*(过程、组织、产品)作为表示和交换业务过程的元模型。POP*是统一企业建模语言(UEML)的继承者。POP*元模型表示起点;(2) PIM4SOA(面向服务架构的平台独立模型)(Benguria et al., 2006)是表示服务、流程、信息和服务元素质量的元模型;(3) WSDL (Web服务描述语言)和BPEL(业务流程执行语言)是平台特定的语言
Summary form only given. This poster presents an experience, on gathering business needs in business models adapted to the business expert language and translating these needs into a service oriented architecture (SOA) in a systematic way. The poster introduces the current situation highlighting three interoperability problems: (1) Organisations do not use a standard, unified and widely adopted business process definition language. Organisations want a common understanding of the process where they are involved from different perspectives; (2) Information systems are implemented to address specific requirements, ignoring future integration needs by using proprietary formats, and ad-hoc communication strategies and protocols; and (3) Information systems do not, clearly, support the business processes. There is a gap between business process models and their information systems implementations. The approach shown in this poster is based on the usage of the SOA paradigm from a model driven point of view: a model driven service oriented architecture (MDSOA) framework. Based on the MDA specification we have identified a metamodel for each of the three abstraction levels: (1) POP* (process, organisation, product) is selected as the metamodel to represent and exchange business processes. POP* is the unified enterprise modelling language (UEML) successor. POP* metamodel represents the starting point; (2) PIM4SOA (platform independent model for service oriented architecture) (Benguria et al., 2006) is a metamodel to represent service, process, information and quality of service elements; and (3) WSDL (Web service description language) and BPEL (business process execution language) are platform specific languages