Enabling Processes

Recommendations

Info

Build, Acquire and Implement 138 : ENABLING PROCESSES BAI03 Process Practices, Inputs/Outputs and Activities (cont.) Management Practice Inputs Outputs BAI03.08 Execute solution testing. Execute testing continually during development, including control testing, in accordance with the defined test plan and development practices in the appropriate environment. Engage business process owners and end users in the test team. Identify, log and prioritise errors and issues identified during testing. From Description Description To APO04.05 �� initiatives Test result logs and audit trails Test result communications BAI07.03 BAI07.03 Activities 1. Undertake testing of solutions and their components in accordance with the testing plan. Include testers independent from the solution team, with representative business process owners and end users. Ensure that testing is conducted only within the development and test environments. 2. Use clearly defined test instructions, as defined in the test plan, and consider the appropriate balance between automated scripted tests and interactive user testing. 3. Undertake all tests in accordance with the test plan and practices including the integration of business processes and IT solution components and of non-functional requirements (e.g., security, interoperability, usability). 4. Identify, log and classify (e.g., minor, significant and mission-critical) errors during testing. Repeat tests until all significant errors have been resolved. Ensure that an audit trail of test results is maintained. 5. Record testing outcomes and communicate results of testing to stakeholders in accordance with the test plan. Management Practice Inputs Outputs BAI03.09 Manage changes to requirements. From Description Description To Track the status of individual requirements (including all APO04.05 Results and Record of all approved and BAI06.03 �� recommendations from applied change requests and manage the approval of changes to requirements. proof-of-concept initiatives BAI02.01 Record of requirement change requests Activities 1. Assess the impact of all solution change requests on the solution development, the original business case and the budget, and categorise and prioritise them accordingly. 2. Track changes to requirements, enabling all stakeholders to monitor, review and approve the changes. Ensure that the outcomes of the change �� Management Practice Inputs Outputs BAI03.10 Maintain solutions. Develop and execute a plan for the maintenance of solution and infrastructure components. Include periodic reviews against business needs and operational requirements. From Description Description To Maintenance plan APO08.05 Updated solution components and related documentation BAI05.05 Activities 1. Develop and execute a plan for the maintenance of solution components that includes periodic reviews against business needs and operational requirements such as patch management, upgrade strategies, risk, vulnerabilities assessment and security requirements. �� impact and resource availability. Ensure that the business process owners understand the effect of designating changes as maintenance. �� follow the development process used for new systems. For maintenance updates, use the change management process. 4. Ensure that the pattern and volume of maintenance activities are analysed periodically for abnormal trends indicating underlying quality or �� 5. For maintenance updates, use the change management process to control all maintenance requests. Personal Copy of: Mr. Dong Hong Wang
BAI03 Process Practices, Inputs/Outputs and Activities (cont.) CHAPTER 5 COBIT 5 PROCESS REFERENCE GUIDE CONTENTS Management Practice Inputs Outputs BAI03.11 Define IT services and maintain the service portfolio. Define and agree on new or changed IT services and service level options. Document new or changed service definitions and service level options to be updated in the services portfolio. From Description Description To EDM04.01 Guiding principles for allocation of resources and capabilities APO02.04 � �� for target environment � �� required to realise target capability Service definitions APO05.01 DSS01.03 Updated service portfolio APO05.05 APO06.02 Budget allocations APO06.03 � �� APO08.05 Definition of potential �� BAI10.02 Configuration baseline BAI10.03 Approved changes to baseline BAI10.04 Configuration status reports Activities 1. Propose definitions of the new or changed IT services to ensure that the services are fit for purpose. Document the proposed service definitions in the portfolio list of services to be developed. 2. Propose new or changed service level options (service times, user satisfaction, availability, performance, capacity, security, continuity, compliance and usability) to ensure that the IT services are fit for use. Document the proposed service options in the portfolio. 3. Interface with business relationship management and portfolio management to agree on the proposed service definitions and service level options. 4. If service change falls within agreed-on approval authority, build the new or changed IT services or service level options. Otherwise, pass the service change to portfolio management for investment review. BAI03 Related Guidance Related Standard Detailed Reference �� Personal Copy of: Mr. Dong Hong Wang 139 Build, Acquire and Implement
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:
Page 17 and 18:
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 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
EDM02 Process Practices, Inputs/Out
Page 39 and 40:
Page 41 and 42:
EDM03 Process Practices, Inputs/Out
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
APO01 Process Practices, Inputs/Out
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
APO04 Manage Innovation (cont.) CHA
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88: APO07 Process Practices, Inputs/Out
Page 89 and 90: CHAPTER 5 COBIT 5 PROCESS REFERENCE
Page 113 and 114: APO13 Manage Security Process Descr
Page 123 and 124: BAI01 Process Practices, Inputs/Out
Page 137: CHAPTER 5 COBIT 5 PROCESS REFERENCE
Page 179 and 180: DSS02 Process Practices, Inputs/Out
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?