Enterprise Architecture - Revision history

User at 19:56, 23 August 2023

2023-08-23T19:56:48Z

User at 19:12, 2 May 2023

2023-05-02T19:12:42Z

User at 23:31, 18 January 2023

2023-01-18T23:31:51Z

User at 22:24, 18 January 2023

2023-01-18T22:24:15Z

User at 15:50, 23 November 2022

2022-11-23T15:50:24Z

Show changes

User at 18:54, 21 November 2022

2022-11-21T18:54:30Z

User at 14:06, 21 November 2022

2022-11-21T14:06:12Z

User at 14:05, 21 November 2022

2022-11-21T14:05:04Z

Show changes

User at 19:43, 16 November 2022

2022-11-16T19:43:39Z

User at 17:43, 16 September 2022

2022-09-16T17:43:17Z

@@ Line 184: / Line 184: @@
 == See Also ==
-*[[Enterprise Architecture Life Cycle (EALC)]]
+#[[Enterprise Architecture Life Cycle (EALC)]]
-*[[Enterprise Architecture Governance]]
+#[[Enterprise Architecture Governance]]
-*[[Enterprise Architecture Management (EAM)]]
+#[[Enterprise Architecture Management (EAM)]]
-*[[IT Capability]]
+#[[IT Capability]]
-*[[IT Transformation]]
+#[[IT Transformation]]
+#[[The Open Group Architecture Framework (TOGAF)]]

← Older revision		Revision as of 19:12, 2 May 2023
Line 169:		Line 169:
	*Mature EA Team: The EA team which don't just believe in Framework and Technology but also has the capability to carry the business with them and got a thick skin to sail through the politics and policies Staff. Also, it is not about the "chief architect," it is about the team of architects/support staff, a mature EA team.		*Mature EA Team: The EA team which don't just believe in Framework and Technology but also has the capability to carry the business with them and got a thick skin to sail through the politics and policies Staff. Also, it is not about the "chief architect," it is about the team of architects/support staff, a mature EA team.
	*EA Skills/Talent: Architecture is more of an art than a science and requires more skills than certifications. Enterprise Architect requires a broad knowledge of many aspects of, business domain knowledge, technologies project management experience, and organizational skills. There are many channels to mature as an Enterprise Architect. Enterprise Architects with different maturing paths may see the same organization with very different challenges.		*EA Skills/Talent: Architecture is more of an art than a science and requires more skills than certifications. Enterprise Architect requires a broad knowledge of many aspects of, business domain knowledge, technologies project management experience, and organizational skills. There are many channels to mature as an Enterprise Architect. Enterprise Architects with different maturing paths may see the same organization with very different challenges.
		+
		+	== 10 Important Factors to Consider When Developing Your Enterprise Architecture ==
		+	#Developing a comprehensive enterprise architecture ensures technology investments support business goals and objectives.
		+	#Documenting the current state of enterprise architecture is an important first step in identifying areas for improvement.
		+	#Establishing a clear vision for enterprise architecture can help to align technology with business strategy and drive innovation.
		+	#Maintaining a well-documented and up-to-date enterprise architecture is essential to effective decision-making and risk management.
		+	#Implementing enterprise architecture best practices can help organizations to optimize their technology investments and increase ROI.
		+	#Collaborating with organizational stakeholders is essential to developing a comprehensive and effective enterprise architecture.
		+	#Regularly reviewing and updating enterprise architecture is important to ensure it remains aligned with changing business needs and technology trends.
		+	#Adopting an agile approach to enterprise architecture can help organizations to respond more quickly to changing market conditions and customer needs.
		+	#Leveraging technology tools and platforms can support the development and maintenance of enterprise architecture and improve visibility and transparency.
		+	#Incorporating security and compliance considerations into enterprise architecture can help organizations to minimize risk and protect sensitive data.

@@ Line 172: / Line 172: @@
 == See Also ==
 *[[Enterprise Architecture Governance]]
 *[[Enterprise Architecture Management (EAM)]]

