The term of Enterprise Architecture (EA) has been used for many years within the information system engineering community. There are two basic challenges facing the enterprise engineering process: enterprise modelling and integration. Modelling involves system analysis of enterprise architectures that define strategic, organisational and technical system views. Many companies have been building information systems for many years, but just few of them have actually understood interdependencies between various architecture types. Even such de facto software industry standard as UML has many inherent weaknesses as far as semantic integrity of various diagrams is concerned. To obtain value from various documents on EA, they must be integrated. Since complexity of diagrams is high, the developers usually rely on a common repository of enterprise engineering tools. The problem is that existence of a common repository does not guarantee consistency and integrity of various enterprise representations. Traditional methods of information system analysis and design are not putting into foreground some important interdependencies that are crucial to glue the organisational and technical system descriptions. Such tradition tends to draw attention away from the semantic modelling aspects and concentrates on the implementation dependent issues. In this paper, we are using a component-oriented way for defining EA. We will demonstrate not only the benefits of component orientation, but also how UML can be empowered by the enterprise modelling.
展开▼
