Difference between revisions of "ISO:Change Reporting\Handling\Planning and Management"
Jump to navigation
Jump to search
(Created page with "==Change management== Changes are logged in Hornbill Technologies’ own Hornbill instance . The originator obtains sufficient information to complete the Change Request for...") |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | This document can now be found at its new location in the [https://docs.hornbill.com/hornbill-cloud/iso/change-reporting-handling-planning-and-management/ Hornbill Document Library]. | ||
| + | |||
| + | [[file:hornbill-document-library.png|Hornbill Cloud|link=https://docs.hornbill.com/hornbill-cloud/iso/change-reporting-handling-planning-and-management/]] | ||
| + | |||
| + | <!-- | ||
==Change management== | ==Change management== | ||
Changes are logged in Hornbill Technologies’ own Hornbill instance . The originator obtains sufficient information to complete the Change Request form and obtains the Chief Technical Officer’s or Cloud Service Manager’s approval for the change, taking into account any technical considerations, the costs of the exercise, the potential benefits, etc. | Changes are logged in Hornbill Technologies’ own Hornbill instance . The originator obtains sufficient information to complete the Change Request form and obtains the Chief Technical Officer’s or Cloud Service Manager’s approval for the change, taking into account any technical considerations, the costs of the exercise, the potential benefits, etc. | ||
| + | |||
Copies of all change requests are retained to provide an audit trail. | Copies of all change requests are retained to provide an audit trail. | ||
| + | |||
The Cloud service Manager is then responsible for reviewing and/or carrying out a risk assessment to identify potential risks, their impacts and then to identify and cost the required controls in line with Hornbill Technologies’ risk management framework. | The Cloud service Manager is then responsible for reviewing and/or carrying out a risk assessment to identify potential risks, their impacts and then to identify and cost the required controls in line with Hornbill Technologies’ risk management framework. | ||
| Line 14: | Line 21: | ||
==Test, development and operational facilities== | ==Test, development and operational facilities== | ||
All testing is conducted in a test environment which is configured for that specific test requirement. It is separated from operational facilities by logical means and requires a password for access, which is issued by the Cloud Team. | All testing is conducted in a test environment which is configured for that specific test requirement. It is separated from operational facilities by logical means and requires a password for access, which is issued by the Cloud Team. | ||
| + | |||
| + | All testing for core platform changes is performed in Dev\BETA environments with https://wiki.hornbill.com/index.php/Continuous_Delivery being used to ensure problems are found\rectified before Live. | ||
| + | |||
| + | No data from live is ever used for testing and all test data used by developers is pseduo-generated. | ||
| + | --> | ||
| + | [[Category:HDOC]] | ||
| + | <!-- /hornbill-cloud/iso/change-reporting-handling-planning-and-management --> | ||
Latest revision as of 17:36, 11 September 2023
This document can now be found at its new location in the Hornbill Document Library.
