Difference between revisions of "Main Page"
(Moved paragraphs from "What Is the EITBOK" to this page) |
|||
Line 8: | Line 8: | ||
It should be noted that the guide does not purport to define the entire body of knowledge for the Enterprise IT domain. Rather, it is to serve as a compendium and guide to the body of knowledge that has been developing and evolving since the 1960s. | It should be noted that the guide does not purport to define the entire body of knowledge for the Enterprise IT domain. Rather, it is to serve as a compendium and guide to the body of knowledge that has been developing and evolving since the 1960s. | ||
+ | |||
+ | Similarly, its purpose is *not* to show the reader how to do EIT work, but to show what types of work are needed in an Enterprise IT organization. For that reason, we refer the reader to established BOKS in specialized areas, such as business analysis and enterprise architecture. | ||
+ | |||
+ | The following specialized works are referenced in this BOK: | ||
+ | |||
+ | <ul> | ||
+ | Enterprise Architecture BOK (EABOK) | ||
This guide complements the “Bodies of Knowledge” outlined in the model computing curricula for undergraduate degrees. This guide discusses the application of knowledge in professional practice. While a university IT program may have a capstone project intended to demonstrate the integrated use of the 13 Knowledge areas in the IT curriculum, it cannot capture how these elements of the KAs come together in the professional lives of practitioners. | This guide complements the “Bodies of Knowledge” outlined in the model computing curricula for undergraduate degrees. This guide discusses the application of knowledge in professional practice. While a university IT program may have a capstone project intended to demonstrate the integrated use of the 13 Knowledge areas in the IT curriculum, it cannot capture how these elements of the KAs come together in the professional lives of practitioners. | ||
<p> If you have any questions about this effort, please contact Chuck Walrad, Editor-in-Chief, cwalrad@daven.com.</p> | <p> If you have any questions about this effort, please contact Chuck Walrad, Editor-in-Chief, cwalrad@daven.com.</p> |
Revision as of 00:08, 1 November 2016
Note: The EITBOK wiki is a work in progress, and may contain missing content, errors, or duplication.
In this guide, the IEEE Computer Society, in cooperation with the ACM IT2017 curriculum project, establishes a baseline for the body of knowledge for the practice of Enterprise information technology (EIT). This work has been undertaken as part of the Society’s responsibility to promote the advancement of both theory and practice in this field. It is written by practitioners, for practitioners, as well as for others who are interested in what EIT is. The authors are invited practitioners from different countries, professional associations, industry, government, and academia. They have contributed –and continue to contribute—hundreds of volunteer hours to the creation of this guide.
We have chosen to use the term Enterprise IT to distinguish it from the wider terms “IT” (Information Technology) and “ICT” (Information and Communications Technology), which are often used to refer to the entire industry of creating, selling, and using electronic information products.
It should be noted that the guide does not purport to define the entire body of knowledge for the Enterprise IT domain. Rather, it is to serve as a compendium and guide to the body of knowledge that has been developing and evolving since the 1960s.
Similarly, its purpose is *not* to show the reader how to do EIT work, but to show what types of work are needed in an Enterprise IT organization. For that reason, we refer the reader to established BOKS in specialized areas, such as business analysis and enterprise architecture.
The following specialized works are referenced in this BOK:
-
Enterprise Architecture BOK (EABOK)
This guide complements the “Bodies of Knowledge” outlined in the model computing curricula for undergraduate degrees. This guide discusses the application of knowledge in professional practice. While a university IT program may have a capstone project intended to demonstrate the integrated use of the 13 Knowledge areas in the IT curriculum, it cannot capture how these elements of the KAs come together in the professional lives of practitioners.
If you have any questions about this effort, please contact Chuck Walrad, Editor-in-Chief, cwalrad@daven.com.