CSC/ECE 517 Fall 2010/ch6 6k JP: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
6k. Enterprise architecture. An enterprise architecture is a rigorous description of the structure of an enterprise, which comprise enterprise components (business entities), the externally visible properties of those components, and the relationships (e.g. the behavior) between them [from Wikipedia]. Explain how it relates to concepts covered in this course (e.g., separation of responsibility). How does designing an enterprise architecture relatee to developing a design for an o-o project? Does working on a larger scale require different skills? Also, contrast enterprise architecture with SOA (service-oriented architecture). | 6k. Enterprise architecture. An enterprise architecture is a rigorous description of the structure of an enterprise, which comprise enterprise components (business entities), the externally visible properties of those components, and the relationships (e.g. the behavior) between them [from Wikipedia]. Explain how it relates to concepts covered in this course (e.g., separation of responsibility). How does designing an enterprise architecture relatee to developing a design for an o-o project? Does working on a larger scale require different skills? Also, contrast enterprise architecture with SOA (service-oriented architecture). | ||
Similarities of Enterprise Architecture and Object Oriented Programming | |||
Enterprise Architecture describes a plan or strategy to incorporate a companies different divisions into an efficient system for achieving a company's goals. Similarly, Object Oriented Programming describes a design of classes and objects working together to achieve a particular output. | |||
Enterprise Architecture is a overarching term that deals with a number of different systems within an organization, including Information Technology. So it is no coincidence that similarities exist between Enterprise Architecture and Object Oriented Programming. | |||
Enterprise Architecture methodologies were created to address the increasing complexity of information systems in large organizations. Software Engineering is a growing field created by the need to organize more and more complex applications. | |||
The Zachman Framework for Enterprise Architectures | |||
"The [Enterprise Architecture] Framework as it applies to Enterprises is simply a logical structure for classifying and organizing the descriptive representations of an Enterprise that are significant to the management of the Enterprise, as well as to the development of the Enterprise's systems" Zachman, John A. "The Framework for Enterprise Architecture: Background, Description and Utility." Zachman Institute for Framework Advancement (ZIFA). Document ID: 810-231-0531 | |||
Basically the Zachman Framework for Enterprise Architectures categorizes different design documents into a matrix based on the particular user and their jobs. In OOA/OOD we organize our design specifications into a similar grid based on the implementation level. | |||
picutre from notes "Object-oriented Languages and Systems" page 3 lecture 15. | |||
picture of zachman framework - http://www.zachmanframeworkassociates.com/ | |||
architectural artifact—A specific document, report, analysis, model, or other tangible that contributes to an architectural description (http://msdn.microsoft.com/en-us/library/bb466232.aspx) |
Revision as of 15:42, 17 November 2010
- This page is currently under construction -
6k. Enterprise architecture. An enterprise architecture is a rigorous description of the structure of an enterprise, which comprise enterprise components (business entities), the externally visible properties of those components, and the relationships (e.g. the behavior) between them [from Wikipedia]. Explain how it relates to concepts covered in this course (e.g., separation of responsibility). How does designing an enterprise architecture relatee to developing a design for an o-o project? Does working on a larger scale require different skills? Also, contrast enterprise architecture with SOA (service-oriented architecture).
Similarities of Enterprise Architecture and Object Oriented Programming
Enterprise Architecture describes a plan or strategy to incorporate a companies different divisions into an efficient system for achieving a company's goals. Similarly, Object Oriented Programming describes a design of classes and objects working together to achieve a particular output.
Enterprise Architecture is a overarching term that deals with a number of different systems within an organization, including Information Technology. So it is no coincidence that similarities exist between Enterprise Architecture and Object Oriented Programming.
Enterprise Architecture methodologies were created to address the increasing complexity of information systems in large organizations. Software Engineering is a growing field created by the need to organize more and more complex applications.
The Zachman Framework for Enterprise Architectures
"The [Enterprise Architecture] Framework as it applies to Enterprises is simply a logical structure for classifying and organizing the descriptive representations of an Enterprise that are significant to the management of the Enterprise, as well as to the development of the Enterprise's systems" Zachman, John A. "The Framework for Enterprise Architecture: Background, Description and Utility." Zachman Institute for Framework Advancement (ZIFA). Document ID: 810-231-0531
Basically the Zachman Framework for Enterprise Architectures categorizes different design documents into a matrix based on the particular user and their jobs. In OOA/OOD we organize our design specifications into a similar grid based on the implementation level.
picutre from notes "Object-oriented Languages and Systems" page 3 lecture 15.
picture of zachman framework - http://www.zachmanframeworkassociates.com/
architectural artifact—A specific document, report, analysis, model, or other tangible that contributes to an architectural description (http://msdn.microsoft.com/en-us/library/bb466232.aspx)