This document regulates how changes are made to Chemwatch software products. The process applies for the changes bigger than 3 days in size, as well as changes having significant user impact and risks related to releasing them to the public.
...
Change authority is a person or a group of people responsible for authorizing a change.
| Position | Level of authorization |
|---|---|
| CEO | Ultimate change authority. |
| Stakeholdes | Can pre-approve a change, but require CEO's review and sign off. |
| Everyone else | Can suggest a change. |
Benefit and risk analysis
...
- Benefits
- Risks and opportunities, including security risks
- Impact on existing clients
- Impact on future clients
- Changes required to the operation procedures
...
| Info |
|---|
For some parts, a change cannot be made until the form and date of it is agreed on by the client. Check Supporting Documents section for more information |
Production Environment Change Control
Production change is usually an ad-hoc process, depending on what change is planned. For example, Database upgrade procedure and corresponding risk assesment may be quite different from upgrading OS or .NET version. In any case, each upgrade (change) to the environment happens in these steps:
- Risk assessment / mitigaiton plans.
- Implementing change on Dev / then test.
- Implementing change on Staging / then test.
- Only if tests passed and risks mitigated the change does to production.
Supporting documents
- Customization analysis and approval flow - covers the details of the process how to deal about outstanding changes required by a client.
...