Enabling Processes

Recommendations

Info

Align, Plan and Organise 66 : ENABLING PROCESSES APO03 Process Practices, Inputs/Outputs and Activities (cont.) APO03.02 Activities 1. Maintain an architecture repository containing standards, reusable components, modelling artefacts, relationships, dependencies and views to enable uniformity of architectural organisation and maintenance. 2. Select reference viewpoints from the architecture repository that will enable the architect to demonstrate how stakeholder concerns are being addressed in the architecture. 3. For each viewpoint, select the models needed to support the specific view required, using selected tools or methods and the appropriate level of decomposition. 4. Develop baseline architectural domain descriptions, using the scope and level of detail necessary to support the target architecture and, to the extent possible, identifying relevant architecture building blocks from the architecture repository. 5. Maintain a process architecture model as part of the baseline and target domain descriptions. Standardise the descriptions and documentation of processes. Define the roles and responsibilities of the process decision makers, process owner, process users, process team and any other process stakeholders who should be involved. �� optimal use of information for decision making. Maintain an enterprise data dictionary that promotes a common understanding and a classification scheme that includes details about data ownership, definition of appropriate security levels, and data retention and destruction requirements. �� and define new or modified components that must be developed for the target architecture. Resolve potential impacts such as incompatibilities, inconsistencies or conflicts within the envisioned architecture. �� statement of architecture work. 9. Finalise business, information, data, applications and technology domain architectures, and create an architecture definition document. Management Practice Inputs Outputs APO03.03 Select opportunities and solutions. From Description Description To Rationalise the gaps between baseline and target APO02.03 Proposed enterprise High-level implementation APO02.05 architectures, taking both business and technical architecture changes and migration strategy �� Outside COBIT � �� Transition architectures APO02.05 IT-enabled investment programmes to ensure that the � �� architectural initiatives are aligned with and enable these initiatives as part of overall enterprise change. Make this a collaborative effort with key enterprise stakeholders from business and IT to assess �� identify opportunities, solutions and all implementation constraints. Activities �� 2. Identify any enterprise drivers that would constrain the sequence of implementation, including a review of the enterprise and line of business strategic and business plans, and consideration of the current enterprise architecture maturity. 3. Review and consolidate the gap analysis results between the baseline and target architectures and assess their implications with respect to potential �� 4. Assess the requirements, gaps, solutions and factors to identify a minimal set of functional requirements whose integration into work packages would lead to a more efficient and effective implementation of the target architecture. 5. Reconcile the consolidated requirements with potential solutions. 6. Refine the initial dependencies, ensuring that any constraints on the implementation and migration plans are identified, and consolidate them into a dependency analysis report. �� 8. Formulate a high-level implementation and migration strategy that will guide the target architecture implementation and structure the transition �� and approach. 10. Develop a series of transition architectures as necessary where the scope of change required to realise the target architecture requires an incremental approach. Personal Copy of: Mr. Dong Hong Wang
CHAPTER 5 COBIT 5 PROCESS REFERENCE GUIDE CONTENTS APO03 Process Practices, Inputs/Outputs and Activities (cont.) Management Practice Inputs Outputs APO03.04 Define architecture implementation. From Description Description To Create a viable implementation and migration plan in �� Resource requirements BAI01.02 Ensure that the plan is closely co-ordinated to ensure Implementation phase BAI01.01 that value is delivered and the required resources are descriptions BAI01.02 available to complete the necessary work. Architecture governance requirements BAI01.01 Activities �� requirements of applicable decision makers. 2. Confirm transition architecture increments and phases and update the architecture definition document. 3. Define architecture implementation governance requirements. Management Practice Inputs Outputs APO03.05 Provide enterprise architecture services. From Description Description To The provision of enterprise architecture services within the enterprise includes guidance to and monitoring �� working through architecture contracts, and measuring �� compliance monitoring. Solution development guidance BAI02.01 BAI02.02 BAI03.02 Activities 1. Confirm scope and priorities and provide guidance for solution development and deployment. �� 3. Manage enterprise architecture requirements and support with architectural principles, models and building blocks. 4. Identify and align enterprise architecture priorities to value drivers. Define and collect value metrics and measure and communicate enterprise architecture value. �� with these standards and guidelines, including compliance with external requirements and their business relevance. APO03 Related Guidance Related Standard Detailed Reference TOGAF 9 At the core of TOGAF is the Architecture Development Method (ADM), which maps to the COBIT 5 practices of developing an architecture vision (ADM Phase A), defining reference architectures (ADM Phases B,C,D), selecting opportunities and solutions (ADM Phase E), and defining architecture implementation (ADM Phases F, G). A number of TOGAF components map to the COBIT 5 practice of providing enterprise architecture services. These include ADM Requirements Management, Architecture Principles, Stakeholder Management, Business Transformation Readiness Assessment, Risk Management, Capability-Based Planning, Architecture Compliance and Architecture Contracts. Personal Copy of: Mr. Dong Hong Wang 67 Align, Plan and Organise
Page 1 and 2:
Enabling Processes Personal Copy of
Page 3 and 4:
ACKNOWLEDGEMENTS ISACA wishes to re
Page 5 and 6:
ACKNOWLEDGEMENTS (CONT.) ACKNOWLEDG
Page 7 and 8:
TABLE OF CONTENTS TABLE OF CONTENTS
Page 9 and 10:
LIST OF FIGURES LIST OF FIGURES Fig
Page 11 and 12:
CHAPTER 1 INTRODUCTION CHAPTER 1 IN
Page 13 and 14:
CHAPTER 2. THE GOALS CASCADE AND ME
Page 15 and 16: CHAPTER 2. THE GOALS CASCADE AND ME
Page 17 and 18: CHAPTER 2. THE GOALS CASCADE AND ME
Page 19 and 20: CHAPTER 3 THE COBIT 5 PROCESS MODEL
Page 21 and 22: Enabler Performance Management CHAP
Page 23 and 24: CHAPTER 4 THE COBIT 5 PROCESS REFER
Page 25 and 26: CHAPTER 5 COBIT 5 PROCESS REFERENCE
Page 27 and 28: Generic Guidance for Processes CHAP
Page 37 and 38: EDM02 Process Practices, Inputs/Out
Page 41 and 42: EDM03 Process Practices, Inputs/Out
Page 55 and 56: APO01 Process Practices, Inputs/Out
Page 65: CHAPTER 5 COBIT 5 PROCESS REFERENCE
Page 71 and 72: APO04 Manage Innovation (cont.) CHA
Page 113 and 114: APO13 Manage Security Process Descr
Page 117 and 118:
CHAPTER 5 COBIT 5 PROCESS REFERENCE
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
BAI01 Process Practices, Inputs/Out
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
DSS02 Process Practices, Inputs/Out
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
DSS05 Process Practices, Inputs/Out
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
MEA01 Process Practices, Inputs/Out
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
APPENDIX A MAPPING BETWEEN COBIT 5
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
APPENDIX B DETAILED MAPPING ENTERPR
Page 227 and 228:
APPENDIX C DETAILED MAPPING IT-RELA
Page 229 and 230:
Deliver, Service and Support Monito
show all

Enabling Processes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?