Enterprise Architecture and Cartography: From Practice to Theory; From Representation to Design

Foreword
	Warning
	About This Book
	In Conclusion
Contents
Acronyms
Part I Motivation: Why We Wrote This Book
	1 Introduction
		1.1 Enterprise Architecture: Expectations and Disappointments
		1.2 Enterprise Design and Representation
		1.3 Enterprise Cartography
			1.3.1 Approaches to Enterprise Cartography
		1.4 Book Structure and Contributions
			1.4.1 Book Contributions
			1.4.2 Book Structure
		1.5 Exercises
		References
Part II Theory: The Theories Behind
	2 Founding Concepts
		2.1 Systems and Enterprises
			2.1.1 Systems
			2.1.2 Enterprises
		2.2 Architecture and Enterprise Architecture
		2.3 Design and Representation
		2.4 Architecture Views and Viewpoints
		References
	3 Enterprise Architecture
		3.1 Introduction
		3.2 Enterprise Architecture Domains and Frameworks
			3.2.1 The Zachman Framework
			3.2.2 The Open Group Architecture Framework
			3.2.3 ArchiMate
			3.2.4 Commonly used Architecture Layers
		3.3 The Architecture of the Enterprise
			3.3.1 Strategy Architecture Layer
				3.3.1.1 Top Layers of the Enterprise Architecture
				3.3.1.2 Business Motivation Concepts
				3.3.1.3 Motivation Modeling
			3.3.2 Business Architecture Layer
				3.3.2.1 System Context
				3.3.2.2 Business Process
				3.3.2.3 Business Layer Concepts
			3.3.3 Information Architecture Layer
				3.3.3.1 Concepts
				3.3.3.2 Information Classification
				3.3.3.3 IA Modeling
			3.3.4 Information Systems Architecture Layer
				3.3.4.1 Concepts
			3.3.5 Technology Architecture Layer
				3.3.5.1 Concepts
			3.3.6 Service Architecture Layer
				3.3.6.1 Concepts
		3.4 Exercises
		References
	4 Enterprise Architecture Patterns and Principles
		4.1 Introduction
			4.1.1 Principles Description
			4.1.2 Principles Summary
		4.2 Cross-Layer Principles
			4.2.1 Components Are Centralized
			4.2.2 Front-Office Processes Are Separated from Back-Office Processes
			4.2.3 Channel-Specific Is Separated from Channel-Independent
			4.2.4 Data Is Provided by the Source
			4.2.5 Data Is Maintained in the Source Application
			4.2.6 Data Is Captured Once
			4.2.7 Systems Communicate Through Services
			4.2.8 Business and Information Architectures Are Aligned
			4.2.9 Business and Application Architectures Are Aligned
			4.2.10 Information and Application Architectures Are Aligned
			4.2.11 Required Application Services Are Available
			4.2.12 Services Have Different Interfaces
			4.2.13 Applications Manage Information with the Same Security Level
			4.2.14 Critical Process Are Executed in Specific Systems
			4.2.15 Each Information Entity Is Managed by a Single Application
			4.2.16 Primitive and Derived Data Are Managed by Different IT Components
		4.3 Business Layer Principles
			4.3.1 Business Units Are Autonomous
			4.3.2 Customers Have a Single Point of Contact
			4.3.3 Management Layers Are Minimized
		4.4 Information Layer Principles
			4.4.1 Information Management Is Everybody's Business
			4.4.2 Common Vocabulary and Data Definitions
			4.4.3 Content and Presentation Are Separated
			4.4.4 Data That Is Exchanged Adhere to a Canonical Data Model
			4.4.5 The Number of Implementations of the Same Information Entity Is Minimized
		4.5 Applications Layer Principles
			4.5.1 Common Use Applications
			4.5.2 Presentation Logic, Process Logic, and Business Logic Are Separated
			4.5.3 Business Logic and Presentation Components Do Not Keep the State
			4.5.4 Minimize the Number of Dependencies and Applications per Service
		4.6 Infrastructure Layer Principles
			4.6.1 Technology Independence
			4.6.2 Interoperability
			4.6.3 IT Systems Are Scalable
			4.6.4 IT Systems Adhere to Open Standards
			4.6.5 IT Systems Are Preferably Open Source
			4.6.6 All Messages Are Exchanged Through the Enterprise Service Bus
			4.6.7 Software Components Are Multi-platform
		4.7 IT Architecture Patterns and Practices
			4.7.1 IT Architecture Layers Patterns
				4.7.1.1 Two-Layer Versus Three-Layer Architectures
			4.7.2 Architectures for High Availability
		4.8 IT Integration Patterns
			4.8.1 Introduction
			4.8.2 File Transfer
			4.8.3 Screen Scraping
				4.8.3.1 Web Scraping or Web Harvesting
			4.8.4 Remote Procedure Call
			4.8.5 Message Queues
			4.8.6 Message-Oriented Middleware
			4.8.7 Data-Oriented Integration
				4.8.7.1 Integration via DBMS
			4.8.8 Application Interface-Oriented Integration
			4.8.9 Transactions and Transaction Monitors
			4.8.10 Business Process-Oriented Integration
				4.8.10.1 Workflow-Oriented Integration
				4.8.10.2 Business Process Execution Language
				4.8.10.3 Orchestration vs Choreography
		4.9 Exercises
		References
	5 Enterprise Cartography
		5.1 Introduction
		5.2 Definitions
			5.2.1 Enterprise Model
			5.2.2 Enterprise Meta-Model
			5.2.3 Architectural Sentence
			5.2.4 Productive Artefacts
			5.2.5 Transformation Initiative
			5.2.6 Enterprise States
			5.2.7 Enterprise Observation
			5.2.8 Enterprise System
			5.2.9 Enterprise Roles
			5.2.10 Enterprise System Representations
		5.3 Enterprise Cartography Principles
			5.3.1 Principle 1: Transformation Initiatives Are Observable Artifacts of the Enterprise AS-IS
			5.3.2 Principle 2: Changes in the Set of Productive Artifacts Are Planned Ones
			5.3.3 Principle 3: All Enterprise Artifacts Have a Five-State Life Cycle: Conceived, Gestating, Alive, Retired, and Removed
			5.3.4 Principle 4: The Emerging AS-IS Can Be Inferred by Observing the Enterprise AS-IS
		References
