Case study on RM-ODP and Enterprise Architecture

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.