"This book is a compilation of chapters on government Enterprise architecture with the intention of informing professionals with different levels of enterprise architecture knowledge"--Provided by publisher
Part 11: Innovation and Collaborative Networks ; International audience ; Enterprises are looking for improvements in their processes, products and services, causing them to become more complex mainly due to the amount of information and requirements involved. At same time, governments and costumers are more conscious about Sustainable Development requirements. Enterprise Architectures supports the analysis, simulation, automated systems projects, distribution of responsibilities and authorities, aimed at reengineering or improvement of companies processes. However, they do not seem to contemplate the requirements related to Sustainable Development in a systemic and integrated way. This paper discusses the derivation and incorporation of Sustainable Development requirements into Enterprise Architecture Frameworks (EAF). Then, this works presents some initial guidelines to extend components of GERAM with ISO standards and frameworks related to sustainability.
Testimony issued by the General Accounting Office with an abstract that begins "The concept of enterprise architecture emerged in the mid- 1980s as a means for optimizing integration and interoperability across organizations. In the early 1990s, GAO research of successful public and private sector organizations led it to identify enterprise architecture as a critical success factor for agencies that are attempting to modernize their information technology (IT) environments. Since then, GAO has repeatedly identified the lack of an enterprise architecture as a key management weakness in major modernization programs at a number of federal agencies. It has also collaborated with the Office of Management and Budget (OMB) and the federal Chief Information Officers (CIO) Council to develop architecture guidance. In 2002, OMB began developing the Federal Enterprise Architecture (FEA), an initiative intended to guide and constrain federal agencies' enterprise architectures and IT investments. GAO was asked to testify on the status of the FEA and on the state of federal agencies' development and use of enterprise architectures."
Enterprises are looking for improvements in their processes, products and services, causing them to become more complex mainly due to the amount of information and requirements involved. At same time, governments and costumers are more conscious about Sustainable Development requirements. Enterprise Architectures supports the analysis, simulation, automated systems projects, distribution of responsibilities and authorities, aimed at reengineering or improvement of companies processes. However, they do not seem to contemplate the requirements related to Sustainable Development in a systemic and integrated way. This paper discusses the derivation and incorporation of Sustainable Development requirements into Enterprise Architecture Frameworks (EAF). Then, this works presents some initial guidelines to extend components of GERAM with ISO standards and frameworks related to sustainability.
In: International journal of enterprise information systems: IJEIS ; an official publication of the Information Resources Management Association, Band 13, Heft 2, S. 50-62
The current enterprise architecture (EA) theory originates from the Business Systems Planning (BSP) methodology initiated by IBM in the 1960s and describes EA as a comprehensive blueprint of an enterprise organized according to a certain framework and describing the current state, the desired future state and the roadmap for transition between them. However, in this paper I demonstrate that the current EA theory poses more questions than answers and is, arguably, in an unsatisfactory state. This paper highlights the critical questions in EA research and is intended to spark further conversation in the EA research community. All the formulated questions address the fundamental aspects of the current EA theory that are critically important for the whole EA discipline. Although this paper does not propose any answers to these questions, it makes a non-theoretical contribution to the EA discipline by critically evaluating the current EA theory, provoking new thoughts and stimulating further research that will substantially alter the EA discipline in the future.
Converging Core and Contextual Requirements -- Interoperability -- Enterprise Applications Integration Basics -- Integration Technologies -- Distributed Systems -- SOA Basics -- SOA Technologies -- Portability -- Cloud Basics -- Cloud Technologies -- Reliability -- Big Data Basics -- Big Data Technologies -- Ubiquity -- Ubiquitous Computing Basics -- Embedded Systems Basics -- Internet of Things Technologies -- Cyber-Physical Systems.