@@ Line 14: / Line 14: @@
 == Key Aspects of Enterprise Architecture Definition<ref>[https://cioindex.com/references/enterprise-architecture/ Key Aspects of Enterprise Architecture Definition as proposed by Sourabh Hajela]</ref> ==
-[https://cioindex.com/profile/shajela/ Sourabh Hajela] of CIO Index defines Enterprise architecture as a holistic, hierarchical, and abstract description of the essential elements of an organization to maximize shareholder value over time. Enterprise Architecture transforms an [[IT Strategy (Information Technology Strategy)|IT Strategy]] into tangible IT Solutions. [[IT Governance]] directs Enterprise Architecture Planning.
+[https://cioindex.com/profile/shajela/ Sourabh Hajela] of CIO Index defines Enterprise architecture as a holistic, hierarchical, and abstract description of the essential elements of an organization to maximize shareholder value over time. Enterprise Architecture transforms an IT Strategy into tangible IT Solutions. IT Governance directs Enterprise Architecture Planning.
 The key aspects in this definition of enterprise architecture: (If an enterprise architecture delivers on these points it would've met its obligation and become a tool for creating and communicating the value in an organization. The process that builds it is called enterprise architecture planning and that includes its use in IT Governance and its own governance.)
@@ Line 133: / Line 133: @@
 *Federal Enterprise Architecture Framework (FEA): The Federal Enterprise Architecture Framework was developed and published by the US Federal Chief Information Officers (CIO) Council. The government was following the industry trend of defining architectural frameworks to guide the development of large, complex systems development. FEAF was in response to the Clinger-Cohen Act 1996, which required Federal Agency CIOs to develop, maintain, and facilitate integrated systems architectures. The overriding goal of FEAF is to organize and promote sharing of Federal information for the entire Federal Government. The architectural segments are developed individually, within structured guidelines, with each segment considered to be its own enterprise within the Federal Enterprise. FEA allows for flexibility in the use of methods, work products, and tools to be used by individual federal agencies.
 *Treasury Enterprise Architecture Framework (TEAF): The Department of the Treasury published the Treasury Enterprise Architecture Framework (TEAF) in July 2000. The Department of the Treasury is comprised of a number of offices that function as individual enterprises. Therefore, its enterprise architecture needs to map the interrelationships among the organizations in order to manage IT resources. The TEAF aims at facilitating “integration, information sharing, and exploitation of common requirements across the department”. Similar to DoDAF, TEAF includes descriptions of work products for documenting and modeling enterprise architectures. TEAF also explicitly states that these work products align with FEAF models and DoDAF products.
-*The Open Group Architecture Framework (TOGAF): The Open Group Architectural Framework (TOGAF) was first developed in 1995 and was based on the Department of Defense’s Technical Architecture Framework for Information Management. TOGAF focuses on mission-critical business applications that use open systems building blocks. “A key element of TOGAF is [[Architecture Development Method (ADM)]] that specifies a process for developing enterprise architecture”. TOGAF explains rules for developing good principles, rather than providing a set of architectural principles. The three levels of principles support decision-making across the entire enterprise; provide guidance on IT resources; and support architecture principles for development and implementation.
+*The Open Group Architecture Framework (TOGAF): The Open Group Architectural Framework (TOGAF) was first developed in 1995 and was based on the Department of Defense’s Technical Architecture Framework for Information Management. TOGAF focuses on mission-critical business applications that use open systems building blocks. “A key element of TOGAF is Architecture Development Method (ADM) that specifies a process for developing enterprise architecture”. TOGAF explains rules for developing good principles, rather than providing a set of architectural principles. The three levels of principles support decision-making across the entire enterprise; provide guidance on IT resources; and support architecture principles for development and implementation.
@@ Line 172: / Line 172: @@
 == See Also ==
 *[[Enterprise Architecture Management (EAM)]]
 *[[IT Capability]]
 *[[IT Transformation]]
-*[[Enterprise Architecture Governance]]

@@ Line 150: / Line 150: @@
 *Organizational design - Enterprise architecture provides support in the areas related to the design and re-design of organizational structures during mergers, acquisitions, or general organizational change.
 *Organizational processes and process standards - Enterprise architecture helps enforce discipline and standardization of business processes, and enables process consolidation, reuse, and integration.
-*[[Project Portfolio Management (PPM)]] - Enterprise architecture supports investment decision-making and work prioritization.
+*Project Portfolio Management (PPM) - Enterprise architecture supports investment decision-making and work prioritization.
-*[[Project Management]] - Enterprise architecture enhances the collaboration and communication between project stakeholders. Enterprise architecture contributes to efficient project scoping, and to defining more complete and consistent project deliverables.
+*Project Management - Enterprise architecture enhances the collaboration and communication between project stakeholders. Enterprise architecture contributes to efficient project scoping, and to defining more complete and consistent project deliverables.
 *Requirements Engineering - Enterprise architecture increases the speed of requirement elicitation and the accuracy of requirement definitions, through the publishing of the enterprise architecture documentation.
 *System development - Enterprise architecture contributes to optimal system designs and efficient resource allocation during system development and testing.
-*[[IT Management (Information Technology Management)|IT management]] and decision making - Enterprise architecture is found to help enforce discipline and standardization of IT planning activities and to contribute to a reduction in time for technology-related decision-making.
+*IT management and decision making - Enterprise architecture is found to help enforce discipline and standardization of IT planning activities and to contribute to a reduction in time for technology-related decision-making.
-*[[IT Value]] - Enterprise architecture helps reduce the system's implementation and operational costs, and minimizes replication of IT infrastructure services across business units.
+*IT Value - Enterprise architecture helps reduce the system's implementation and operational costs, and minimizes replication of IT infrastructure services across business units.
 *IT complexity - Enterprise architecture contributes to a reduction in IT complexity, consolidation of data and applications, and to better interoperability of the systems.
 *IT openness - Enterprise architecture contributes to more open and responsive IT as reflected through increased accessibility of data for regulatory compliance, and increased transparency of infrastructure changes.
-*[[Risk Management|IT risk management]] - Enterprise architecture contributes to the reduction of business risks from system failures and security breaches. Enterprise architecture helps reduce risks of project delivery.
+*IT risk management - Enterprise architecture contributes to the reduction of business risks from system failures and security breaches. Enterprise architecture helps reduce risks of project delivery.
@@ Line 166: / Line 166: @@
 *Understand Stewardship and Ownership differences. Too often an EA attempts to take ownership of a business process and ends up getting blamed. An Enterprise Architect is a steward to practice strategic EA Leadership & Operational Stewardship --> alignment of execution with Strategy is extremely critical for EA success.
 *EA Maturity: EA engagement model and governance. This gears toward corporate processes, politics, and people issues. Enterprise Architecture is simply a heavy burden to a lot of people and projects if the EA engagement and governance model is not efficient and effective. Somehow, a fragmented EA engagement model and governance process are very common in the workplace. It seems to take forever to streamline. In other words, Governance and Compliance inward are extremely important.
-*Organizational Maturity. A mature organization is a base to start a successful EA program. On the other hand, an effective EA program improves organizational maturity. Too many organizations try to institute an EA program when the organization is not prepared to do so. Often, leadership hears or gets the pitch that EA will save the day and they start a program, without supporting the program, thinking that "doing" EA will fix everything. EA requires wide preparation and active participation.
+*Organizational Maturity. A mature organization is a base to start a successful EA program. On the other hand, an effective EA program improves organizational maturity. Too many organizations try to institute an EA program when they are not prepared to do so. Often, leadership hears or gets the pitch that EA will save the day and they start a program, without supporting the program, thinking that "doing" EA will fix everything. EA requires wide preparation and active participation.
 *Business/Architecture Alignment --> This has to be earned by EA Team and should not be considered a blank check or an entitlement, as this would require relationship management and transparency in delivery to match the business priorities. PMO and Architecture team are critical for earning and establishing trust.
 *Move from Vendor/Group/Institute-centric EA to Customer-centric EA. Advance from just being DNA or “enterprise genotype” (a full nomenclature of enterprise artifacts) to provide a formal link with “enterprise phenotype” (a set of observable characteristics such as performance) and business ecosystem.
@@ Line 176: / Line 176: @@
 == See Also ==
 *[[Enterprise Architecture Management (EAM)]]
-*[[ Enterprise Architecture Value Framework (EAVF)]]
+*[[Enterprise Architecture Value Framework (EAVF)]]
 *[[Business Systems Planning (BSP)]]
 *[[IT Capability]]

← Older revision		Revision as of 14:06, 21 November 2022
Line 194:		Line 194:
	*[https://www.cio.com/article/3253335/enterprise-architecture/why-enterprise-architecture-maximizes-organizational-value.html Why enterprise architecture maximizes organizational value]		*[https://www.cio.com/article/3253335/enterprise-architecture/why-enterprise-architecture-maximizes-organizational-value.html Why enterprise architecture maximizes organizational value]
	*[https://www.bcs.org/content/conWebDoc/59399 Enterprise architecture tools: Fake and real]		*[https://www.bcs.org/content/conWebDoc/59399 Enterprise architecture tools: Fake and real]
		+
		+	__NOTOC__

@@ Line 4: / Line 4: @@
 Often defined as a blueprint, Enterprise architecture (EA) is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy.
-Enterprise Architecture is critical for business IT alignment and business transformation in an organization. It helps visualize the current state, future state, and what needs to happen to migrate, determine where there are gaps between the current state and future requirements, understand how different processes overlap with each other, creating a business continuity plan so that people can continue to work in the event of a disaster, and, finally creating an IT architecture that is scalable.
+Enterprise Architecture is critical for business IT alignment and business transformation in an organization. It helps visualize the current state, future state, and what needs to happen to migrate, determine where there are gaps between the current state and future requirements, understand how different processes overlap with each other, create a business continuity plan so that people can continue to work in the event of a disaster, and, finally creating an IT architecture that is scalable.
@@ Line 16: / Line 13: @@
-== Essential Elements of Enterprise Architecture<ref>Essential Elements of Enterprise Architecture [https://cioindex.com/references/enterprise-architecture/ Essential Elements of Enterprise Architecture based on Sourabh Hajela's Definition of Enterprise Architecture]</ref> ==
+== Key Aspects of Enterprise Architecture Definition<ref>Essential Elements of Enterprise Architecture [https://cioindex.com/references/enterprise-architecture/ Key Aspects of Enterprise Architecture Definition as proposed by Sourabh Hajela]</ref> ==
 The key aspects in this definition of enterprise architecture: (If an enterprise architecture delivers on these points it would've met its obligation and become a tool for creating and communicating the value in an organization. The process that builds it is called enterprise architecture planning and that includes its use in IT Governance and its own governance.)
 *Enterprise Architecture is holistic: the scope of enterprise architecture planning is top to bottom, and left to right i.e. it spans the entire organization and all of its dimensions. However, that does not mean "here and now" i.e. an enterprise architecture can - should, and MUST - be built piece - domain - by piece not all at once.

@@ Line 46: / Line 46: @@
 *10. According to The Open Group “By being inclusive with all other management frameworks, EA is a discipline that helps the Enterprise define, develop and exploit the boundaryless information flow (BIF*) capabilities in order to achieve the Enterprise’s strategic intent.” Note: Boundaryless Information Flow is a Trademark of The Open Group
 *10. US Federal Enterprise Architecture Framework (FEAF) defines Enterprise architecture as "a management practice to maximize the contribution of an agency’s resources, IT investments, and system development activities to achieve its performance goals. Architecture describes clear relationships from strategic goals and objectives through investments to measurable performance improvements for the entire enterprise or a portion (or segment) of the enterprise”
-. [https://www.leanix.net/en/wiki/ea/enterprise-architecture According to LeanIX, Enterprise Architecture (EA) is] "a discipline that manages conflicting approaches to success within large-scale organizations. A specialty devoted equally to the worlds of IT and Business, it introduces practical standards across departmental units and teams in order to streamline efforts with an intelligent sharing of resources."
+*11. [https://www.leanix.net/en/wiki/ea/enterprise-architecture According to LeanIX, Enterprise Architecture (EA) is] "a discipline that manages conflicting approaches to success within large-scale organizations. A specialty devoted equally to the worlds of IT and Business, it introduces practical standards across departmental units and teams in order to streamline efforts with an intelligent sharing of resources."