Information Framework (IFW) - Revision history

User at 21:02, 28 August 2023

2023-08-28T21:02:18Z

User at 09:18, 17 January 2023

2023-01-17T09:18:51Z

User at 19:25, 20 September 2022

2022-09-20T19:25:33Z

User at 19:21, 20 September 2022

2022-09-20T19:21:42Z

User at 19:03, 20 September 2022

2022-09-20T19:03:26Z

User at 18:54, 20 September 2022

2022-09-20T18:54:29Z

User at 18:45, 20 September 2022

2022-09-20T18:45:08Z

User at 18:42, 20 September 2022

2022-09-20T18:42:53Z

User at 17:28, 20 September 2022

2022-09-20T17:28:04Z

User at 17:22, 20 September 2022

2022-09-20T17:22:48Z

@@ Line 1: / Line 1: @@
-'''Information FrameWork (IFW)''' is an enterprise architecture framework, populated with a comprehensive set of banking-specific [[Business Model|business models]]. It was developed by Roger Evernden as an alternative to the [[Zachman Framework]]. The banking-specific business models represent the best practices in banking and are a natural extension to the [[Component Business Model (CBM)|Component Business Model]].<ref>Definition of Information FrameWork (IFW) [https://en.wikipedia.org/wiki/Information_Framework]</ref>
+'''Information FrameWork (IFW)''' is an [[Enterprise Architecture Framework|enterprise architecture framework]], populated with a comprehensive set of banking-specific [[Business Model|business models]]. It was developed by Roger Evernden as an alternative to the [[Zachman Framework]]. The banking-specific business models represent the best practices in banking and are a natural extension to the [[Component Business Model (CBM)|Component Business Model]].<ref>Definition of Information FrameWork (IFW) [https://en.wikipedia.org/wiki/Information_Framework]</ref>
 The Information FrameWork (IFW) has built upon the ideas presented by Zachman. However, the objectives and scope of IFW are broader than that of the original Zachman framework. IFW is described and compared with the original Zachman structure, showing the evolution, changes, and rationale behind the changes based on experiences from within the financial services industry. Since 1992 Information FrameWork (IFW) has provided the architectural foundation and framework for a set of models developed to support agile, component-based IT systems. Although these models were aimed primarily for the Banking, Finance, and Securities industry sector within IBM, the ideas and principles behind the architecture and the model have much wider applicability.
@@ Line 93: / Line 93: @@
 === See Also ===
 *[[Strategic Information Systems Planning (SISP)]]
 === References ===
 <references/>

@@ Line 1: / Line 1: @@
-'''Information FrameWork (IFW)''' is an [[Enterprise Architecture Framework|enterprise architecture framework]], populated with a comprehensive set of banking-specific [[Business Model|business models]]. It was developed by Roger Evernden as an alternative to the [[Zachman Framework]]. The banking-specific business models represent the best practices in banking and are a natural extension to the [[Component Business Model (CBM)|Component Business Model]].<ref>Definition of Information FrameWork (IFW) [https://en.wikipedia.org/wiki/Information_Framework]</ref>
+'''Information FrameWork (IFW)''' is an enterprise architecture framework, populated with a comprehensive set of banking-specific [[Business Model|business models]]. It was developed by Roger Evernden as an alternative to the [[Zachman Framework]]. The banking-specific business models represent the best practices in banking and are a natural extension to the [[Component Business Model (CBM)|Component Business Model]].<ref>Definition of Information FrameWork (IFW) [https://en.wikipedia.org/wiki/Information_Framework]</ref>
 The Information FrameWork (IFW) has built upon the ideas presented by Zachman. However, the objectives and scope of IFW are broader than that of the original Zachman framework. IFW is described and compared with the original Zachman structure, showing the evolution, changes, and rationale behind the changes based on experiences from within the financial services industry. Since 1992 Information FrameWork (IFW) has provided the architectural foundation and framework for a set of models developed to support agile, component-based IT systems. Although these models were aimed primarily for the Banking, Finance, and Securities industry sector within IBM, the ideas and principles behind the architecture and the model have much wider applicability.
@@ Line 93: / Line 93: @@
 === See Also ===
-[[Enterprise Architecture]]<br />
+*[[Enterprise Architecture]]
-[[Enterprise Architecture Framework]]<br />
+*[[Strategic Information Systems Planning (SISP)]]
 === References ===
 <references/>

← Older revision		Revision as of 19:25, 20 September 2022
Line 47:		Line 47:

	'''IFW Supports Strategic Information Systems Planning<ref>IFW Supports Strategic Information Systems Planning [https://www.slideshare.net/Ravisarkar1/ifw-framework-for-banking-industry-presentation-38093834]</ref>'''<br />		'''IFW Supports Strategic Information Systems Planning<ref>IFW Supports Strategic Information Systems Planning [https://www.slideshare.net/Ravisarkar1/ifw-framework-for-banking-industry-presentation-38093834]</ref>'''<br />
−	IFW was designed to accommodate a variety of approaches and methodologies providing a comprehensive structure to manage architectures. Research suggests five different approaches ~~to Strategic Information Systems Planning~~ (SISP). ~~This~~ is ~~shown~~ in the diagram below:	+	IFW was designed to accommodate a variety of approaches and methodologies providing a comprehensive structure to manage architectures. Research by Michael Earl suggests that there are five different approaches for strategic information systems planning (SISP), each with different characteristics, strengths, and weaknesses. Although the research is based on information systems, the five approaches can be used in a more general sense to understand the different styles of information management. The five different approaches, with a discussion of how they are related to IFW, are illustrated in the diagram below:

@@ Line 77: / Line 77: @@
-Objectives of the Information FrameWork<ref>Objectives of the Information FrameWork [https://indexarticles.com/reference/ibm-systems-journal/the-information-framework/]</ref><br />
+'''Six Dimensions of the Information FrameWork'''<br />
 *Provide a strategy for managing information as a valuable asset: The need for a clear strategy for managing information has been a major issue in the 1990s. The focus of IFW is on information, and its primary objective is therefore to provide a strategy for managing information as a valuable asset; hence the name “Information FrameWork.” It was not named after information systems, application development, or any of a number of alternative uses of the word “information,” because IFW can be used in a wide range of information-related projects. Although IFW was initially developed for the financial services industry, IBM did not limit the name by calling it “Financial Services FrameWork,” because the principles and ideas behind IFW can be applied to information in any industry. Whereas the Zachman framework is focused on an information systems architecture, the Information FrameWork is aimed at managing information. ISA “provides a systematic taxonomy of concepts for relating things in the world to the representations in the computer.” It has been said that since the introduction of the Zachman framework it “has been widely adopted by systems analysts and database designers,” whereas IFW is suitable for use in any situation where “information” is created or used. This distinction, which has also been made by other framework developers, is of some importance because the underlying focus of a framework helps to determine the format of the framework itself.
 *Provide the means to realize the potential value of the information asset in the most effective manner: Much of the development work in IFW has been exploratory. The Zachman framework was tested in a number of projects, and, where necessary, enhancements were made. In philosophy, a framework is often used as an outline or hypothesis in the production of new knowledge. IFW has been used in this sense, with additions and changes to the basic hypothesis, evolving as IBM gained more experience through practical customer projects. IFW has drawn upon many sources for its intellectual foundation, including the notion of a “framework” from object-oriented theory. A paper by Cockburn states that a framework is “a template for a group of objects that manage a responsibility jointly, using a predefined protocol among themselves,” and goes on to say that the framework itself “consists of the statement of how the responsibility is divided and the definition of the protocol.” In this sense, the components of IFW have responsibility for managing information. The cells in IFW show the division of responsibility, with each cell localizing one aspect of the problem of managing information. The protocol is a methodology that explains exactly how component objects are grouped together in IFW to define solutions.

← Older revision		Revision as of 19:03, 20 September 2022
Line 78:		Line 78:

	Objectives of the Information FrameWork<ref>Objectives of the Information FrameWork [https://indexarticles.com/reference/ibm-systems-journal/the-information-framework/]</ref><br />		Objectives of the Information FrameWork<ref>Objectives of the Information FrameWork [https://indexarticles.com/reference/ibm-systems-journal/the-information-framework/]</ref><br />
		+	*Provide a strategy for managing information as a valuable asset: The need for a clear strategy for managing information has been a major issue in the 1990s. The focus of IFW is on information, and its primary objective is therefore to provide a strategy for managing information as a valuable asset; hence the name “Information FrameWork.” It was not named after information systems, application development, or any of a number of alternative uses of the word “information,” because IFW can be used in a wide range of information-related projects. Although IFW was initially developed for the financial services industry, IBM did not limit the name by calling it “Financial Services FrameWork,” because the principles and ideas behind IFW can be applied to information in any industry. Whereas the Zachman framework is focused on an information systems architecture, the Information FrameWork is aimed at managing information. ISA “provides a systematic taxonomy of concepts for relating things in the world to the representations in the computer.” It has been said that since the introduction of the Zachman framework it “has been widely adopted by systems analysts and database designers,” whereas IFW is suitable for use in any situation where “information” is created or used. This distinction, which has also been made by other framework developers, is of some importance because the underlying focus of a framework helps to determine the format of the framework itself.
		+	*Provide the means to realize the potential value of the information asset in the most effective manner: Much of the development work in IFW has been exploratory. The Zachman framework was tested in a number of projects, and, where necessary, enhancements were made. In philosophy, a framework is often used as an outline or hypothesis in the production of new knowledge. IFW has been used in this sense, with additions and changes to the basic hypothesis, evolving as IBM gained more experience through practical customer projects. IFW has drawn upon many sources for its intellectual foundation, including the notion of a “framework” from object-oriented theory. A paper by Cockburn states that a framework is “a template for a group of objects that manage a responsibility jointly, using a predefined protocol among themselves,” and goes on to say that the framework itself “consists of the statement of how the responsibility is divided and the definition of the protocol.” In this sense, the components of IFW have responsibility for managing information. The cells in IFW show the division of responsibility, with each cell localizing one aspect of the problem of managing information. The protocol is a methodology that explains exactly how component objects are grouped together in IFW to define solutions.

← Older revision		Revision as of 18:54, 20 September 2022
Line 75:		Line 75:
	*Responsibility - enterprises are formed by people. Everyone has some responsibility for the enterprise architecture. Some people are users; some people make decisions or fund changes; others supply components; and some architect! This factor covers all of these roles and accountabilities.		*Responsibility - enterprises are formed by people. Everyone has some responsibility for the enterprise architecture. Some people are users; some people make decisions or fund changes; others supply components; and some architect! This factor covers all of these roles and accountabilities.
	*Meta Levels - finally, enterprise architectures are very complex, and a key aspect of architecting is to view things at different meta-levels. For example, the metamodel is one of the most vital tools in EA. And a metaframework is arguably the most useful tool of all!		*Meta Levels - finally, enterprise architectures are very complex, and a key aspect of architecting is to view things at different meta-levels. For example, the metamodel is one of the most vital tools in EA. And a metaframework is arguably the most useful tool of all!
		+
		+
		+	Objectives of the Information FrameWork<ref>Objectives of the Information FrameWork [https://indexarticles.com/reference/ibm-systems-journal/the-information-framework/]</ref><br />
		+
		+
		+	=== See Also ===
		+	[[Enterprise Architecture]]<br />
		+	[[Enterprise Architecture Framework]]<br />
		+	[[Strategic Information Systems Planning (SISP)]]<br />
		+	[[Zachman Framework]]
		+
		+
		+	=== References ===
		+	<references/>

@@ Line 44: / Line 44: @@
 *Focus on achieving competitive differentiation;
 *Identify and leverage best practice behaviors across the organization
@@ Line 56: / Line 51: @@
 [[File:SISP and IFW.png|400px|SISP and IFW]]

@@ Line 3: / Line 3: @@
 The Information FrameWork (IFW) has built upon the ideas presented by Zachman. However, the objectives and scope of IFW are broader than that of the original Zachman framework. IFW is described and compared with the original Zachman structure, showing the evolution, changes, and rationale behind the changes based on experiences from within the financial services industry. Since 1992 Information FrameWork (IFW) has provided the architectural foundation and framework for a set of models developed to support agile, component-based IT systems. Although these models were aimed primarily for the Banking, Finance, and Securities industry sector within IBM, the ideas and principles behind the architecture and the model have much wider applicability.
-The Information Framework (IFW) has become part of what is commonly known as the Industry Models. The IBM Industry Models are used primarily for the development of internal company standards and provide an overall integration layer across an organization's existing and future IT investments. With their strong business and IT orientation, IBM Industry Models are designed to be customized to reflect the precise needs of every company using them. Hence, every company will have its own customized industry-specific version of IBM's data, process and service models, allowing them to represent areas that are unique to their business and constitute competitive advantage. In addition, the models can be easily augmented to embrace industry extensions, jurisdiction, and company-specific extensions easily.
+The Information Framework can be thought of as a giant filing system, with separate cabinets for further differentiation within the primary categories, and separate drawers within each cabinet for different types of analysis. The IFW diagram contains 50 cells to represent ten basic information types and five types of analysis.
 The Industry Models (IFW) has products for the following industries:
@@ Line 12: / Line 30: @@
 *Retail (Data).
 While in some markets IBM Industry Models have become de facto standards, their purpose is not to standardize at the level of an industry, but to provide the basis for defining corporate standards. IBM's approach is to facilitate or embody the most important industry standards, which are most often data models or messaging formats. Architectural elements in the IBM Industry Models are data models, process models, and service models.

← Older revision		Revision as of 17:28, 20 September 2022
Line 2:		Line 2:

	The Information FrameWork (IFW) has built upon the ideas presented by Zachman. However, the objectives and scope of IFW are broader than that of the original Zachman framework. IFW is described and compared with the original Zachman structure, showing the evolution, changes, and rationale behind the changes based on experiences from within the financial services industry. Since 1992 Information FrameWork (IFW) has provided the architectural foundation and framework for a set of models developed to support agile, component-based IT systems. Although these models were aimed primarily for the Banking, Finance, and Securities industry sector within IBM, the ideas and principles behind the architecture and the model have much wider applicability.		The Information FrameWork (IFW) has built upon the ideas presented by Zachman. However, the objectives and scope of IFW are broader than that of the original Zachman framework. IFW is described and compared with the original Zachman structure, showing the evolution, changes, and rationale behind the changes based on experiences from within the financial services industry. Since 1992 Information FrameWork (IFW) has provided the architectural foundation and framework for a set of models developed to support agile, component-based IT systems. Although these models were aimed primarily for the Banking, Finance, and Securities industry sector within IBM, the ideas and principles behind the architecture and the model have much wider applicability.
		+
		+	The Information Framework (IFW) has become part of what is commonly known as the Industry Models. The IBM Industry Models are used primarily for the development of internal company standards and provide an overall integration layer across an organization's existing and future IT investments. With their strong business and IT orientation, IBM Industry Models are designed to be customized to reflect the precise needs of every company using them. Hence, every company will have its own customized industry-specific version of IBM's data, process and service models, allowing them to represent areas that are unique to their business and constitute competitive advantage. In addition, the models can be easily augmented to embrace industry extensions, jurisdiction, and company-specific extensions easily.
		+
		+	The Industry Models (IFW) has products for the following industries:
		+	*Banking and Financial Markets (Data, Process, Services),
		+	*Insurance (Data, Process, Services),
		+	*Healthcare (Data),
		+	*Telecommunications (Data),
		+	*Retail (Data).
		+	While in some markets IBM Industry Models have become de facto standards, their purpose is not to standardize at the level of an industry, but to provide the basis for defining corporate standards. IBM's approach is to facilitate or embody the most important industry standards, which are most often data models or messaging formats. Architectural elements in the IBM Industry Models are data models, process models, and service models.

← Older revision		Revision as of 17:22, 20 September 2022
Line 1:		Line 1:
	'''Information FrameWork (IFW)''' is an [[Enterprise Architecture Framework\|enterprise architecture framework]], populated with a comprehensive set of banking-specific [[Business Model\|business models]]. It was developed by Roger Evernden as an alternative to the [[Zachman Framework]]. The banking-specific business models represent the best practices in banking and are a natural extension to the [[Component Business Model (CBM)\|Component Business Model]].<ref>Definition of Information FrameWork (IFW) [https://en.wikipedia.org/wiki/Information_Framework]</ref>		'''Information FrameWork (IFW)''' is an [[Enterprise Architecture Framework\|enterprise architecture framework]], populated with a comprehensive set of banking-specific [[Business Model\|business models]]. It was developed by Roger Evernden as an alternative to the [[Zachman Framework]]. The banking-specific business models represent the best practices in banking and are a natural extension to the [[Component Business Model (CBM)\|Component Business Model]].<ref>Definition of Information FrameWork (IFW) [https://en.wikipedia.org/wiki/Information_Framework]</ref>
		+
		+	The Information FrameWork (IFW) has built upon the ideas presented by Zachman. However, the objectives and scope of IFW are broader than that of the original Zachman framework. IFW is described and compared with the original Zachman structure, showing the evolution, changes, and rationale behind the changes based on experiences from within the financial services industry. Since 1992 Information FrameWork (IFW) has provided the architectural foundation and framework for a set of models developed to support agile, component-based IT systems. Although these models were aimed primarily for the Banking, Finance, and Securities industry sector within IBM, the ideas and principles behind the architecture and the model have much wider applicability.