Requirements Management using MagicDraw

For something like this, I would suggest that keeping the requirements in their own, separate model is the best option. That way, the main system models can use whatever version is appropriate. So when a new baseline is available, simply "point" the other models at the new version.
Note that TeamWork Cloud supports branching, merging, and other management techniques that would support this effort

Now I'm going to ask the challenging question: Why not update the requirements instantly? Let's leverage the power of our tools and see things now rather than later. Example: physical requirement for length changes. Model automatically detects that our length value exceeds the limit. I can start fixing that NOW instead of not knowing until the next approved baseline is released.

For something like this, I would suggest that keeping the requirements in their own, separate model is the best option. That way, the main system models can use whatever version is appropriate. So when a new baseline is available, simply "point" the other models at the new version.
Note that TeamWork Cloud supports branching, merging, and other management techniques that would support this effort

Now I'm going to ask the challenging question: Why not update the requirements instantly? Let's leverage the power of our tools and see things now rather than later. Example: physical requirement for length changes. Model automatically detects that our length value exceeds the limit. I can start fixing that NOW instead of not knowing until the next approved baseline is released.