{"title":"面向工作流协作的三层业务流程体系结构","authors":"R. Saga, Naoto Okada, H. Tsuji","doi":"10.1109/ETFA.2006.355205","DOIUrl":null,"url":null,"abstract":"This paper proposes architecture for workflow cooperation among organizations. To design system architecture, business processes are classified and systematized. The proposed architecture consists of three components: request message converter, business process auto-generator and business process manager. Using WordNet for pair of words, the first component converts a message to a trigger for the second component. Then according to MIT Process Handbook for business process repository, the second component automatically generates a business process instance in an operating order. Finally, referring to case base, the third component decides and manages proper schedule and transactors for the instance from case-base. In an experiment, this paper also validates the proposed architecture and discusses its feasibility.","PeriodicalId":431393,"journal":{"name":"2006 IEEE Conference on Emerging Technologies and Factory Automation","volume":"19 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2006-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"Three Layered Business Process Architecture for Workflow Cooperation\",\"authors\":\"R. Saga, Naoto Okada, H. Tsuji\",\"doi\":\"10.1109/ETFA.2006.355205\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"This paper proposes architecture for workflow cooperation among organizations. To design system architecture, business processes are classified and systematized. The proposed architecture consists of three components: request message converter, business process auto-generator and business process manager. Using WordNet for pair of words, the first component converts a message to a trigger for the second component. Then according to MIT Process Handbook for business process repository, the second component automatically generates a business process instance in an operating order. Finally, referring to case base, the third component decides and manages proper schedule and transactors for the instance from case-base. In an experiment, this paper also validates the proposed architecture and discusses its feasibility.\",\"PeriodicalId\":431393,\"journal\":{\"name\":\"2006 IEEE Conference on Emerging Technologies and Factory Automation\",\"volume\":\"19 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2006-09-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2006 IEEE Conference on Emerging Technologies and Factory Automation\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ETFA.2006.355205\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2006 IEEE Conference on Emerging Technologies and Factory Automation","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ETFA.2006.355205","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Three Layered Business Process Architecture for Workflow Cooperation
This paper proposes architecture for workflow cooperation among organizations. To design system architecture, business processes are classified and systematized. The proposed architecture consists of three components: request message converter, business process auto-generator and business process manager. Using WordNet for pair of words, the first component converts a message to a trigger for the second component. Then according to MIT Process Handbook for business process repository, the second component automatically generates a business process instance in an operating order. Finally, referring to case base, the third component decides and manages proper schedule and transactors for the instance from case-base. In an experiment, this paper also validates the proposed architecture and discusses its feasibility.