Part III How We Do It: Supporting Methodologies and Technologies
	6 Enterprise Architecture Development Framework
		6.1 Introduction
		6.2 TOGAF ADM
			6.2.1 Preliminary Phase
			6.2.2 Phase A: Architecture Vision
			6.2.3 Phase B: Business Architecture
			6.2.4 Phase C: Information Systems Architecture
			6.2.5 Phase D: Technology Architecture
			6.2.6 Phase E: Opportunities and Solutions
			6.2.7 Phase F: Migration Planning
			6.2.8 Phase G: Implementation Governance
			6.2.9 Phase H: Architecture Change Management
			6.2.10 ADM Architecture Requirement Management
			6.2.11 Implementing the ADM
		References
	7 Enterprise Strategy Design
		7.1 Introduction
		7.2 Context Identification
			7.2.1 PESTEL
			7.2.2 External Stakeholders and Drivers
		7.3 Desired Result Definition
			7.3.1 Balanced Scorecard
			7.3.2 Vision and Goals
		7.4 Courses of Action and Requirement Definition
			7.4.1 Business Model Canvas
			7.4.2 Mission, Strategies, Tactics, Business Policies, Business Rules, Requirements, and Constraints
		7.5 Assessment Definition
			7.5.1 SWOT
			7.5.2 Assessments and Outcomes
		7.6 Enterprise Strategy Design Overview
		7.7 Exercises
		References
	8 Business Process Design
		8.1 Business Process Design Overview
			8.1.1 Process Identification
			8.1.2 Activity Identification
			8.1.3 Activity Classification
		8.2 A Methodology for Business Process Design
			8.2.1 Foundations for Business Process Design Methodology
				8.2.1.1 The SemantifyingBPMN Tool
			8.2.2 Business Process Elicitation
			8.2.3 Business Process Discovery
			8.2.4 Business Process Enrichment
			8.2.5 Extending to Business Process Prototyping
		8.3 Exercises
		References
	9 Information Architecture Design
		9.1 Approaches for Information Architecture Design
		9.2  Design Primitives
			9.2.1  Top-Down Design Primitives
			9.2.2 Bottom-Up Design Primitives
		9.3 Design Approaches
			9.3.1  Top-Down Design Approach
			9.3.2  Bottom-Up Design Approach
			9.3.3  Discussion
		9.4 Exercises
		Reference
	10 Information Systems Architecture Design
		10.1 Information Systems Architecture Planning
			10.1.1 Information Systems Architecture Alignment
				10.1.1.1 Alignment Between Business and Applications
				10.1.1.2 Alignment Between Business and Information
				10.1.1.3 Alignment Between Information and Applications
			10.1.2 Information Systems Architecture Design
				10.1.2.1 Rules for Designing the ISA
			10.1.3 Information Systems Architecture Project Approach
				10.1.3.1 Level 1: Getting Started
				10.1.3.2 Level 2: Where We Are Today
				10.1.3.3 Level 3: The Vision of Where We Want to Be
				10.1.3.4 Level 4: How We Plan to Get There
		10.2 Application Portfolio Management
			10.2.1 APM Analysis
			10.2.2 APM Indicators
				10.2.2.1 Business Relevance
				10.2.2.2 Technical Quality
			10.2.3 APM Actions
			10.2.4 APM Project Approach
		10.3 Service Architecture Design
		10.4 Exercises
		References
	11 A Method for Enterprise Cartography
		11.1 Phases of the EC Approach
			11.1.1 Phase 1: Identify Key Questions
			11.1.2 Phase 2: Concept Clarification
			11.1.3 Phase 3: Identify the Best Sources of Information
			11.1.4 Phase 4: Structure the Processes and Tools to Capture Information
			11.1.5 Phase 5: Define and Configure the Architectural Views
			11.1.6 Phase 6: Populate the KB with an Initial Baseline
				11.1.6.1 Incremental Loading of the KB
				11.1.6.2 Naming Enterprise Artifacts
		11.2 A Method for Concept Clarification
			11.2.1 Identification of Relevant Properties
			11.2.2 Identification of Relevant Perspectives
			11.2.3 Concept Representation
			11.2.4 An Example: Clarifying the Application Concept
				11.2.4.1 Concepts at Business Layer
				11.2.4.2 Concepts at Information System Layer
				11.2.4.3 Concepts at the Infrastructure Layer
		11.3 Exercises
		References
