{"title":"RM-ODP与企业架构的案例研究","authors":"Daisuke Hashimoto, Akira Tanaka, Masanori Yokoyama","doi":"10.1109/EDOCW.2007.10","DOIUrl":null,"url":null,"abstract":"Like RM-ODP [1], enterprise architecture (or EA for short) has its own perspectives as a basic construct for its architecture definition to represent areas of concern. In this paper, difference between RM-ODP and one concrete example EA, and applicability of Use of UML for ODP system specifications [2] (or UML4ODP in short) standard to the example EA, are discussed. Several additional diagrams that exist in EA guideline book in Japan [4] but not in UML4ODP are suggested as complementary additions to existing diagrams. The work is based on the UML4JEA Profile [5][6] developed by Interoperability Technology Association for Information Processing, Japan.","PeriodicalId":181454,"journal":{"name":"2007 Eleventh International IEEE EDOC Conference Workshop","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2007-10-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":"{\"title\":\"Case study on RM-ODP and Enterprise Architecture\",\"authors\":\"Daisuke Hashimoto, Akira Tanaka, Masanori Yokoyama\",\"doi\":\"10.1109/EDOCW.2007.10\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Like RM-ODP [1], enterprise architecture (or EA for short) has its own perspectives as a basic construct for its architecture definition to represent areas of concern. In this paper, difference between RM-ODP and one concrete example EA, and applicability of Use of UML for ODP system specifications [2] (or UML4ODP in short) standard to the example EA, are discussed. Several additional diagrams that exist in EA guideline book in Japan [4] but not in UML4ODP are suggested as complementary additions to existing diagrams. The work is based on the UML4JEA Profile [5][6] developed by Interoperability Technology Association for Information Processing, Japan.\",\"PeriodicalId\":181454,\"journal\":{\"name\":\"2007 Eleventh International IEEE EDOC Conference Workshop\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2007-10-15\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"7\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2007 Eleventh International IEEE EDOC Conference Workshop\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/EDOCW.2007.10\",\"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 Eleventh International IEEE EDOC Conference Workshop","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/EDOCW.2007.10","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 7
摘要
与RM-ODP[1]一样，企业架构(简称EA)有自己的透视图作为其架构定义的基本构造，以表示关注的领域。本文讨论了RM-ODP与一个具体示例EA的区别，以及使用UML for ODP系统规范[2](简称UML4ODP)标准对该示例EA的适用性。在日本[4]中存在的EA指南书中，但在UML4ODP中没有的几个附加图被建议作为对现有图的补充。该工作基于日本信息处理互操作性技术协会开发的UML4JEA概要文件b[5][6]。
Like RM-ODP [1], enterprise architecture (or EA for short) has its own perspectives as a basic construct for its architecture definition to represent areas of concern. In this paper, difference between RM-ODP and one concrete example EA, and applicability of Use of UML for ODP system specifications [2] (or UML4ODP in short) standard to the example EA, are discussed. Several additional diagrams that exist in EA guideline book in Japan [4] but not in UML4ODP are suggested as complementary additions to existing diagrams. The work is based on the UML4JEA Profile [5][6] developed by Interoperability Technology Association for Information Processing, Japan.
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
