Change management, and keeping track of versions is always a wider discussion, there are several approaches, however we have seen good success for most architecture practices with the inbuilt baselines and RAS. Except for firms working on Code generation from models (where you need a GIT or SVN), this has always worked. I did a video (quite basic) to show how to use Baselines and RAS in 15.1 (over a shared repository)The video
deosn't have a voice, i did my talk and used this during my presentation, however has some captions to help you understand (Baselines and RAS on shared repositories)
Yes, and I change the status as Implelemted. This is path to find out what was the reason of change. Now you can see actual model of working software, and all changes that are made upon the live of application. All of course is well categorised and each part has his own place.