Change Control Forms Post Software Validation

[CerysC]

Hi All
I just need advice on the following question
Do you need to create documentation such as change control request form to document that updates were made to specifications such as User Requirements , Functional specifications etc post validation.
I had always thought that change request forms were only applicable to the computer system themselves and that any changes to the specifications are recorded in the revision history of the document ?
However if changes had to be made to specifications post validation should an impact assessment be performed on a change control form to document these changes ?
Hope my question makes sense ! Any advice at all would be greatly appreciated

 

[yodon]

The important thing is that you control the changes. Part of control would be, in fact, assessing (and documenting) the impact of the change. Change control means that only the things that are authorized to be changed actually do get changed. Often, software developers like to make other changes when they get in. The change authorization needs to track to specific changes and you should be able to compare code differences before / after the change to confirm that only the authorized changes were made. So without that documented assessment, you quite possibly lose control.

Whether you record this on a form is your choice. Most often, there is some kind of form involved - whether a paper- or electronic-based. Forms just help guide the process.

 

[CerysC]

Thank you very much Yodon !!