Los puntos clave no están disponibles para este artículo en este momento.
There is a lot of pressures from organizations to continually redesign the business processes and the technology infrastructure to support the organization, but to also help organizations manage competing stakeholder needs, changing objectives and behaviour, and so on. A key part of this is making sure that all their activities in the different components of the business are interconnected and that they are moving in the same direction. Enterprise Architecture (EA) is an effective way of dealing with the challenge of designing business activities and supporting IT. This paper will summarize the organization of EA and look more closely at some major components of EA: governance architecture, business architecture, information architecture and technical architecture and consider the overlap and constructive interaction involved. Enterprise Architecture can be best understood through business process redesign. So, it is useful to briefly review the leading frameworks for business process redesign, including COBIT from ISACA, LEAN from the Toyota Group, TOGAF from the Object-Management Group, and the Capgemini Integrated Architecture Framework (IAF). All these frameworks allow us to more successful transformation, to return to the central idea of this paper.
Tobi Towoju (Wed,) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: