To provide structure and transparency to the complex world of IT, Enterprise Architecture was created. However, we created complexities within Enterprise Architecture with Frameworks that are not easily understandable and purposefully implementable. In this book, Nagesh and Gerry help to turnaround Enterprise Architecture organizations. They introduce a simple IDEA Framework that is based on common practices and investments within IT organizations. The Ten deliverables presented in this book bring structure and clarity to IT organizations that are 10-people IT shops and 1000+ IT staff enterprises alike. This book is not an ivory tower work, it is actionable, applied Enterprise Architecture. It is also a healthy dose of EA tough love. If you want to know why EA fails, read the second chapter. It is introspective, it does not blame external forces: the not-my-fault syndrome. It also does not blame, in fact it hardly mentions, technology. To be fair, the Nagesh and Gerry do recognize external influences; however they are viewed as risks that must be managed. Most corporations focus on this years budget, investments, and rewards. The same focus rolls downhill to the Information Technology department. If the IT department has not successfully communicated the budget and managed to spend it within the limits (10% variance), everything else may seem irrelevant. Eventually, Nagesh and Gerry started looking through current IT systems and IT assets to understand: (a) where the current funds were being invested, (b) how these investments jelled or were mandated because of the previous investments that had been made by IT, and (c) how the companys business priorities aligned with future technology needs, including the need to meet compliance requirements. Considering and discovering the answers to these three questions led Nagesh and Gerry to develop a definition of Enterprise Architecture that was based on technology investments Investment Driven Enterprise Architecture (IDEA) Framework. The purpose of the IDEA Framework is to provide guidance on how the corporations future technology will be drafted and communicated. Its method is to utilize actual systems, hardware, people, and business functions in order to establish boundaries within which the IDEA Framework will work. The structure of the IDEA Framework differs from that of many others because it consists of key deliverables that fit into day-to-day activities and it accommodates an enterprise-wide strategic plan. It also provides for the much-needed interaction between these key deliverables and facilitates contributions from key stakeholders across Business Units and the various IT departments. In essence, the IDEA Framework takes the key deliverables, stakeholders, and organizations and demonstrates how they dynamically function together.

To provide structure and transparency to the complex world of IT, Enterprise Architecture was created. However, we created complexities within Enterprise Architecture with Frameworks that are not easily understandable and purposefully implementable. In this book, Nagesh and Gerry help to turnaround Enterprise Architecture organizations. They introduce a simple IDEA Framework that is based on common practices and investments within IT organizations. The Ten deliverables presented in this book bring structure and clarity to IT organizations that are 10-people IT shops and 1000+ IT staff enterprises alike. This book is not an ivory tower work, it is actionable, applied Enterprise Architecture. It is also a healthy dose of EA "tough love." If you want to know why EA fails, read the second chapter. It is introspective, it does not blame external forces: the not-my-fault syndrome. It also does not blame, in fact it hardly mentions, technology. To be fair, the Nagesh and Gerry do recognize external influences; however they are viewed as risks that must be managed. Most corporations focus on this year's budget, investments, and rewards. The same focus rolls downhill to the Information Technology department. If the IT department has not successfully communicated the budget and managed to spend it within the limits (±10% variance), everything else may seem irrelevant. Eventually, Nagesh and Gerry started looking through current IT systems and IT assets to understand: (a) where the current funds were being invested, (b) how these investments jelled or were mandated because of the previous investments that had been made by IT, and (c) how the company's business priorities aligned with future technology needs, including the need to meet compliance requirements. Considering and discovering the answers to these three questions led Nagesh and Gerry to develop a definition of Enterprise Architecture that was based on technology investments - Investment Driven Enterprise Architecture (IDEA) Framework. The purpose of the IDEA Framework is to provide guidance on how the corporation's future technology will be drafted and communicated. Its method is to utilize actual systems, hardware, people, and business functions in order to establish boundaries within which the IDEA Framework will work. The structure of the IDEA Framework differs from that of many others because it consists of key deliverables that fit into day-to-day activities and it accommodates an enterprise-wide strategic plan. It also provides for the much-needed interaction between these key deliverables and facilitates contributions from key stakeholders across Business Units and the various IT departments. In essence, the IDEA Framework takes the key deliverables, stakeholders, and organizations and demonstrates how they dynamically function together.

Organizational complexity is an unavoidable aspect of all businesses, even larger ones, which can hinder their ability to react to sudden or disruptive change. However, with the implementation of enterprise architecture (EA), businesses are able to provide their leaders with the resources needed to address any arising challenges. A Systemic Perspective to Managing Complexity with Enterprise Architecture highlights the current advances in utilizing enterprise architecture for managing organizational complexity. By demonstrating the value and usefulness of EA, this book serves as a reference for business leaders, managers, engineers, enterprise architects, and many others interested in new research and approaches to business complexity.

"This book provides a detailed analysis of the important strategies for integrating IT systems into fields such as e-business and customer-relationship management. It supplies readers with a comprehensive survey of existing enterprise architecture and integration approaches, and presents case studies that illustrate best practices, describing innovative methods, tools, and architectures with which organizations can systematically achieve enterprise integration"--Provided by publisher.

This book provides practical advice on how to develop an enterprise architecture practice. The authors developed different tools and models to support organizations in implementing and professionalizing an enterprise architecture function. Coverage applies these tools and models to a number of different organizations and, as a result, will help readers avoid potential pitfalls and achieve success with enterprise architecture.

This book takes the position that organizations, such as businesses and government agencies, form a special class of living system. As such, they come into being, live through lifecycle stages, and can experience organizational health and various forms of organizational illness along the way. If the latter is frequent or extended, such organizations often die an untimely death. A services perspective can go a long way to combat this outcome and assist in maintaining organizational health. Allowing this perspective to permeate, an organization induces a consideration of its genuine value and leads to a greater understanding of the breadth of stakeholders who are the beneficiaries of it.

Effective administration of government and governmental organizations is a crucial part of achieving success in those organizations. To develop and implement best practices, policymakers and leaders must first understand the fundamental tenants and recent advances in public administration. Public Affairs and Administration: Concepts, Methodologies, Tools, and Applications explores the concept of governmental management, public policy, and politics at all levels of organizational governance. With chapters on topics ranging from privacy and surveillance to the impact of new media on political participation, this multi-volume reference work is an important resource for policymakers, government officials, and academicians and students of political science.

The overall functions of a government impact a wide range of sectors in society. It is imperative for governments to work at full capacity and potential in order to ensure quality progress for its citizens. Driving Efficiency in Local Government Using a Collaborative Enterprise Architecture Framework: Emerging Research and Opportunities is an essential scholarly publication for the latest research on methods for smart government initiatives and implementations, and addresses prevalent internal and external security risks. Featuring extensive coverage on a broad range of topics such as technology funds, mobile technology, and cloud computing, this book is ideally designed for professionals, academicians, researchers, and students seeking current research on the ways in which governments can advance and prosper.

"This book addresses the gap in current literature in terms of linking and understanding the relationship between e-government and government enterprise architecture"--Provided by publisher.

An Introduction to Enterprise Architecture is the culmination of several decades of experience that I have gained through work initially as an information technology manager and then as a consultant to executives in the public and private sectors. I wrote this book for three major reasons: (1) to help move business and technology planning from a systems and process-level view to a more strategy-driven enterprise-level view, (2) to promote and explain the emerging profession of EA, and (3) to provide the first textbook on the subject of EA, which is suitable for graduate and undergraduate levels of study. To date, other books on EA have been practitioner books not specifically oriented toward a student who may be learning the subject with little to no previous exposure. Therefore, this book contains references to related academic research and industry best practices, as well as my own observations about potential future practices and the direction of this emerging profession.