Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Zachman Framework
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== "Information Systems Architecture" framework === [[File:ZFArticlePages.jpg|thumb|210px|The original 1987 "Information Systems Architecture Framework".]] [[File:Zachman Framework Detailed.jpg|thumb|320px|Simple example of the 1992 Framework.]] In the 1987 article "A Framework for Information Systems Architecture"<ref name="Zach87">{{cite journal |first=John A. |last=Zachman |authorlink=John Zachman |date=1987 |url=http://www.research.ibm.com/journal/50th/applications/zachman.html |title=A Framework for Information Systems Architecture |journal=IBM Systems Journal |volume=26 |issue=3 |id=IBM Publication G321-5298}}</ref> Zachman noted that the term "architecture" was used loosely by information systems professionals, and meant different things to planners, designers, programmers, communication specialists, and others.<ref name="Jac92">{{cite journal |first=Durward P. |last=Jackson |date=1992 |title=Process-Based Planning in Information Resource Management |journal=Emerging Information Technologies for Competitive Advantage and Economic Development: Proceedings of 1992 Information Resources Management Association International Conference |editor-first=Mehdi |editor-last=Khosrowpour |isbn=1-878289-17-9}}</ref> In searching for an objective, independent basis upon which to develop a framework for information systems architecture, Zachman looked at the field of classical [[architecture]], and a variety of complex engineering projects in industry. He saw a similar approach and concluded that architectures exist on many levels and involve at least three perspectives: raw material or [[data]], function or processes, and location or networks.<ref name="Jac92"/> Zachman's Information Systems Architecture is designed to be a classification schema for organizing architecture models. It provides a synoptic view of the models needed for enterprise architecture. Information Systems Architecture does not define in detail what the models should contain, it does not enforce the modeling language used for each model, and it does not propose a method for creating these models.<ref>[[Alain Wegmann]] et al. (2008). [http://infoscience.epfl.ch/record/129325/files/Wegmann_et_al-SEAM_%26_Zachman-EDOC2008.pdf "Augmenting the Zachman Enterprise Architecture Framework with a Systemic Conceptualization"]. Presented at the 12th IEEE International EDOC Conference (EDOC 2008), München, Germany, September 15–19, 2008.</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)