Part IV Practice: Sample Projects
	12 Enterprise Architecture Case Projects
		12.1 Case 1: Lisbon Smart City Enterprise Architecture
			12.1.1 Introduction
			12.1.2 Strategy
			12.1.3 Organization
			12.1.4 Business Processes
			12.1.5 Information
			12.1.6 Current Applications
				12.1.6.1 Relationship Management with the Citizen
				12.1.6.2 Human Resource Management
				12.1.6.3 Urban Cleaning Management
				12.1.6.4 Fleet Management
				12.1.6.5 Equipment, Uniforms, and Consumables Management
				12.1.6.6 Other Applications
				12.1.6.7 Transverse Support Applications
			12.1.7 Current Infrastructure
				12.1.7.1 Technological Infrastructure
				12.1.7.2 Support Artifacts
			12.1.8 Project Goals
		12.2 Case 2: Instituto Superior Técnico Enterprise Architecture
			12.2.1 Introduction
			12.2.2 Location
			12.2.3 Organization
			12.2.4 Strategy
			12.2.5 Business Process and Information
			12.2.6 EA Guidelines
			12.2.7 Project Goals
		12.3 Case 3: Public Procurement Enterprise Architecture
			12.3.1 Introduction
				12.3.1.1 AS-IS
				12.3.1.2 Motivation
				12.3.1.3 Business Components
				12.3.1.4 Information Architecture
				12.3.1.5  Information System Components
				12.3.1.6 Technological Components
			12.3.2 Public Procurement Interoperability Initiative (TO-BE)
			12.3.3 The Project to Be Done
		References