http://eitbokwiki.org/api.php?action=feedcontributions&feedformat=atom&user=Daniel+RobbinsEITBOK - User contributions [en]2026-05-07T05:55:11ZUser contributionsMediaWiki 1.25.1http://eitbokwiki.org/index.php?title=Enterprise_IT_Skill_Frameworks&diff=701Enterprise IT Skill Frameworks2016-06-15T17:55:54Z<p>Daniel Robbins: Daniel Robbins moved page EIT Skills Matrix to Enterprise IT Skill Frameworks</p>
<hr />
<div><h2> Key Skills Introduction</h2><br />
<p>While many large companies have defined their own sets of skills for purposes of talent management (to recruit, retain, and further develop the highest quality staff members that they can find, afford and hire), the advancement of EIT professionalism will require common definitions of EIT skills that can be used not just across enterprises, but also across countries. We have selected three major sources of skill definitions. While none of them is used universally, they provide a good cross-section of options. Each chapter contains a short description of the three frameworks and list of the skills that apply to the chapter. </p><br />
<h2>Skills Framework for the Information Age</h2><br />
<p> The Skills Framework for the Information Age (SFIA) has defined nearly 100 skills. SFIA describes 7 levels of competency which can be applied to each skill. Not all skills, however, cover all seven levels. Some reach only partially up the seven step ladder. Others are based on mastering foundational skills, and start at the fourth or fifth level of competency. It is used in nearly 200 countries, from Britain to South Africa, South America, to the Pacific Rim, to the United States. (http://www.sfia-online.org)</p><br />
<br />
<h2>European Competency Framework</h2><br />
<p> The European Union's European Competency Framework (e-CF) has 40 “competencies” and is used in the EU. (http://www.ecompetences.eu/) It uses five levels of competency. As in SFIA, not all skills are subject to all 5 levels. The EU has also created a mapping between e-CF and SFIA.</p><br />
<h2>i-Competency Dictionary </h2><br />
<p>The Information Technology Promotion Agency in Japan has developed the i-CD, translated it into English, and describes it at https://www.ipa.go.jp/english/humandev/icd.html. . It is an extensive skills and tasks database, used in Japan and southeast Asian countries. Like SFIA, it establishes seven levels of competencies for skills. An example showcasing the skills and tasks relevant to this chapter is given below. </p></div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=EIT_Skills_Matrix&diff=702EIT Skills Matrix2016-06-15T17:55:54Z<p>Daniel Robbins: Daniel Robbins moved page EIT Skills Matrix to Enterprise IT Skill Frameworks</p>
<hr />
<div>#REDIRECT [[Enterprise IT Skill Frameworks]]</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=700MediaWiki:Sidebar2016-06-15T17:55:01Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits and Acknowledgements<br />
**Background|Background<br />
**Contributors|Contributors<br />
**Framework Document Reviewers|Framework Document Reviewers<br />
**Board of Governors' Approval|Board of Governors' Approval<br />
<br />
*Getting Started with the EITBOK<br />
**What is the Enterprise IT BOK?|What is the Enterprise IT BOK?<br />
**What is Enterprise IT?|What is Enterprise IT?<br />
<br />
*Part 1: The Enterprise Perspective<br />
**What is the Enterprise Perspective?|What is the Enterprise Perspective?<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Life Cycle Perspective<br />
**What Makes Up a Life Cycle?|What Makes Up a Life Cycle?<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Maintenance in Operation|14. Maintenance in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Enterprise IT Skill Frameworks|D. Enterprise IT Skill Frameworks<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Curriculum Mapping|H. Curriculum Mapping<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=524MediaWiki:Sidebar2016-04-20T06:10:55Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits and Acknowledgements<br />
**Background|Background<br />
**Contributors|Contributors<br />
**Framework Document Reviewers|Framework Document Reviewers<br />
**Board of Governors' Approval|Board of Governors' Approval<br />
<br />
*Getting Started with the EITBOK<br />
**What is the Enterprise IT BOK?|What is the Enterprise IT BOK?<br />
**What is Enterprise IT?|What is Enterprise IT?<br />
<br />
*Part 1: The Enterprise Perspective<br />
**What is the Enterprise Perspective?|What is the Enterprise Perspective?<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Life Cycle Perspective<br />
**What Makes Up a Life Cycle?|What Makes Up a Life Cycle?<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Maintenance in Operation|14. Maintenance in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**EIT Skills Matrix|D. EIT Skills Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Curriculum Mapping|H. Curriculum Mapping<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=482MediaWiki:Sidebar2016-02-22T01:21:12Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits and Acknowledgements<br />
**Background|Background<br />
**Contributors|Contributors<br />
**Framework Document Reviewers|Framework Document Reviewers<br />
**Board of Governors' Approval|Board of Governors' Approval<br />
<br />
*Getting Started with the EITBOK<br />
**What is the Enterprise IT BOK?|What is the Enterprise IT BOK?<br />
**What is Enterprise IT?|What is Enterprise IT?<br />
<br />
*Part 1: The Enterprise Perspective<br />
**What is the Enterprise Perspective?|What is the Enterprise Perspective?<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Life Cycle Perspective<br />
**What Makes Up a Life Cycle?|What Makes Up a Life Cycle?<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=What_is_the_Enterprise_IT_BOK%3F&diff=480What is the Enterprise IT BOK?2016-02-22T01:20:59Z<p>Daniel Robbins: Daniel Robbins moved page What is the Enterprise IT BoK? to What is the Enterprise IT BOK?</p>
<hr />
<div>In this guide, the IEEE Computer Society establishes a baseline for the body of knowledge for the practice of '''[http://eitbokwiki.org/Glossary#eit 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 experts 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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Furthermore, the practice of Enterprise IT necessarily requires the application of knowledge not just from the IT curriculum, but also from the adjacent disciplines of Information Systems and Software Engineering. This Guide attempts to help the practitioner and aspiring practitioner see themselves as part of a community of those who work together within enterprises across the globe to facilitate the successful execution of the enterprises activities. EIT, at its heart provides the circulatory system for the information that drives the enterprise’s decision-making and thus its ability to survive and thrive.<br />
<br />
By depicting the activities that an IT professional engages in we are able to see the skills needed to perform the various roles within an EIT organization.<br />
In this Guide, we refer to skills described in the Skills Framework for the Information Age, and roles described in ITIL and/or the ISO/IEC 20000 standard. Although there are very many nation-specific and region-specific job classification schemes and skill certifications, this Guide recognizes that EIT is global, and that its skills are international. For this reason, the most international reference points are used: SFIA and ITIL. We hope to add skills from the European Competency Framework (eCF) as well as the Japanese government’s ICompetency Dictionary.<br />
<br />
The development of this book has engaged the participation of individuals from several countries.<br />
<br />
There are several hallmarks for the maturing of a profession. One of the most important is an agreement by the professional community on what knowledge is included in the profession, including how that knowledge should be captured and organized to facilitate use by practitioners, researchers, and educators; i.e., a guide to its body of knowledge. Without a recognized body of knowledge for practitioners, each practitioner has no community-accepted framework to structure his understanding of the field, and any organization that certifies practicing Enterprise IT professionals and guides career development does so without the benefit of community-accepted standards. And in everyday work, the lack of a standard, commonly-accepted vocabulary to facilitate communication among its practitioners and with the larger enterprise they operate within impedes effectiveness and advancement. <br />
<br />
<h1>Motivation for the Guide</h1><br />
<br />
The EITBOK Guide project was undertaken because:<br />
<ul><br />
<li>There is no authoritative source that defines and organizes the knowledge across the whole of Enterprise IT, including its methods, processes, practices, and tools. The resulting knowledge gap creates unnecessary inconsistency and confusion in understanding roles in enterprise IT projects and programs; and in defining common products and processes. This EITBOK will fill that gap, becoming the “go to” reference for IT practitioners and practitioners to be.</li><br />
<br />
<li>The process of creating the Enterprise ITBOK Guide will help to build community consensus on the boundaries and context of Enterprise IT thinking, and use this to help understand and improve the ability of business management science and engineering disciplines to work together.</li><br />
<br />
<li>Having a common way to refer to Enterprise IT knowledge will facilitate communication among IT professionals and their business partners. It will also provide a shared baseline for consistent competency models, certification programs, educational programs, and other workforce development initiatives around the world.</li><br />
</ul><br />
<br />
The Enterprise ITBOK Guide leverages respected existing guides to bodies of knowledge in specific areas of IT practice, such as Business Analysis and Data Management. As well, these include guides to the related disciplines of software engineering (SwE) and project management (PM), and three of the five ACM/IEEE Computing Curricula: those for Software Engineering, Information Systems, and, of course, Information Technology. <br />
<br />
It is important to point out that the EITBOK Guide is not in itself an inclusive compendium of all Enterprise IT knowledge. Rather, this Guide to the Enterprise ITBOK is a portal that guides the user in finding and understanding where to seek information in the vast amount of material that has been separately published in books, articles, websites, and other generally accessible resources. All references included in the Enterprise ITBOK Guide are generally available to any interested reader; i.e., no proprietary information is referenced. However, references that are available to any interested reader are not necessarily free; some references are to books or standards that must be purchased. The criterion for inclusion is simply that the authors believed them to be among the best generally available sources of information on the topic.<br />
<br />
<h2>Objectives of the Guide</h2><br />
<br />
The Guide to the Enterprise IT Body of Knowledge (ITBOK) was established with the following objectives:<br />
<br />
<ul><br />
<li>To promote a consistent view of enterprise IT work and its importance, worldwide, across national boundaries</li><br />
<li>To provide consistency with an internationally accepted skills framework (SFIA) as the basis for role definitions within enterprise IT and therefore as a basis for competency evaluations</li><br />
<li>To provide a single, readily accessible portal to the widely scattered parts of the Body of Knowledge stretched across the globe.</li><br />
<li>To provide information about existing international standards that can be useful for IT practitioners and organizations.</li><br />
<li>To provide a common, unified foundation for discussing, analyzing and maturing the EIT profession.</li><br />
</ul><br />
<br />
<h1>Audience</h1><br />
<br />
Potential audiences for the Enterprise ITBOK will include<br />
<br />
<ul><br />
<li>Experienced and aspiring IT professionals.</li><br />
<li>Executives with an interest in managing enterprise IT assets to provide maximum value to the enterprise.</li><br />
<li>Business managers and information workers who rely on enterprise IT services.</li><br />
<li>Consultants conducting assessments of client IT areas and helping to implement and improve IT solutions at these clients.</li><br />
<li>Educators responsible for developing and delivering an IT curriculum.</li><br />
<li>Researchers in the field of information technology.</li><br />
<li>Acquirers and suppliers of enterprise IT services.</li><br />
<li>Policy makers charged with creating regulations, legislations, and operating environment for the practice of IT professions.</li><br />
<li>Other stakeholders and owners of some or all aspects of IT</li><br />
</ul><br />
<br />
<h1>Potential Uses of the Enterprise ITBOK Guide</h1><br />
<br />
IEEE-CS foresees several potential uses of the Enterprise ITBOK, including:<br />
<ul><br />
<li>Informing a diverse audience about the nature and importance of IT.</li><br />
<li>Helping build consensus within the IT community.</li><br />
<li>Providing common ground for assessments of IT effectiveness, maturity, and capability. </li><br />
<li>Guiding efforts to implement and improve IT Knowledge Areas (KA). </li><br />
<li>Educating students, new hires, practitioners, and executives on IT KAs.</li><br />
<li>Informing the development and delivery of IT curriculum content for higher education.</li><br />
<li>Suggesting areas of further research in the field of IT. Help organizations understand and define their enterprise IT strategies, tactics, and operations. </li><br />
</ul><br />
<br />
Like other Guides to professional bodies of knowledge, such as the SWEBOK, DAMA DMBOK, BABOK , and the SEBOK, this Guide can serve a variety of useful purposes.<br />
<br />
<table border="1" style="vertical-align:top; border-collapse: collapse; padding: 15px"><br />
<tr><br />
<th>Use</th><br />
<th>Description</th> </tr><br />
<tr><br />
<td>Inform Practice</td><br />
<td>Inform IT practitioners about the boundaries, terminology, and structure of their professional domain and point them to useful information needed to practice Enterprise IT in any type of enterprise</td></tr><br />
<tr><br />
<td>Inform Research</td><br />
<td>Inform researchers about the limitations and gaps in current Enterprise IT knowledge that should help guide their research agenda</td><tr><br />
<tr><br />
<td>Inform Curricula</td><br />
<td>Define the content that should be common in undergraduate and graduate programs that lead to careers in Enterprise IT</td></tr><br />
<tr><br />
<td>Inform Certification of Professionals</td><br />
<td>Define the skills for which to certify individuals as qualified to perform in Enterprise IT roles</td></tr><br />
<tr><br />
<td>Establish Common Competencies</td><br />
<td>Illuminate the competencies that IT practitioners should possess in various roles ranging from recent IT graduates to expert levels</td></tr><br />
</table><br />
<br />
As a guide to the body of knowledge, the Enterprise ITBOK Guide most directly enables Inform Practice and Inform Research. These are the heart of what the Enterprise is about. The Enterprise ITBOK Guide supports the remaining three uses, but less directly. For example, the task Certify Professionals is supported by the sections in each chapter that describe the skills needed to perform in that area. The Guide to the Enterprise ITBOK can play an important role in this area. As it stands today, there are thousands of different certifications offered by various vendors and various professional education companies. Very few of these, however, have been able to establish any value in the marketplace because there is no way to determine what essential higher-level skills they can lead to competencies in. That’s because there has been no commonly accepted model of essential IT competencies.<br />
The IEEE Computer Society has adopted the Skills Framework for the Information Age (SFIA) as the basis of IT competencies and is working with the SFIA Council and Foundation to better define skills in specific areas of specialization of increasing importance today. In addition, we have invited participation by the creators of the Japanese i-Competency Dictionary (iCD) of ICT skills and the European Competency Framework (e-CF).<br />
<br />
<h1>Scope of the Guide</h1><br />
<br />
The EITBOK addresses Enterprise IT functions, activities and roles in medium to large EIT organizations. Although small EIT organizations may not define jobs (positions) in the same way as larger organizations, the functions performed by various roles are still usually necessary. In the smaller organization, many roles may be carried out by a single person. Thus, the activities described here can apply to any size organization. However, we recognize that not all EIT organizations have the same breadth of responsibilities, so some of the activities described here may not be carried out by all organizations. <br />
<br />
<h1>Organization of the Guide</h1><br />
<br />
The EITBOK presupposes a flow of information and decision making from enterprise strategy formulation through various activities that cascade that strategy through the organization, via defined projects and translation of project results into operations.<br />
<br />
We have divided the EITBOK into two main parts: the Enterprise Perspective and the Life Cycle Perspective.<br />
<br />
The Enterprise Perspective presents subjects that bridge the enterprise and the EIT organization (Enterprise Architecture, Strategy and Governance, Change Initiatives) and that form the backdrop for all EIT projects (Interoperability, Security, Quality, Disaster Preparedness, and Operations and Support)<br />
<br />
</h1>Common Structure of the Knowledge Areas</h1><br />
<br />
The KAs in the EITBOK represent areas of practice rather than areas of learning. That is, in an EIT organization, we may find specialists in Security practices, in Disaster Recovery planning, in developing requirements for EIT services, or in Construction of those services.<br />
<br />
Each KA contains a context diagram that provides a quick overview of the KA. It shows activities requiring knowledge in the KA, information inputs to and outputs from the activities, and the roles involved in the activities.<br />
<br />
Each context diagram includes:<br />
<ul><br />
<li>Definition of the KA.</li><br />
<li>Goals of successfully performing the KA.</li><br />
<li>Activities: The list of high-level activities performed in the KA.</li><br />
<li>Information Inputs – information that is directly necessary for the KA activities to be carried out</li><br />
<li>Information Outputs --information directly produced by the activities for the benefit of other activities</li><br />
<li>Information Supplier Roles: Roles and/or teams that supply the inputs to the activity.</li><br />
<li>Information User Roles: Roles and/or teams that perform the activity.</li><br />
<li>KA Key roles: The most important roles acting within the KA.</li><br />
</ul><br />
<br />
[[file:ITBOK KA Diagram template-simpllified - KA Context Diagram.jpeg | 600 px]]<br />
<br />
<em>Figure 3 is an example of a context diagram for a KA.</em><br />
<br />
Each KA description follows the same structure:<br />
<ul><br />
<li>Acronyms and Abbreviations</li><br />
<li>Introduction: Overview of the KA and its boundaries</li><br />
<li>Goals and Guiding Principles</li><br />
<li>Context Diagram</li><br />
<li>Description of activities in the KA</li><br />
<li>Skills </li><br />
<li>Roles</li><br />
<li>Standards</li><br />
</ul></div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=What_is_the_Enterprise_IT_BoK%3F&diff=481What is the Enterprise IT BoK?2016-02-22T01:20:59Z<p>Daniel Robbins: Daniel Robbins moved page What is the Enterprise IT BoK? to What is the Enterprise IT BOK?</p>
<hr />
<div>#REDIRECT [[What is the Enterprise IT BOK?]]</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=442MediaWiki:Sidebar2016-02-05T04:58:15Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*Getting Started with the EITBOK?<br />
**What is the Enterprise IT BoK?|What is the Enterprise IT BoK?<br />
**What is Enterprise IT?|What is Enterprise IT?<br />
<br />
*Part 1: The Enterprise Perspective<br />
**What is the Enterprise Perspective?|What is the Enterprise Perspective?<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Life Cycle Perspective<br />
**What Makes Up a Life Cycle?|What Makes Up a Life Cycle?<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
*Credits and Acknowledgements<br />
**Background|Background<br />
**Contributors|Contributors<br />
**Framework Document Reviewers|Framework Document Reviewers<br />
**Board of Governors' Approval|Board of Governors' Approval<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=441MediaWiki:Sidebar2016-02-05T04:57:06Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*Getting Started with the EITBOK?<br />
**What is the Enterprise IT BoK?|What is the Enterprise IT BoK?<br />
**What is Enterprise IT?|What is Enterprise IT?<br />
<br />
*Part 1: The Enterprise Perspective<br />
**What is the Enterprise Perspective?|What is the Enterprise Perspective?<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Life Cycle Perspective<br />
**What Makes Up a Life Cycle?|What Makes Up a Life Cycle?<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
*Credits/Acknowledgements<br />
**Background|Background<br />
**Contributors|Contributors<br />
**Framework Document Reviewers|Framework Document Reviewers<br />
**Board of Governors' Approval|Board of Governors' Approval<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=398MediaWiki:Sidebar2016-02-02T04:52:46Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*Getting Started with the EITBOK?<br />
**What is the Enterprise IT BoK?|What is the Enterprise IT BoK?<br />
**What is Enterprise IT?|What is Enterprise IT?<br />
<br />
*Part 1: The Enterprise Perspective<br />
**What is the Enterprise Perspective?|What is the Enterprise Perspective?<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Life Cycle Perspective<br />
**What Makes Up a Life Cycle?|What Makes Up a Life Cycle?<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=What_is_the_Enterprise_IT_BOK%3F&diff=396What is the Enterprise IT BOK?2016-02-02T04:51:39Z<p>Daniel Robbins: Daniel Robbins moved page Motivation for the Guide to What is the Enterprise IT BoK?</p>
<hr />
<div><h1>Introduction to the Guide</h1><br />
<br />
In this guide, the IEEE Computer Society 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 experts 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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Furthermore, the practice of Enterprise IT necessarily requires the application of knowledge not just from the IT curriculum, but also from the adjacent disciplines of Information Systems and Software Engineering. This Guide attempts to help the practitioner and aspiring practitioner see themselves as part of a community of those who work together within enterprises across the globe to facilitate the successful execution of the enterprises activities. EIT, at its heart provides the circulatory system for the information that drives the enterprise’s decision-making and thus its ability to survive and thrive.<br />
<br />
By depicting the activities that an IT professional engages in we are able to see the skills needed to perform the various roles within an EIT organization.<br />
In this Guide, we refer to skills described in the Skills Framework for the Information Age, and roles described in ITIL and/or the ISO/IEC 20000 standard. Although there are very many nation-specific and region-specific job classification schemes and skill certifications, this Guide recognizes that EIT is global, and that its skills are international. For this reason, the most international reference points are used: SFIA and ITIL. We hope to add skills from the European Competency Framework (eCF) as well as the Japanese government’s ICompetency Dictionary.<br />
<br />
The development of this book has engaged the participation of individuals from several countries.<br />
<br />
There are several hallmarks for the maturing of a profession. One of the most important is an agreement by the professional community on what knowledge is included in the profession, including how that knowledge should be captured and organized to facilitate use by practitioners, researchers, and educators; i.e., a guide to its body of knowledge. Without a recognized body of knowledge for practitioners, each practitioner has no community-accepted framework to structure his understanding of the field, and any organization that certifies practicing Enterprise IT professionals and guides career development does so without the benefit of community-accepted standards. And in everyday work, the lack of a standard, commonly-accepted vocabulary to facilitate communication among its practitioners and with the larger enterprise they operate within impedes effectiveness and advancement. <br />
<br />
<h2>Motivation for the Guide</h2><br />
<br />
The EITBOK Guide project was undertaken because:<br />
<ul><br />
<li>There is no authoritative source that defines and organizes the knowledge across the whole of Enterprise IT, including its methods, processes, practices, and tools. The resulting knowledge gap creates unnecessary inconsistency and confusion in understanding roles in enterprise IT projects and programs; and in defining common products and processes. This EITBOK will fill that gap, becoming the “go to” reference for IT practitioners and practitioners to be.</li><br />
<br />
<li>The process of creating the Enterprise ITBOK Guide will help to build community consensus on the boundaries and context of Enterprise IT thinking, and use this to help understand and improve the ability of business management science and engineering disciplines to work together.</li><br />
<br />
<li>Having a common way to refer to Enterprise IT knowledge will facilitate communication among IT professionals and their business partners. It will also provide a shared baseline for consistent competency models, certification programs, educational programs, and other workforce development initiatives around the world.</li><br />
</ul><br />
<br />
The Enterprise ITBOK Guide leverages respected existing guides to bodies of knowledge in specific areas of IT practice, such as Business Analysis and Data Management. As well, these include guides to the related disciplines of software engineering (SwE) and project management (PM), and three of the five ACM/IEEE Computing Curricula: those for Software Engineering, Information Systems, and, of course, Information Technology. <br />
<br />
It is important to point out that the EITBOK Guide is not in itself an inclusive compendium of all Enterprise IT knowledge. Rather, this Guide to the Enterprise ITBOK is a portal that guides the user in finding and understanding where to seek information in the vast amount of material that has been separately published in books, articles, websites, and other generally accessible resources. All references included in the Enterprise ITBOK Guide are generally available to any interested reader; i.e., no proprietary information is referenced. However, references that are available to any interested reader are not necessarily free; some references are to books or standards that must be purchased. The criterion for inclusion is simply that the authors believed them to be among the best generally available sources of information on the topic.<br />
<br />
<h2>Objectives of the Guide</h2><br />
<br />
The Guide to the Enterprise IT Body of Knowledge (ITBOK) was established with the following objectives:<br />
<br />
<ul><br />
<li>To promote a consistent view of enterprise IT work and its importance, worldwide, across national boundaries</li><br />
<li>To provide consistency with an internationally accepted skills framework (SFIA) as the basis for role definitions within enterprise IT and therefore as a basis for competency evaluations</li><br />
<li>To provide a single, readily accessible portal to the widely scattered parts of the Body of Knowledge stretched across the globe.</li><br />
<li>To provide information about existing international standards that can be useful for IT practitioners and organizations.</li><br />
<li>To provide a common, unified foundation for discussing, analyzing and maturing the EIT profession.</li><br />
</ul><br />
<br />
<h2>Audience</h2><br />
<br />
Potential audiences for the Enterprise ITBOK will include<br />
<br />
<ul><br />
<li>Experienced and aspiring IT professionals.</li><br />
<li>Executives with an interest in managing enterprise IT assets to provide maximum value to the enterprise.</li><br />
<li>Business managers and information workers who rely on enterprise IT services.</li><br />
<li>Consultants conducting assessments of client IT areas and helping to implement and improve IT solutions at these clients.</li><br />
<li>Educators responsible for developing and delivering an IT curriculum.</li><br />
<li>Researchers in the field of information technology.</li><br />
<li>Acquirers and suppliers of enterprise IT services.</li><br />
<li>Policy makers charged with creating regulations, legislations, and operating environment for the practice of IT professions.</li><br />
<li>Other stakeholders and owners of some or all aspects of IT</li><br />
</ul><br />
<br />
<h2>Potential Uses of the Enterprise ITBOK Guide</h2><br />
<br />
IEEE-CS foresees several potential uses of the Enterprise ITBOK, including:<br />
<ul><br />
<li>Informing a diverse audience about the nature and importance of IT.</li><br />
<li>Helping build consensus within the IT community.</li><br />
<li>Providing common ground for assessments of IT effectiveness, maturity, and capability. </li><br />
<li>Guiding efforts to implement and improve IT Knowledge Areas (KA). </li><br />
<li>Educating students, new hires, practitioners, and executives on IT KAs.</li><br />
<li>Informing the development and delivery of IT curriculum content for higher education.</li><br />
<li>Suggesting areas of further research in the field of IT. Help organizations understand and define their enterprise IT strategies, tactics, and operations. </li><br />
</ul><br />
<br />
Like other Guides to professional bodies of knowledge, such as the SWEBOK, DAMA DMBOK, BABOK , and the SEBOK, this Guide can serve a variety of useful purposes.<br />
<br />
<table border="1" style="vertical-align:top; border-collapse: collapse; padding: 15px"><br />
<tr><br />
<th>Use</th><br />
<th>Description</th> </tr><br />
<tr><br />
<td>Inform Practice</td><br />
<td>Inform IT practitioners about the boundaries, terminology, and structure of their professional domain and point them to useful information needed to practice Enterprise IT in any type of enterprise</td></tr><br />
<tr><br />
<td>Inform Research</td><br />
<td>Inform researchers about the limitations and gaps in current Enterprise IT knowledge that should help guide their research agenda</td><tr><br />
<tr><br />
<td>Inform Curricula</td><br />
<td>Define the content that should be common in undergraduate and graduate programs that lead to careers in Enterprise IT</td></tr><br />
<tr><br />
<td>Inform Certification of Professionals</td><br />
<td>Define the skills for which to certify individuals as qualified to perform in Enterprise IT roles</td></tr><br />
<tr><br />
<td>Establish Common Competencies</td><br />
<td>Illuminate the competencies that IT practitioners should possess in various roles ranging from recent IT graduates to expert levels</td></tr><br />
</table><br />
<br />
As a guide to the body of knowledge, the Enterprise ITBOK Guide most directly enables Inform Practice and Inform Research. These are the heart of what the Enterprise is about. The Enterprise ITBOK Guide supports the remaining three uses, but less directly. For example, the task Certify Professionals is supported by the sections in each chapter that describe the skills needed to perform in that area. The Guide to the Enterprise ITBOK can play an important role in this area. As it stands today, there are thousands of different certifications offered by various vendors and various professional education companies. Very few of these, however, have been able to establish any value in the marketplace because there is no way to determine what essential higher-level skills they can lead to competencies in. That’s because there has been no commonly accepted model of essential IT competencies.<br />
The IEEE Computer Society has adopted the Skills Framework for the Information Age (SFIA) as the basis of IT competencies and is working with the SFIA Council and Foundation to better define skills in specific areas of specialization of increasing importance today. In addition, we have invited participation by the creators of the Japanese i-Competency Dictionary (iCD) of ICT skills and the European Competency Framework (e-CF).<br />
<br />
<h2>Scope of the Guide</h2><br />
<br />
The EITBOK addresses Enterprise IT functions, activities and roles in medium to large EIT organizations. Although small EIT organizations may not define jobs (positions) in the same way as larger organizations, the functions performed by various roles are still usually necessary. In the smaller organization, many roles may be carried out by a single person. Thus, the activities described here can apply to any size organization. However, we recognize that not all EIT organizations have the same breadth of responsibilities, so some of the activities described here may not be carried out by all organizations. <br />
<br />
<h2>Organization of the Guide</h2><br />
<br />
The EITBOK presupposes a flow of information and decision making from enterprise strategy formulation through various activities that cascade that strategy through the organization, via defined projects and translation of project results into operations.<br />
<br />
We have divided the EITBOK into two main parts: the Enterprise Perspective and the Life Cycle Perspective.<br />
<br />
The Enterprise Perspective presents subjects that bridge the enterprise and the EIT organization (Enterprise Architecture, Strategy and Governance, Change Initiatives) and that form the backdrop for all EIT projects (Interoperability, Security, Quality, Disaster Preparedness, and Operations and Support)<br />
<br />
</h2>Common Structure of the Knowledge Areas</h2><br />
<br />
The KAs in the EITBOK represent areas of practice rather than areas of learning. That is, in an EIT organization, we may find specialists in Security practices, in Disaster Recovery planning, in developing requirements for EIT services, or in Construction of those services.<br />
<br />
Each KA contains a context diagram that provides a quick overview of the KA. It shows activities requiring knowledge in the KA, information inputs to and outputs from the activities, and the roles involved in the activities.<br />
<br />
Each context diagram includes:<br />
<ul><br />
<li>Definition of the KA.</li><br />
<li>Goals of successfully performing the KA.</li><br />
<li>Activities: The list of high-level activities performed in the KA.</li><br />
<li>Information Inputs – information that is directly necessary for the KA activities to be carried out</li><br />
<li>Information Outputs --information directly produced by the activities for the benefit of other activities</li><br />
<li>Information Supplier Roles: Roles and/or teams that supply the inputs to the activity.</li><br />
<li>Information User Roles: Roles and/or teams that perform the activity.</li><br />
<li>KA Key roles: The most important roles acting within the KA.</li><br />
</ul><br />
<br />
<strong>CONTEXT DIAGRAM GOES HERE</strong><br />
<br />
<em>Figure 3 is an example of a context diagram for a KA.</em><br />
<br />
Each KA description follows the same structure:<br />
<ul><br />
<li>Acronyms and Abbreviations</li><br />
<li>Introduction: Overview of the KA and its boundaries</li><br />
<li>Goals and Guiding Principles</li><br />
<li>Context Diagram</li><br />
<li>Description of activities in the KA</li><br />
<li>Skills </li><br />
<li>Roles</li><br />
<li>Standards</li><br />
</ul></div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=Motivation_for_the_Guide&diff=397Motivation for the Guide2016-02-02T04:51:39Z<p>Daniel Robbins: Daniel Robbins moved page Motivation for the Guide to What is the Enterprise IT BoK?</p>
<hr />
<div>#REDIRECT [[What is the Enterprise IT BoK?]]</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=372MediaWiki:Sidebar2015-12-28T02:36:16Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*What is the Enterprise IT BoK?<br />
**Motivation for the Guide|Motivation for the Guide<br />
**Objectives of the Guide|Objectives of the Guide<br />
**Audience|Audience<br />
**Potential Uses of the Enterprise ITBOK Guide|Potential Uses of the Enterprise ITBOK Guide<br />
**Scope of the Guide|Scope of the Guide<br />
**Organization of the Guide|Organization of the Guide<br />
**Common Structure and Knowledge Areas|Common Structure and Knowledge Areas<br />
<br />
*Part 1: The Enterprise Perspective<br />
**What is the Enterprise Perspective?|What is the Enterprise Perspective?<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**What Makes Up a Lifecycle?|What Makes Up a Lifecycle?<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=371MediaWiki:Sidebar2015-12-28T02:31:28Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*What is the Enterprise IT BoK?<br />
**Motivation for the Guide|Motivation for the Guide<br />
**Objectives of the Guide|Objectives of the Guide<br />
**Audience|Audience<br />
**Potential Uses of the Enterprise ITBOK Guide|Potential Uses of the Enterprise ITBOK Guide<br />
**Scope of the Guide|Scope of the Guide<br />
**Organization of the Guide|Organization of the Guide<br />
**Common Structure and Knowledge Areas|Common Structure and Knowledge Areas<br />
<br />
*Part 1: The Enterprise Perspective<br />
**What is the Enterprise Perspective?|What is the Enterprise Perspective?<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=369MediaWiki:Sidebar2015-12-02T15:51:08Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*What is the Enterprise IT BoK?<br />
**Motivation for the Guide|Motivation for the Guide<br />
**Objectives of the Guide|Objectives of the Guide<br />
**Audience|Audience<br />
**Potential Uses of the Enterprise ITBOK Guide|Potential Uses of the Enterprise ITBOK Guide<br />
**Scope of the Guide|Scope of the Guide<br />
**Organization of the Guide|Organization of the Guide<br />
**Common Structure and Knowledge Areas|Common Structure and Knowledge Areas<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=368MediaWiki:Sidebar2015-12-02T15:50:22Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*What is the Enterprise IT BoK?<br />
**Motivation for the Guide|Motivation for the Guide<br />
**Objectives of the Guide|Objectives of the Guide<br />
**Audience|Audience<br />
**Potential Uses of the Enterprise ITBOK Guide<br />
**Scope of the Guide<br />
**Organization of the Guide<br />
**Common Structure and Knowledge Areas<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=202MediaWiki:Sidebar2015-11-03T23:54:14Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*Preface<br />
**Foreword|Foreword<br />
**What is the Enterprise ITBOK?|What is the Enterprise ITBOK?<br />
**History|History<br />
**Purpose|Purpose<br />
**Goals|Goals<br />
**Audience|Audience<br />
**Potential Uses|Potential Uses<br />
**Knowledge Areas|Knowledge Areas<br />
**Context Diagrams|Context Diagrams<br />
**Structure|Structure<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: Introduction to the Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Preparedness<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. Introduction to the Lifecycle Perspective<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=201MediaWiki:Sidebar2015-11-03T23:38:43Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*Preface<br />
**Foreword|Foreword<br />
**What is the Enterprise ITBOK?|What is the Enterprise ITBOK?<br />
**History|History<br />
**Purpose|Purpose<br />
**Goals|Goals<br />
**Audience|Audience<br />
**Potential Uses|Potential Uses<br />
**Knowledge Areas|Knowledge Areas<br />
**Context Diagrams|Context Diagrams<br />
**Structure|Structure<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
**Ethics|9. Ethics<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|10. Requirements<br />
**Acquisition|11. Acquisition<br />
**Construction|12. Construction<br />
**Transition into Operation|13. Transition into Operation<br />
**Sustainment in Operation|14. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=200MediaWiki:Sidebar2015-11-03T23:37:44Z<p>Daniel Robbins: </p>
<hr />
<div>*blah<br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*Preface<br />
**Foreword|Foreword<br />
**What is the Enterprise ITBOK?|What is the Enterprise ITBOK?<br />
**History|History<br />
**Purpose|Purpose<br />
**Goals|Goals<br />
**Audience|Audience<br />
**Potential Uses|Potential Uses<br />
**Knowledge Areas|Knowledge Areas<br />
**Context Diagrams|Context Diagrams<br />
**Structure|Structure<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|9. Requirements<br />
**Acquisition|10. Acquisition<br />
**Construction|11. Construction<br />
**Transition into Operation|12. Transition into Operation<br />
**Sustainment in Operation|13. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=199MediaWiki:Sidebar2015-11-03T23:37:34Z<p>Daniel Robbins: </p>
<hr />
<div><br />
*Credits/Acknowledgements<br />
**Steering Committee Members|a. Steering Committee Members<br />
**Contributor List|b. Contributor List<br />
**PAB-IT Roster|c. PAB-IT Roster<br />
**List of Public Reviewers|d. List of Public Reviewers<br />
**Notice of PEB and BOG Approval|e. Notice of PEB and BOG Approval<br />
<br />
*Preface<br />
**Foreword|Foreword<br />
**What is the Enterprise ITBOK?|What is the Enterprise ITBOK?<br />
**History|History<br />
**Purpose|Purpose<br />
**Goals|Goals<br />
**Audience|Audience<br />
**Potential Uses|Potential Uses<br />
**Knowledge Areas|Knowledge Areas<br />
**Context Diagrams|Context Diagrams<br />
**Structure|Structure<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|9. Requirements<br />
**Acquisition|10. Acquisition<br />
**Construction|11. Construction<br />
**Transition into Operation|12. Transition into Operation<br />
**Sustainment in Operation|13. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=198MediaWiki:Sidebar2015-11-03T23:30:29Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
**Table of Contents|Table of Contents<br />
<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|9. Requirements<br />
**Acquisition|10. Acquisition<br />
**Construction|11. Construction<br />
**Transition into Operation|12. Transition into Operation<br />
**Sustainment in Operation|13. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=197MediaWiki:Sidebar2015-11-03T23:30:17Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
**Table of Contents|Table of Contents<br />
<br />
*Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|9. Requirements<br />
**Acquisition|10. Acquisition<br />
**Construction|11. Construction<br />
**Transition into Operation|12. Transition into Operation<br />
**Sustainment in Operation|13. Sustainment in Operation<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=196MediaWiki:Sidebar2015-11-03T23:08:55Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition into Operation|11. Transition into Operation<br />
**Sustainment in Operation|12. Sustainment in Operation<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Key Standards|E. Key Standards<br />
**Consolidated References List|F. Consolidated References List<br />
**Input & Outputs Matrix|G. Inputs & Outputs Matrix<br />
**Mapping to ACM/IEEE IT 2008 Curriculum|H. Mapping to ACM/IEEE IT 2008 Curriculum<br />
**Mapping to IS 2010 Curriculum|I. Mapping to IS 2010 Curriculum<br />
**Mapping to SE 2014 Curriculum|J. Mapping to IS 2014 Curriculum<br />
<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=Key_Standards&diff=194Key Standards2015-11-03T23:05:38Z<p>Daniel Robbins: Daniel Robbins moved page Standards to Key Standards</p>
<hr />
<div><h2>Purpose of This Standards Guide</h2><br />
<p>This guide is designed for software producers, as well as producers of systems with embedded software. The purpose of this guide is to help informatics practitioners ensure that developed and deployed systems and software have the following characteristics:</p><br />
<ul><br />
<li>They can be and are verified and validated.</li><br />
<li>They meet the purpose for which they are intended.</li><br />
<li>They are robust, reliable and resilient enough to consistently perform to their intended use.</li><br />
</ul><br />
<p>IEEE System and Software Engineering Standards are as critical to industry as they have been to space exploration. This guide introduces you to the core subset of S2ESC’s portfolio of standards.</p><br />
<h3>The Value of System and Software Standards to Industry</h3><br />
<p>The aggressive transition to technology-based information is successful only if software and software-intensive systems &mdash; which encompass myriad products and processes in complex ways &mdash; seamlessly collect, aggregate, share, analyze, and present dynamic information in a timely manner.</p><br />
<p>For example, the anticipated human and economic benefits from the present rapid transition to health information technologies demand that software and systems developers of medical devices, digital medical records, and administrative, financial, and regulatory systems (e.g., public health, service/healthcare providers, and payers) design, develop, and deliver interoperable products, processes, and services that are safe, secure, reliable, and robust. </p><br />
<p>The application of IEEE S2ESC systems and software standards helps software producers by ''simplifying product development processes'', ''avoiding the pitfalls that have overcome many software projects'', and thus ''reduces non-value-adding efforts and costs''. Adoption and implementation of the core software and systems engineering standards across companies that produce or tailor information systems and devices ''increases their development organization’s ability to deliver robust software in shorter time frames''. Even more important, the consistent use of these IEEE standards lowers the risks of delivering faulty products.</p><br />
<p>Standards for Software and Systems Engineering encompass the full software and systems life cycles, from concept and development to delivery and maintenance, and even the reuse of software components. </p><br />
<h3>Standards Essential To Informatics Technology Producers</h3><br />
<p>Ensuring that delivered software meets its purpose and consistently performs to its intended use is vital to effective information delivery. As fundamental building blocks for international systems and software development, IEEE Software and Systems Engineering Standards help producers ensure interconnectivity, interoperability and verification of new informatics products and systems enabling the rapid implementation and trusted use of medical technologies.</p><br />
<p>The essential set [[#One|[1]]] of IEEE System and Software Standards that are key to the development and delivery of robust software are listed in the table below.</p><br />
<p>'''Table 1. Essential Standards'''</p><br />
<table border="1" cellpadding="10" width="900"><br />
<tr valign="top"><td width="20%" style="background-color: #58ACFA;"><font color="white">'''Number'''</font></td><td width="20%" style="background-color: #58ACFA;"><font color="white">'''Official Designation'''</font></td><td style="background-color: #58ACFA;"><font color="white">'''Name'''</font></td></tr><br />
<tr valign="top"><br />
<td>730</td><td>IEEE Std 730-2002</td><td>IEEE Standard for Software Quality Assurance Plans</td></tr><br />
<tr valign="top"><br />
<td>828</td><td>IEEE Std 828-1998 (R2005)</td><td>IEEE Standard for Software Configuration Management</td></tr><br />
<tr valign="top"><br />
<td>830</td><td>IEEE Std 830-1998</td><td>IEEE Recommended Practice for Software Requirements Specifications</td></tr><br />
<tr valign="top"><br />
<td>1008</td><td>IEEE Std 1008-1987(R2002) </td><td>IEEE Standard for Software Unit Testing</td></tr><br />
<tr valign="top"><br />
<td>1012</td><td>IEEE Std 1012-2004 </td><td>IEEE Standard for System and Software Verification and Validation</td></tr><br />
<tr valign="top"><br />
<td>1016</td><td>IEEE Std 1016-1998(R2009)</td><td>IEEE Recommended Practice for Software Design Descriptions</td></tr><br />
<tr valign="top"><br />
<td>1028</td><td>IEEE Std 1028-2008 </td><td>IEEE Standard for Software Reviews and Audits</td></tr><br />
<tr valign="top"><br />
<td>1058</td><td>IEEE Std 1058-1998</td><td>IEEE Standard for Software Project Management Plans</td></tr><br />
<tr valign="top"><br />
<td>1063</td><td>IEEE Std 1063-2001 (R2007)</td><td>IEEE Standard for Software User Documentation</td></tr><br />
<tr valign="top"><br />
<td>1074</td><td>IEEE Std 1074-2006</td><td>IEEE Standard for Developing a Software Project Life-cycle Process</td></tr><br />
<tr valign="top"><br />
<td>12207</td><td>ISO/IEC/IEEE 12207: 2008</td><td>Systems and Software Engineering &mdash; life-cycle processes</td></tr><br />
<tr valign="top"><br />
<td>14764</td><td>IEEE Std 14764-2006 </td><td>Software Engineering &mdash; System Life-cycle Processes &mdash; Maintenance</td></tr></table><br />
<p>In addition, HITSP may wish to examine these S2ESC standards. </p><br />
<p>'''Table 2. Additional Standards'''</p><br />
<table border="1" cellpadding="10" width="900"><br />
<tr valign="top"><td width="20%" style="background-color: #58ACFA;"><font color="white">'''Number'''</font></td><td width="20%" style="background-color: #58ACFA;"><font color="white">'''Official Designation'''</font></td><td style="background-color: #58ACFA;"><font color="white">'''Name'''</font></td></tr><br />
<tr valign="top"><br />
<td>829</td><td>IEEE Std 829-2008 (March 27)</td><td>IEEE Standard for Software and System Test Documentation</td></tr><br />
<tr valign="top"><br />
<td>1044</td><td>IEEE Std 1044-2002 </td><td>IEEE Standard Classification for Software Anomalies</td></tr><br />
<tr valign="top"><br />
<td>1062</td><td>IEEE Std 1062-2002 </td><td>IEEE Recommended Practice for Software Acquisition</td></tr><br />
<tr valign="top"><br />
<td>1233</td><td>IEEE Std 1233-1998 (R2002)</td><td>IEEE Guide for Developing System Requirements Specifications</td></tr><br />
<tr valign="top"><br />
<td>1362</td><td>IEEE Std 1362-1998 (R2007)</td><td>IEEE Guide for Information Technology-System Definition-Concept of Operations (ConOps) Document</td></tr><br />
<tr valign="top"><br />
<td>14143-1</td><td>ISO/IEC/IEEE14143-1</td><td>Implementation Note for IEEE Adoption of ISO/IEC<br />14143-1:2007 Information Technology &mdash; Software Measurement &mdash; Function Size Measurement Part I: Definition of Concepts</td></tr><br />
<tr valign="top"><br />
<td>15288</td><td>ISO/IEC/IEEE 15288(2008)</td><td>Systems and Software Engineering &mdash; System Life-cycle Processes</td></tr></table><br />
<h2>Short Descriptions of the Standards</h2><br />
<h3>IEEE Std 730-2002: Software Quality Assurance Plans</h3><br />
<p>'''Abstract:''' The standard specifies the format and content of software quality-assurance plans. It meets the IEEE/EIA 12207.1 requirements for such plans.</p><br />
<p>The SQA plan defines the means to ensure that software developed for a specific product satisfies the user’s requirements and is of the highest quality possible within project constraints. To do so, it must first ensure that the quality target is clearly defined and understood. It must consider management, development, and maintenance plans for the software. [[#Two|[2]]]</p><br />
<h3>IEEE Std 828-2005: Software Configuration Management</h3><br />
<p>'''Abstract:''' The minimum required contents of a software configuration management (SCM) plan are established via this standard. The application of this standard is not restricted to any form, class, or type of software. This standard applies to the entire life cycle of critical software (e.g., where failure would impact safety or cause large financial or social losses), as well as to noncritical software and to software already developed. A new version of this standard that defines the individual processes that make up software configuration management is currently underway, and expected to be published in 2010.</p><br />
<h3>IEEE Std 829-2008: Software and System Test Documentation</h3><br />
<p>'''Abstract:''' Test processes determine whether the development products of a given activity conform to the requirements of that activity and whether the system and software satisfies its intended use and user needs. Testing process tasks are specified for different integrity levels. These process tasks determine the appropriate breadth and depth of test documentation. The documentation elements for each type of test documentation can then be selected. The scope of testing encompasses software-based systems, computer software, hardware, and their interfaces. This standard applies to software-based systems being developed, maintained, or reused (legacy, commercial off-the-shelf, non-developmental items). The term “software” also includes firmware, microcode, and documentation. Test processes can include inspection, analysis, demonstration, verification, and validation of software and software-based system products.</p><br />
<h3>IEEE Std 830-1998: Software Requirements Specifications</h3><br />
<p>'''Abstract:''' The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. It is very useful for development teams to use as a checklist to remember all the different types of requirements (functional, derived, operational, quality, etc.) that must be provided to the development team.</p><br />
<h3>IEEE Std 1008-1987: Software Unit Testing</h3><br />
<p>Unit testing verifies the functioning in isolation of software pieces that are separately testable. Depending on the context, these could be the individual subprograms or a larger component made of tightly related units. A test unit is defined more precisely in the IEEE Standard for Software Unit Testing (IEEE1008-87), which also describes an integrated approach to systematic and documented unit testing. Typically, unit testing occurs with access to the code being tested and with the support of debugging tools, and might involve the programmers who wrote the code. [[#Three|[3]]] Test cases should be under the control of software configuration management and include the expected results for each test. [[#Four|[4]]]</p><br />
<p>Key aspects of test planning include coordination of personnel, management of available test facilities and equipment (which may include magnetic media, test plans, and procedures), and planning for possible undesirable outcomes. If more than one baseline of the software is being maintained, then a major planning consideration is the time and effort needed to ensure that the test environment is set to the proper configuration. [[#Five|[5]]]</p><br />
<h3>IEEE Std 1012-2004: System and Software Verification and Validation</h3><br />
<p>'''Abstract:''' Software verification and validation (V&V) processes determine whether the development products of a given activity conform to the requirements of that activity and whether the software satisfies its intended use and user needs. Software V&V life-cycle process requirements are specified for different software integrity levels. The scope of V&V processes encompasses software-based systems, computer software, hardware, and interfaces. This standard applies to software being developed, maintained, or reused (legacy, commercial off-the-shelf (COTS), non-developmental items). The term software also includes firmware, microcode, and documentation. Software V&V processes include analysis, evaluation, review, inspection, assessment, and testing of software products.</p><br />
<h3>IEEE Std 1016-2009: Software Design Descriptions</h3><br />
<p>'''Abstract:''' The necessary information content and recommendations for an organization for software design descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.</p><br />
<h3>IEEE Std 1028-2008: Software Reviews and Audits</h3><br />
<p>'''Abstract:''' Five types of software reviews and audits, together with procedures required for the execution of each type, are defined in this standard. This standard is concerned only with the reviews and audits; procedures for determining the necessity of a review or audit are not defined, and the disposition of the results of the review or audit is not specified. Types included are management reviews, technical reviews, inspections, walk-throughs, and audits. </p><br />
<h3>IEEE Std 1044-1993(R2002): Classification for Software Anomalies</h3><br />
<p>'''Abstract:''' A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life-cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly. </p><br />
<h3>IEEE Std 1058-1998: Software Project Management Plans</h3><br />
<p>'''Abstract:''' The format and contents of software project management plans, applicable to any type or size of software project, are described. The elements that should appear in all software project management plans are identified. This standard has recently been merged into ISO/IEC 16326.</p><br />
<h3>IEEE Std 1062-1998(R2002): Software Acquisition</h3><br />
<p>'''Abstract:''' This standard provides a set of useful quality practices for use during one or more steps in a software acquisition process. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.</p><br />
<h3>IEEE Std 1063-2001(R2007): Software User Documentation</h3><br />
<p>'''Abstract:''' This standard provides the minimum requirements for the structure, information content, and format of user documentation, including both printed and electronic documents used in the work environment by users of systems containing software. </p><br />
<h3>IEEE Std 1074-2006: Developing a Software Project Life-cycle Process</h3><br />
<p>'''Abstract:''' This standard provides a process for creating a software project life-cycle process (SPLCP). It is primarily directed at the process architect for a given software project. IEEE Std 1074-2006 is unique in that it provides activities for ensuring building in security throughout the software life cycle.</p><br />
<p>IEEE Std 1074 is a standard for establishing the process to be used in a software development, maintenance, or other type of software project, including disposal/withdrawal of the product. This standard requires selection of a user’s software project life-cycle model (SPLCM) based on the organization’s mission, vision, goals, and resources. EIT does not impose, define, or imply a particular software life-cycle model or methodology. This standard describes the individual activities that are to be used within the selected model and provides examples of mapping them onto typical SPLCMs. </p><br />
<p>This standard may also be used to develop organizational processes to support software development and maintenance or to develop special, single-function processes within a project.</p><br />
<h3>IEEE Std 1233-1998(R2002): Developing System Requirements Specifications</h3><br />
<p>'''Abstract:''' This standard provides guidance for the development of the set of requirements, system requirements specification (SyRS), to satisfy an expressed need. Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are the conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also covers the necessary characteristics and qualities of individual requirements and the set of all requirements.</p><br />
<h3>IEEE Std 1362-1998(R2007): Information Technology &mdash; System Definition &mdash; Concept of Operations (ConOps) Document</h3><br />
<p>'''Abstract:''' The format and contents of a concept of operations (ConOps) document are described. A ConOps is a user-oriented document that describes system characteristics for a proposed system from the users’ viewpoint. The ConOps document is used to communicate overall quantitative and qualitative system characteristics to the user, buyer, developer, and other organizational elements (for example, training, facilities, staffing, and maintenance). It is used to describe the user organizations, missions, and organizational objectives from an integrated systems point of view. </p><br />
<h3>IEEE Std 12207-2008: Systems and Software Engineering &mdash; Software Life-cycle Processes</h3><br />
<p>'''Abstract:''' This international standard establishes a common framework for software life-cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (system life-cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (process assessment). An annex provides support for IEEE users and describes relationships of this international standard to IEEE standards. </p><br />
<h3>IEEE Std 14143.1-2007: Information technology &mdash; software measurement &mdash; functional size measurement. Part 1: definition of concepts</h3><br />
<p>'''Abstract:''' This standard defines the concepts of functional size measurement (FSM). The concepts of FSM are designed to overcome the limitations of earlier methods of sizing software by shifting the focus away from measuring how the software is implemented to measuring size in terms of the functions required by the user. </p><br />
<h3>IEEE Std 14764-2006: Software Engineering &mdash; System Life-cycle Processes &mdash; Maintenance</h3><br />
<p>'''Abstract:''' The process for managing and executing software maintenance activities is described.</p><br />
<p>IEEE Std 14764:2006 describes in greater detail management of the maintenance process described in IEEE Std 12207, including amendments. It also establishes definitions for the various types of maintenance. IEEE Std 14764:2006 provides guidance that applies to planning, execution and control, review and evaluation, and closure of the maintenance process. The scope includes maintenance for multiple software products with the same maintenance resources. In IEEE Std 14764:2006, ''maintenance'' means software maintenance unless otherwise stated.</p><br />
<p>IEEE Std 14764:2006 provides the framework within which generic and specific software maintenance plans may be executed, evaluated, and tailored to the maintenance scope and magnitude of given software products. It provides the framework, precise terminology, and processes to allow the consistent application of technology (tools, techniques, and methods) to software maintenance.</p><br />
<p>IEEE Std 14764:2006 provides guidance for the maintenance of software. The basis for the maintenance process and its activities comes from the definitions of IEEE Std 12207. It defines the activities and tasks of software maintenance, and provides maintenance planning requirements. It does not address the operation of software and the operational functions, such as backup, recovery, and system administration, which are normally performed by those who operate the software.</p><br />
<p>IEEE Std 14764:2006 is written primarily for maintainers of software and additionally for those responsible for development and quality assurance. It may also be used by acquirers and users of systems containing software who may provide inputs to the maintenance plan. </p><br />
<h3>IEEE Std 15288-2008: Systems and Software Engineering &mdash; Software Life-cycle Processes</h3><br />
<p>'''Abstract:''' This international standard establishes a common process framework for describing the life cycle of man-made systems. It defines a set of processes and associated terminology for the full life cycle, including conception, development, production, utilization, support, and retirement. This standard also supports the definition, control, assessment, and improvement of these processes. These processes can be applied concurrently, iteratively, and recursively to a system and its elements throughout the life cycle of a system.</p><br />
<h3>The IEEE Software Engineering Body of Knowledge (SWEBOK)</h3><br />
<p>In this guide, the IEEE Computer Society establishes for the first time a baseline for the body of knowledge for the field of software engineering, and the work partially fulfills the Society’s responsibility to promote the advancement of both theory and practice in this field. In so doing, the Society has been guided by the experience of disciplines with longer histories but was not bound either by their problems or their solutions.</p><br />
<p>It should be noted that this guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the body of knowledge that has been developing and evolving over the past four decades. Furthermore, this body of knowledge is not static. The guide must, necessarily, develop and evolve as software engineering matures. Nevertheless, it constitutes a valuable element of the software engineering infrastructure. [[#Six|[6]]]</p><br />
<p>The purpose of the ''Guide to the Software Engineering Body of Knowledge'' is to provide a consensually validated characterization of the bounds of the software engineering discipline and to provide a topical access to the body of knowledge supporting that discipline. The body of knowledge is subdivided into ten software engineering knowledge areas (KAs) plus an additional chapter providing an overview of the KAs of strongly related disciplines. The descriptions of the KAs are designed to discriminate among the various important concepts, permitting readers to find their way quickly to subjects of interest. Upon finding a subject, readers are referred to key papers or book chapters selected because they succinctly present the knowledge.</p><br />
<p>This guide is oriented toward a variety of audiences, all over the world. It serves public and private organizations in need of a consistent view of software engineering for defining education and training requirements, classifying jobs, developing performance evaluation policies, or specifying software development tasks. It also addresses practicing, or managing, software engineers and the officials responsible for making public policy regarding licensing and professional guidelines. In addition, professional societies and educators defining the certification rules, accreditation policies for university curricula, and guidelines for professional practice benefit from SWEBOK, as well as the students learning the software engineering profession and educators and trainers engaged in defining curricula and course content. [[#Seven|[7]]]</p><br />
<h2>References</h2><br />
<div id="One"></div><p>[1] This set is available from IEEE on the ''Essentials'' CD. </p><br />
<div id="Two"></div><p>[2] Guide to SWEBOK 2004. 2.1.</p><br />
<div id="Three"></div><p>[3] Guide to SWEBOK 2004. 2.1.1.</p><br />
<div id="Four"></div><p>[4] Guide to SWEBOK 2004. 5.2.2.</p><br />
<div id="Five"></div><p>[5] Guide to SWEBOK 2004. 5.2.1.</p><br />
<div id="Six"></div><p>[6] Guide to SWEBOK 2004. Foreword.</p><br />
<div id="Seven"></div><p>[7] Guide to SWEBOK 2004. Preface.</p></div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=Standards&diff=195Standards2015-11-03T23:05:38Z<p>Daniel Robbins: Daniel Robbins moved page Standards to Key Standards</p>
<hr />
<div>#REDIRECT [[Key Standards]]</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=193MediaWiki:Sidebar2015-11-03T23:05:21Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition into Operation|11. Transition into Operation<br />
**Sustainment in Operation|12. Sustainment in Operation<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Related and Informing Disciplines|A. Related and Informing Disciplines<br />
**Glossary|B. Glossary<br />
**Structuring the Enterprise IT Organization|C. Structuring the Enterprise IT Organization<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=192MediaWiki:Sidebar2015-11-03T23:03:57Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition into Operation|11. Transition into Operation<br />
**Sustainment in Operation|12. Sustainment in Operation<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=191MediaWiki:Sidebar2015-11-03T23:02:36Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Preparedness|7. Disaster Recovery<br />
**Operations and Support|8. Operations and Support<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=Disaster_Preparedness&diff=189Disaster Preparedness2015-11-03T23:01:54Z<p>Daniel Robbins: Daniel Robbins moved page Disaster Recovery to Disaster Preparedness</p>
<hr />
<div><h2>Introduction</h2><br />
<p>Disaster preparedness and disaster recovery ([http://eitbokwiki.org/Glossary#dr DR]) supports business continuity planning and includes planning for [http://eitbokwiki.org/Glossary#eit EIT] resiliency, as well as recovery from adversity, such that critical business services affected are restored to a satisfactory working state within an [http://eitbokwiki.org/Glossary#acceptable acceptable] timeframe after the event. </p><br />
<p>[http://eitbokwiki.org/Glossary#dr DR] can be defined as “in computer system operations, the return to normal operation after a hardware or software failure.” [[#One|[1]]] Also, the “activities and programs designed to return the organization to an [http://eitbokwiki.org/Glossary#acceptable acceptable] condition. The ability to respond to an interruption in services by implementing a disaster recovery plan to restore an organization's critical business functions.” [[#Two|[2]]] </p><br />
<p>This section defines these processes and deliverables, and who should be responsible for planning, creating the documents, and communicating should a disaster occur. The following are some examples for context: </p><br />
<ul><br />
<li>'''Examples of disasters'''<br /><br />
<ul><br />
<li>Natural disaster affecting datacenters or EIT service operations (flood, fire, earthquake, wind)</li><br />
<li>Security breach resulting in disaster (destruction of data, admin password changes, virus/malware installation, sabotage)</li><br />
<li>Usage error (accidental deletion, unplug/turn off system resulting in corruption)</li><br />
<li>Utility failure affecting datacenters (loss of power even after UPS)</li><br />
<li>Vendor failure (cloud provider security failure, oil spill)</li><br />
<li>Staffing issue (employment dispute/walkout, epidemic)</li><br />
</ul><br />
<li>'''Examples of unpreparedness'''<br /><br />
<ul><br />
<li>Requiring use of computers or printers when power is out</li><br />
<li>Requiring use of internet when power or connectivity is out</li><br />
<li>Single point of knowledge/control for administration access</li><br />
<li>Lack of offsite backup storage</li><br />
<li>Lack of working restoration from backups</li><br />
<li>Lack of failover datacenters in separate locations</li><br />
<li>Undocumented or out of date documentation for system interfaces</li><br />
<li>Requiring use of phones that are out of power</li><br />
<li>Lack of designation of leaders in restoration efforts (who is in charge of restoring service and they know they are in charge)</li><br />
<li>In general, no cohesive, comprehensive EIT service restoration plan</li></ul></li></ul><br />
<h2>Goals and Principles</h2><br />
<p>EIT organizations are responsible for the following goals:</p><br />
<ul><br />
<li>To document and plan for appropriate backup and recovery processes for all systems, and priority of systems for restoration. </li><br />
<li>To create and deploy an EIT disaster recovery plan. </li><br />
<li>To ensure that the business has business continuity processes in place in case of a disaster.</li></ul><br />
<p>Fundamental principles of disaster recovery depends on the business functions within the enterprise, and how critical each is to the health of the business. There are several methods for determining criticality of functions. </p><br />
<ul><li>Hierarchy of need and stated in [http://eitbokwiki.org/Glossary#sla SLAs], which is that the most critical business functions should be restored first, or in the first phase of disaster recovery. </li><br />
<li>Keep the lights on ([http://eitbokwiki.org/Glossary#ktlo KTLO]) or keep the business running ([http://eitbokwiki.org/Glossary#ktbr KTBR]), which are not the same thing</li><br />
<li>All non-critical services are in the final phase of recovery.</li><br />
<li>Industry-specific, so all systems delivering lifesaving functions are the highest priority for recovery efforts, whereas administration systems wait for second or third wave of recovery. </li><br />
</ul><br />
<p>However, a fundamental recovery principle is that all systems to be recovered should be attended to within the specifications for recovery time objectives ([http://eitbokwiki.org/Glossary#rto RTO]) and recovery point objectives ([http://eitbokwiki.org/Glossary#rpo RPO]) laid out by the business in the DR plan.</p><br />
<h2>Context Diagram</h2><br />
[[File:ContextDiagram_DisasterRecovery.jpg]]<br />
<p>'''Figure 1. Context Diagram for Disaster Preparedness and Recovery'''</p><br />
<h3>Gather Inputs</h3><br />
<p>The following inputs are necessary for this process to initiate or continue:</p><br />
<ul><br />
<li>Budget for DR plan</li><br />
<li>Business risk factors/risk assessment</li><br />
<li>Business and EIT [http://eitbokwiki.org/Glossary#sla SLAs], [http://eitbokwiki.org/Glossary#ola OLAs], and contractual obligations to upstream/downstream systems</li><br />
<li>Business continuity plan</li><br />
<li>Configuration management database ([http://eitbokwiki.org/Glossary#cmdb CMDB]) and asset inventory (see the [http://eitbokwiki.org/Operations_and_Support Operations and Support chapter])</li><br />
<li>Current enterprise architecture artifacts/source code/document management systems</li><br />
<li>EIT [http://eitbokwiki.org/Glossary#service_cat service catalogue] </li><br />
<li>EIT staff capabilities</li><br />
<li>Vendor service agreements/maintenance agreements</li><br />
</ul><br />
<p>The obvious business driver is to reduce [http://eitbokwiki.org/Glossary#risk risk] for the business, by providing both mitigation strategies and contingency plans. High-risk projects or operational inefficiencies can lead to lost business, which ultimately causes lost income for the business &mdash; this can be the high price of risk.</p><br />
<p>Another business driver for formal DR processes may be to meet regulatory (i.e., [http://eitbokwiki.org/Glossary#sox SOX]) or sustainability objectives. Part of the information gathering includes conducting workshops or interviews to document the drivers to ensure deliverables meet these requirements.</p><br />
<p>Another related information-gathering effort is to define and document the technical drivers driving DR, including aging technology or lack of application support capabilities. </p><br />
<h2>Description of Activities</h2><br />
<h3>Business Impact Analysis</h3><br />
<h4>Define Critical Business Services</h4><br />
<p>With input from the business, such as the risk management group, the business continuity management, audit departments, and executives, define services critical to operations. Business impact analysis is a technique that can be used. Critical services are those that, if missing, the enterprise could no longer meet commitments and deliver business products or services. Use business process diagrams to assist with analysis. </p><br />
<p>The following list is a suggested structure for determining the ''service categories'' and corresponding criticality of organizations services (for definitions of the categories, refer to the [[#StandardServiceDefinitions|Standard Service Definitions]] section***where should ref go?***):</p><br />
<ul><br />
<li>Mission critical</li><br />
<li>Business critical</li><br />
<li>Business operational</li><br />
<li>Administrative services [[#Three|[3]]] </li> <br />
</ul><br />
<p>Examples of typical critical services within an enterprise are safety processes, safety documentation management, communication polices and processes, and financial data and processes.</p><br />
<h4>Map Critical Business Services to EIT Services</h4><br />
<p>This function is often referred to as ''building an EIT service catalog'', which is an important input to disaster recovery planning. A service catalog is “a database or structured document with information about all live EIT services, including those available for deployment…The service catalog includes information about deliverables, prices, contact points, ordering, and request processes.” [[#Four|[4]]] Templates exist to assist with this mapping. [[#Five|[5]]] See the [http://eitbokwiki.org/Operations_and_Support Operations and Support chapter] for more information on service catalogs.</p><br />
<h4>Define Relevant Disaster Scenarios and Responsible Parties</h4><br />
<p>Clearly define criteria for who declares a disaster, including when and how. Mature organizations have assigned responsible parties when disasters occur so that there is a clear leader determining which processes and procedures to implement during the disaster, and following the communication plan. Not having this in place allows for invalid assumptions about who is in charge, including no one taking ownership, or multiple parties competing for ownership, neither of which helps resolve the disaster and recover service.</p><br />
<h4>Define Successive Waves for Extending Recovery Across the Business</h4><br />
<p>Due to the complex nature of EIT systems within the enterprise today, it is unrealistic to provide recovery for all services in the initial recovery phase. There are different levels of recovery for different tiers of business services, and a corresponding, agreed-to timeframe for recovery of each service within the enterprise. These waves of recovery begin with the most critical services as defined, and move through to the least critical in a timeframe [http://eitbokwiki.org/Glossary#acceptable acceptable] based on a risk-mitigation process. For example, level one (i.e., Tier 1) recovery may take place within 72 hours of a disaster and would include services such as product production, shipping, and customer service applications. Note: A non-critical service may be recovered in the first pass of recovery based solely on a critical service having it as a dependency. </p><br />
<p>Critical systems management is a useful process in the identification and documentation of critical systems. [[#Six|[6]]] Also, it ensures proper application life-cycle management is occurring for these EIT services. [[#Seven|[7]]] </p><br />
<p>Use risk-assessment techniques to analyze how disaster scenarios could adversely affect the business. One such process would be to tier possible risks into levels such as:</p><br />
<ul><br />
<li>Affecting the entire enterprise</li><br />
<li>Affecting only certain business units</li><br />
<li>Affecting a single component (either a technology component or a business unit)</li><br />
<li>Affecting a single business function (such as processing credit card transactions)</li><br />
</ul><br />
<h3>Recovery Objectives and DR Plan</h3><br />
<h4>Determine Recovery Objectives and Develop Plan</h4><br />
<p>In cooperation with the business, define the recovery point objectives ([http://eitbokwiki.org/Glossary#rpo RPO]) and recovery time objectives ([http://eitbokwiki.org/Glossary#rto RTO]). </p><br />
<p>[http://eitbokwiki.org/Glossary#rpo RPO] is the point in time to which all integrated systems are recovered, taking into account backup schedules, sync points, and data transfer points to ensure data quality and integrity. </p><br />
<p>[http://eitbokwiki.org/Glossary#rto RTO] is how long it will take to return an EIT service to active duty. This varies depending on the criticality of the service as well as how integrated the service is with other services. </p><br />
<p>***add diagram***</p><br />
<p>Configuration management is a process that helps document the business impact of a service, as well as documenting the backup and recovery requirements. Also, it provides an inventory of applications and supporting infrastructure needed in the restoration processes.</p><br />
<p>'''Organization and Culture'''</p><br />
<p>The risk tolerance and depth of capabilities within the organization have a large impact on the disaster preparedness level within the organization. In other words, the business’s disaster tolerance is the “the time gap the business can accept the non-availability of EIT facilities.” [[#Two|[2]]] The lower the tolerance, the more extensive and costly DR practices and techniques are deployed. </p><br />
<p>Also, the business product deliveries determine the requirements of the planning effort and metrics. </p><br />
<h4>Develop Communications Plan</h4><br />
<p>An effective communication plan is an essential component to the successful implementation and adoption of the DR processes. The communication plan should include:</p><br />
<ul><br />
<li>How to deliver communications when standard communication systems are unavailable (such as email or phone systems)</li><br />
<li>Who to contact in a disaster situation, including specific lists for specific situations or systems affected</li><br />
<li>What the information each communication should include, and not include</li><br />
</ul><br />
<p>Contact information lists should include the following [http://eitbokwiki.org/Glossary#stakeholder stakeholders]:</p><br />
<ul><br />
<li>External partners (service providers and suppliers)</li><br />
<li>Police/fire/municipal departments</li><br />
<li>EIT management and staff</li><br />
<li>Business management and product owners</li><br />
</ul><br />
<p>The DR communication plan should describe the process to provide business updates to business continuity plans after the recovery has been completed.</p><br />
<p>A process for disaster declaration needs to be included in the DR plan and be well communicated to the team. In this section, all contact information and approval authority should be spelled out (i.e., who has the authority to declare a disaster within the company).</p><br />
<h4>Develop Backup and Archive Strategies and Schedule</h4><br />
<ul><br />
<li>The area of EIT responsible for DR is either responsible for backup and recovery or works closely with the team who is. Backup types such as archiving and incremental backups need to be scheduled for the varying needs of the systems being supported. Backup standards and recovery strategies should be defined to ensure the business requirements are met.</li><br />
<li>Backup and storage technology has a large role to play in the recoverability of applications and systems. Current backup utilities provide incremental forever-backup processes, which can help reduce the cost of storage used for holding backups. In addition, architecture features such as high-availability options and failover redundancies can both reduce risk of service loss, as well as provide mitigation strategies for unstable or unreliable systems. </li><br />
</ul><br />
<h4>Develop and Document DR Plan</h4><br />
<p>'''Disaster recovery plan ([http://eitbokwiki.org/Glossary#drp DRP])''' is “a set of human, physical, technical, and procedural resources to recover, within a defined time and cost, an activity interrupted by an emergency or disaster.” [[#Two|[2]]]</p><br />
<p>The DR plan document needs to include all of the information needed to recovery all critical systems a business needs to operate. EIT must work with the business to develop and document a DR plan. See the [[#Template|template at the end of this section]] for recommended sections of a DR plan.</p><br />
<p>Data collection techniques are critical to the development of a meaningful DR plan that meets the needs of the business. </p><br />
<h4>Interface with Business Continuity</h4><br />
<p>EIT must communicate their processes to the business, and make consistent updates to the business continuity plan ([http://eitbokwiki.org/Glossary#bcp BCP]). As the new business components or services are added, the business assigns a criticality level, which then needs to be translated into EIT services, that internally are assigned a tier to determine the disaster recovery requirements. This relationship between business continuity and EIT disaster recovery is a symbiotic relationship that is critical to the success of both functions within the enterprise.</p><br />
<h3>Implement and Test DR plan (Drill or Simulation)</h3><br />
<p>The first step to implementing a DR plan is to allocate resources and assign responsibilities. The DR team needs to be assigned early in the process to ensure accountability and understanding of roles at the time of a disaster. Many different roles are needed to define and execute a successful DR plan. The DR test is an opportunity to cross train in the many roles needed, in order to mitigate the risk of key roles not being available should a disaster occur. It is likely that no one from the business DR team will be available for the recovery of the systems, so documentation, testing, and assigning a strategic partner is important to the recovery of business services.</p><br />
<h4>Roles and Responsibilities</h4><br />
<p>Input supplier roles are roles and teams that supply the inputs to the process:</p><br />
<ul><br />
<li>Enterprise risk management team</li><br />
<li>BCP manager</li><br />
<li>EIT managers</li><br />
<li>Enterprise architecture team</li><br />
<li>Solution management team</li><br />
</ul><br />
<p>Key roles are the responsible individuals or teams that perform the process:</p><br />
<ul><li>DR team leads</li><br />
<li>Test team</li><br />
<li>Recovery center manager</li><br />
<li>System specialists (multiple)</li><br />
<li>Business management team<br /><br />
<ul><br />
<li>Facilities manager</li><br />
<li>Service manager</li><br />
</ul></li></ul><br />
<p>User roles expect and receive the deliverables:</p><br />
<ul><br />
<li>Operations management team<br /><br />
<ul><br />
<li>Backup process manager</li></ul></li><br />
<li>Test manager</li><br />
<li>Business management team</li><br />
</ul><br />
<p>Stakeholder roles are informed or consulted on the process execution:</p><br />
<ul><br />
<li>Enterprise risk management team</li><br />
<li>Operations management team<br /><br />
<ul><br />
<li>Business continuity manager</li></ul></li><br />
<li>Business management team<br /><br />
<ul><br />
<li>Contract manager</li></ul></li></ul><br />
<h4>Document Recovery Strategies</h4><br />
<p>As mentioned above, there are many strategies to recovery services the business needs to function. There is a different [http://eitbokwiki.org/Glossary#solution solution] for every different service out there. The most important element is to choose a strategy, then document and communicate it.</p><br />
<ul><br />
<li>Use a third-party hot recovery site. The hot site should be in a geographical separate location to ensure a natural disaster does not take out both the primary production location as well as the backup site location. These distances vary depending on geographic as well as infrastructure dependences (such as power, water, and network commonalities). </li><br />
<li>Real-time mirroring is a technique used to replicate data to a geographically separate location to ensure data is available should a restore processes be needed.</li><br />
<li>Manual, non-standard, or ad-hoc/on-demand/unscheduled procedures are also an important aspect that is a responsibility of the business units to ensure business continuity during the time EIT is rebuilding system services. Recommend to business management that manual processes either be automated, or have testing be completed on a regular basis. Also recommended is documenting methods used to mitigate problems caused by aging technology, such as having parts inventories, redundant or cold standby equipment.</li><br />
<li>Offsite archiving of data is a technique used to ensure backups are available should a disaster make the primary site unavailable. Offsite services are available through many service provides. Due diligence by the DR team is important to ensure the offsite facilities can guarantee secure and proper handling of backup data, an important enterprise asset.</li><br />
<li>Actions plans and recovery processes differ depending on what type of disaster has occurred. A single-component failure results in a standalone recovery of the failing component (i.e., application, server, or appliance). An enterprise-wide disaster results in a disaster declaration event with a full DR plan being executed with the full DR team being mobilized.</li><br />
<li>Identify and document potential disaster scenarios which have a high probability of happening to the business. For example, intrusion or denial of service attacks could have very adverse effects on a technology company, whereas adverse environment conditions create higher risks to a construction company. </li><br />
</ul><br />
<h4>Define a Schedule for Service Continuity Testing</h4><br />
<p>Defining a schedule for the disaster recovery testing is a critical factor to the success of a plan. One method often used is to simulate a disaster to test system recovery. Another process strongly recommended is to have production support test refreshes on a regular (i.e., monthly) basis. This not only ensures backups are usable, but also ensures processes are well documented and actually work, ensuring data quality and integration integrity. </p><br />
<h4>Implement and Test DR Plan (Drill or Simulation)</h4><br />
<ul><br />
<li>Implementation can take many forms. A hot site contract is an agreement with a third-party vendor to provide facilities and infrastructure needed to restore agreed to services in the timeframe specified. There are many variants to this type of contract depending on the dollar value of the [http://eitbokwiki.org/Glossary#contract contract] and the expected availability of internal staff at the time of a disaster. If the hot sites are geographically distant from the enterprise offices it is likely the contract includes staff to perform the recovery as well. </li><br />
<li>Due to the size and complexity of many enterprises, in-house DR facilities are often the norm, meaning these are secondary owned facilities used as recovery centers for primary facilities if needed.</li><br />
<li>A useful metric from testing processes is timing of actual recovery procedures as well as a measure of the capabilities of the DR team, third-party or secondary facilities, and the level of maturity of both staff knowledge and processes accuracy. </li><br />
</ul><br />
<h3>DR Plan &mdash; Change Management</h3><br />
<p>Regular verification and updates to backup processes is necessary to ensure accurate and usable backups are delivered. This change management process needs to provide updates to the documentation of the backup and recovery processes. For example:</p><br />
<ul><br />
<li>DR testing cycle changes as services change or risk tolerances change.</li><br />
<li>DR test results always cause process improvements and lessons learned to be added to the documentation.</li><br />
<li>Updates and changes to [http://eitbokwiki.org/Glossary#bcp BCP] go hand in hand with the changes to systems and services.</li><br />
</ul><br />
<p>Mature organizations build continual improvement evaluation and activities into all processes.</p><br />
<h4>Update DR Plan Based on DR Test Results and Validation</h4><br />
<p>Validation metrics are the measurements that quantify the success of processes, based on the requirements and goals of the business. The following measures can be used to determine the success of a DR test or simple restore procedure execution:</p><br />
<ul><br />
<li>Recovery point objectives met</li><br />
<li>Recovery time objectives met</li><br />
<li>Testing result measurements (for example, timing of restore, accuracy of data, and integration points)</li><br />
<li>Verification of backup usability</li><br />
</ul><br />
<h2>Summary</h2><br />
<p>Like most others, DR processes are a closed loop of plan > build > test > review with action. Continuous improvement and maturity of these processes are obtained through regular execution of DR tests, measuring results, and then revising the DR plan as necessary. Stakeholder involvement with setting requirements is critical to the success of DR processes. </p><br />
<h2>Important Skills</h2><br />
<ul><br />
<li>Change management</li><br />
<li>Enterprise and business architecture</li><br />
<li>Risk management</li><br />
<li>Configuration management</li><br />
<li>Testing and validation</li><br />
</ul><br />
<h2>Standards</h2><br />
<p>ISO/IEC 24765:2009 Systems and software engineering</p><br />
<h2>References &mdash; Bibliography</h2><br />
<div id="One"></div><p>[1] Systems and Software Engineering Vocabulary. (2009). ISO/IEC 24765 </p><br />
<div id="Two"></div><p>[2] ISACA. (n.d.). http://www.isaca.org/Pages/Glossary.aspx</p><br />
<div id="Three"></div><p>[3] ITIL Service Catalogue: How to produce a Service Catalogue; http://www.itilnews.com/ITIL_Service_Catalogue_How_to_produce_a_Service_Catalogue.html</p><br />
<div id="Four"></div><p>[4] “Introduction to the ITIL Service Lifecycle”, Second Edition, Office of Government Commerce, 2010</p><br />
<div id="Five"></div><p>[5] Dwight Kayto, “Defining IT Services”, Art of Change; http://www.artofchange.ca/images/documents/defining%20it%20services.pdf</p><br />
<div id="Six"></div><p>[6] British Computing Society, BCS “Delivery mission critical system,” 2011; http://www.bcs.org/content/conWebDoc/43139<br /><br />
http://www.downloads.xdelta.co.uk/2011/2011_07_19-bcs-mission_critical-colin_butcher.pdf</p><br />
<div id="Seven"></div><p>[7] Realtech, “Application Lifecycle Management,” Diagram;<br />
http://www.realtech.com/wInternational/software/solutions/application-lifecycle-management/application-lifecycle-managementW3DnavanchorW262110100.php</p><br />
<h2>Related and Informing Disciplines</h2><br />
<ul><br />
<li>Business continuity management</li><br />
<li>Application life cycle management</li><br />
<li>Risk management</li><br />
<li>Change management</li><br />
<li>Enterprise and business architecture</li><br />
<li>Configuration management</li><br />
<li>Testing and validation</li><br />
</ul><br />
<h2>Appendix</h2><br />
<div id="Template"></div><p>TEMPLATE for a disaster recovery plan</p><br />
<ol><li>Introduction<br /><br />
<ul><br />
<li>Scope of the plan</li><br />
<li>Objectives &mdash; RTO, RPO</li><br />
<li>Authority</li><br />
<li>Distribution</li><br />
<li>Disaster Declaration Process</li><br />
<li>Plan Review</li></ul></li><br />
<li>Recovery<br /><br />
<ul><br />
<li>Recovery Team</li><br />
<li>Recovery Plan</li><br />
<li>Disaster Preparation</li><br />
<li>Recovery Tasks (Short Term and Long Term)</li><br />
</ul></li><br />
<li>Backup<br /><br />
<ul><br />
<li>Backup Strategy for each Critical System</li><br />
</ul></li><br />
<li>Contact Information<br /><br />
<ul><br />
<li>Facilities Information</li><br />
<li>Recovery Team Information</li><br />
<li>Other Business Contact of Importance</li><br />
</ul></li></ol></div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=Disaster_Recovery&diff=190Disaster Recovery2015-11-03T23:01:54Z<p>Daniel Robbins: Daniel Robbins moved page Disaster Recovery to Disaster Preparedness</p>
<hr />
<div>#REDIRECT [[Disaster Preparedness]]</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=User_talk:Invicta&diff=40User talk:Invicta2015-08-20T22:28:44Z<p>Daniel Robbins: Welcome!</p>
<hr />
<div>'''Welcome to ''EITBOK''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:Daniel Robbins|Daniel Robbins]] ([[User talk:Daniel Robbins|talk]]) 22:28, 20 August 2015 (UTC)</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Vector.css&diff=38MediaWiki:Vector.css2015-08-13T22:54:28Z<p>Daniel Robbins: </p>
<hr />
<div>/* CSS placed here will affect users of the Vector skin */<br />
<br />
#left-navigation {<br />
margin-left: 260px;<br />
margin-bottom: 0px;<br />
}<br />
<br />
div#content, div#footer {<br />
margin-left: 260px;<br />
}<br />
<br />
div#mw-panel {<br />
width: 250px;<br />
}<br />
<br />
#p-logo a {<br />
width: 250px;<br />
}<br />
<br />
#footer {<br />
margin-left: 260px;<br />
}<br />
<br />
#mw-panel.collapsible-nav .portal {<br />
background-image: none;<br />
}<br />
<br />
#mw-panel.collapsible-nav .portal {<br />
margin: 0;<br />
}<br />
<br />
div#mw-panel div.portal h3#p-tb-label a {<br />
font-size: 11px;<br />
}<br />
<br />
.dtree {<br />
margin-bottom: 0.5em;<br />
}</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=User_talk:Drobbins.wikiworks&diff=37User talk:Drobbins.wikiworks2015-08-13T21:38:03Z<p>Daniel Robbins: Welcome!</p>
<hr />
<div>'''Welcome to ''EITBOK''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:Daniel Robbins|Daniel Robbins]] ([[User talk:Daniel Robbins|talk]]) 21:38, 13 August 2015 (UTC)</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=36MediaWiki:Sidebar2015-08-13T17:18:08Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=35MediaWiki:Sidebar2015-08-13T17:17:05Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
<br />
*Table of Contents<br />
*Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=34MediaWiki:Sidebar2015-08-13T17:16:43Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*QuickLinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
<br />
*Table of Contents|Table of Contents<br />
*Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=33MediaWiki:Sidebar2015-08-13T17:15:49Z<p>Daniel Robbins: </p>
<hr />
<div>*Test1<br />
*Test<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
<br />
<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=32MediaWiki:Sidebar2015-08-13T17:15:29Z<p>Daniel Robbins: </p>
<hr />
<div><br />
*Test<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
<br />
<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=31MediaWiki:Sidebar2015-08-13T17:13:43Z<p>Daniel Robbins: </p>
<hr />
<div>*Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=30MediaWiki:Sidebar2015-08-13T17:12:44Z<p>Daniel Robbins: </p>
<hr />
<div>* Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**Structuring the Enterprise IT Organization|A. Structuring the Enterprise IT Organization<br />
**Glossary|B. Glossary<br />
**Related and Informing Disciplines|C. Related and Informing Disciplines<br />
**Roles Matrix|D. Roles Matrix<br />
**Standards|E. Standards<br />
**Primary References|F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=29MediaWiki:Sidebar2015-08-13T17:11:46Z<p>Daniel Robbins: </p>
<hr />
<div>* Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**Requirements|8. Requirements<br />
**Acquisition|9. Acquisition<br />
**Construction|10. Construction<br />
**Transition|11. Transition<br />
**Sustainment|12. Sustainment<br />
**Operations and Support|13. Operations and Support<br />
**Retirements|14. Retirements<br />
<br />
*Appendices<br />
**A. Structuring the Enterprise IT Organization<br />
**B. Glossary<br />
**C. Related and Informing Disciplines<br />
**D. Roles Matrix<br />
**E. Standards<br />
**F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=28MediaWiki:Sidebar2015-08-13T17:10:37Z<p>Daniel Robbins: </p>
<hr />
<div>* Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
<br />
*Part 1: The Enterprise Perspective|Part 1: The Enterprise Perspective<br />
**Enterprise Architecture|1. Enterprise Architecture<br />
**Strategy and Governance|2. Strategy and Governance<br />
**Change Initiatives|3. Change Initiatives<br />
**Interoperability|4. Interoperability<br />
**Security|5. Security<br />
**Quality|6. Quality<br />
**Disaster Recovery|7. Disaster Recovery<br />
<br />
*Part 2. The Lifecycle Perspective<br />
**8. Requirements<br />
**9. Acquisition<br />
**10. Construction<br />
**11. Transition<br />
**12. Sustainment<br />
**13. Operations and Support<br />
**14. Retirements<br />
<br />
*Appendices<br />
**A. Structuring the Enterprise IT Organization<br />
**B. Glossary<br />
**C. Related and Informing Disciplines<br />
**D. Roles Matrix<br />
**E. Standards<br />
**F. Primary References<br />
<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=27MediaWiki:Sidebar2015-08-13T17:08:40Z<p>Daniel Robbins: </p>
<hr />
<div>* Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
*Outline<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT|Introduction to Enterprise IT<br />
**Part 1: The Enterprise Perspective|Part 1: The Enterprise Perspective<br />
***1. Enterprise Architecture|Enterprise Architecture<br />
***2. Strategy and Governance|Strategy and Governance<br />
***3. Change Initiatives|Change Initiatives<br />
***4. Interoperability|Interoperability<br />
***5. Security<br />
***6. Quality<br />
***7. Disaster Recovery<br />
**Part 2. The Lifecycle Perspective<br />
***8. Requirements<br />
***9. Acquisition<br />
***10. Construction<br />
***11. Transition<br />
***12. Sustainment<br />
***13. Operations and Support<br />
***14. Retirements<br />
**Appendices<br />
***A. Structuring the Enterprise IT Organization<br />
***B. Glossary<br />
***C. Related and Informing Disciplines<br />
***D. Roles Matrix<br />
***E. Standards<br />
***F. Primary References<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=26MediaWiki:Sidebar2015-08-13T17:07:47Z<p>Daniel Robbins: </p>
<hr />
<div>* Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
*Outline<br />
**Table of Contents|Table of Contents<br />
**Introduction to Enterprise IT<br />
**Part 1: The Enterprise Perspective<br />
***1. Enterprise Architecture<br />
***2. Strategy and Governance<br />
***3. Change Initiatives<br />
***4. Interoperability<br />
***5. Security<br />
***6. Quality<br />
***7. Disaster Recovery<br />
**Part 2. The Lifecycle Perspective<br />
***8. Requirements<br />
***9. Acquisition<br />
***10. Construction<br />
***11. Transition<br />
***12. Sustainment<br />
***13. Operations and Support<br />
***14. Retirements<br />
**Appendices<br />
***A. Structuring the Enterprise IT Organization<br />
***B. Glossary<br />
***C. Related and Informing Disciplines<br />
***D. Roles Matrix<br />
***E. Standards<br />
***F. Primary References<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=25MediaWiki:Sidebar2015-08-13T17:07:29Z<p>Daniel Robbins: </p>
<hr />
<div>* Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
*Outline<br />
**Table of Contents<br />
**Introduction to Enterprise IT<br />
**Part 1: The Enterprise Perspective<br />
***1. Enterprise Architecture<br />
***2. Strategy and Governance<br />
***3. Change Initiatives<br />
***4. Interoperability<br />
***5. Security<br />
***6. Quality<br />
***7. Disaster Recovery<br />
**Part 2. The Lifecycle Perspective<br />
***8. Requirements<br />
***9. Acquisition<br />
***10. Construction<br />
***11. Transition<br />
***12. Sustainment<br />
***13. Operations and Support<br />
***14. Retirements<br />
**Appendices<br />
***A. Structuring the Enterprise IT Organization<br />
***B. Glossary<br />
***C. Related and Informing Disciplines<br />
***D. Roles Matrix<br />
***E. Standards<br />
***F. Primary References<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=Table_of_Contents&diff=24Table of Contents2015-08-13T17:05:52Z<p>Daniel Robbins: Created page with "test"</p>
<hr />
<div>test</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=23MediaWiki:Sidebar2015-08-13T17:05:29Z<p>Daniel Robbins: </p>
<hr />
<div>* Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
*Outline<br />
**[[Table of Contents]]<br />
**[[Introduction to Enterprise IT]]<br />
**[[Part 1: The Enterprise Perspective]]<br />
***[[1. Enterprise Architecture]]<br />
***[[2. Strategy and Governance]]<br />
***[[3. Change Initiatives]]<br />
***[[4. Interoperability]]<br />
***[[5. Security]]<br />
***[[6. Quality]]<br />
***[[7. Disaster Recovery]]<br />
**[[Part 2. The Lifecycle Perspective]]<br />
***[[8. Requirements]]<br />
***[[9. Acquisition]]<br />
***[[10. Construction]]<br />
***[[11. Transition]]<br />
***[[12. Sustainment]]<br />
***[[13. Operations and Support]]<br />
***[[14. Retirements]]<br />
**[[Appendices]]<br />
***[[A. Structuring the Enterprise IT Organization]]<br />
***[[B. Glossary]]<br />
***[[C. Related and Informing Disciplines]]<br />
***[[D. Roles Matrix]]<br />
***[[E. Standards]]<br />
***[[F. Primary References]]<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=Outline&diff=22Outline2015-08-13T17:04:28Z<p>Daniel Robbins: Blanked the page</p>
<hr />
<div></div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=Outline&diff=21Outline2015-08-13T16:49:45Z<p>Daniel Robbins: </p>
<hr />
<div><div id="outline-tree"> <br />
{{#tree:root=Outline|<br />
*[[Table of Contents]]<br />
*[[Introduction to Enterprise IT]]<br />
*[[Part 1: The Enterprise Perspective]]<br />
**[[1. Enterprise Architecture]]<br />
**[[2. Strategy and Governance]]<br />
**[[3. Change Initiatives]]<br />
**[[4. Interoperability]]<br />
**[[5. Security]]<br />
**[[6. Quality]]<br />
**[[7. Disaster Recovery]]<br />
*[[Part 2. The Lifecycle Perspective]]<br />
**[[8. Requirements]]<br />
**[[9. Acquisition]]<br />
**[[10. Construction]]<br />
**[[11. Transition]]<br />
**[[12. Sustainment]]<br />
**[[13. Operations and Support]]<br />
**[[14. Retirements]]<br />
*[[Appendices]]<br />
**[[A. Structuring the Enterprise IT Organization]]<br />
**[[B. Glossary]]<br />
**[[C. Related and Informing Disciplines]]<br />
**[[D. Roles Matrix]]<br />
**[[E. Standards]]<br />
**[[F. Primary References]]<br />
}}</div></div>Daniel Robbinshttp://eitbokwiki.org/index.php?title=MediaWiki:Sidebar&diff=20MediaWiki:Sidebar2015-08-13T16:49:33Z<p>Daniel Robbins: </p>
<hr />
<div>* Quicklinks<br />
**Main Page|Main Page <br />
**BKCASE Governance and Editorial Board|BKCASE Governance and Editorial Board<br />
**Acknowledgements and Release History|Acknowledgements and Release History<br />
**How to Read the EITBoK|How to Read the EITBoK<br />
**Download EITBoK PDF|Download EITBoK PDF<br />
*Outline<br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Daniel Robbins