recently it is explained in this forum

Change control and configuration work most of time hand by hand. CC comes whenever I have a change in project and config mgt comes when these approved cc making a change in my configuration item. So for example there is project to make a a vehicle like I-road. It will have engine,design,turning steering,tyres etc etc. now let start our configuration mgt. first I want to see which are all parts that I need to consider for configuration or ( you can versioning) ..and let we consider engine,design and turning steering. Once I know these are my item I also look for their specifications ..for ex engine need 700 hp,metal used say copper ,etc etc.,same will do for design and turning steering - the process I just finished is identification. Now let us consider that during testing it was found that engine HP is at least need 750. So a change control came to change engine HP to 750. You made the changes in all the project documents and also updated configuration item engine to reflect HP as 750.

now for communication purpose or some asked , can I get latest specifications for all the items.So you will share specifications for all items ..and definitely your engine item will show 750hp. This process of giving latest or any older version (i means ppl can also ask old version of engine and that will still show 700hp)of item's specification is status accounting.

now you one I-road is made,and you want to audit it so that it uses latest specifications ..I mean this should show engine hp750. This is verification and audit.

all the above story is configuration mgt.

I hope it will help.

forgot to mention I-road is toyota's patent word :)