Collaborative Method to Develop an Enterprise Architecture in a Public Institution

The growth of organizational complexity degrades business processes efficiency. Enterprise Architecture (EA) is an instrument to manage organizational complexity, through the improvement of organizational self-awareness. EA improves alignment between business and IT to ensure the business value of IT, and enables rationalization of organizational resources. However, depending of organizational culture and characteristics, there are several issues hindering the EA development within an organization. Actual frameworks, like TOGAF, require a significant number of skilled human resources (HR), which some organizations, like public institutions, cannot assign to EA activities. Our research goal is to provide an EA capability to public institutions, enabling these institutions to take advantage of EA benefits. Public institution contexts and stakeholder concerns were explored as well as issues acting as enablers or as inhibitors for an EA development. We propose a collaborative method to develop an EA, applying lean and agile principles, focusing on public institution specificities. Our collaborative method tries to capture organizational knowledge, spread among employees, into an EA model, to map the enterprise cartography of the institution. Our method has been demonstrated and evaluated in the IT sector of the Portuguese Navy.info:eu-repo/semantics/draf

Inter-organizational fault management: Functional and organizational core aspects of management architectures

Outsourcing -- successful, and sometimes painful -- has become one of the hottest topics in IT service management discussions over the past decade. IT services are outsourced to external service provider in order to reduce the effort required for and overhead of delivering these services within the own organization. More recently also IT services providers themselves started to either outsource service parts or to deliver those services in a non-hierarchical cooperation with other providers. Splitting a service into several service parts is a non-trivial task as they have to be implemented, operated, and maintained by different providers. One key aspect of such inter-organizational cooperation is fault management, because it is crucial to locate and solve problems, which reduce the quality of service, quickly and reliably. In this article we present the results of a thorough use case based requirements analysis for an architecture for inter-organizational fault management (ioFMA). Furthermore, a concept of the organizational respective functional model of the ioFMA is given.Comment: International Journal of Computer Networks & Communications (IJCNC