Requirements Management using MagicDraw

It really depends upon the magnitude of the scope -- how big is the model? how many requirements? how many baselines are you attempting to manage utilizing MagicDraw?

Either way, there a various pros and cons to either option -- Managing Requirements Directly within the System Model vs. Managing Requirements in a Large Model Split into Modules. I think the requirements sync goes a bit smoother if you elect to manage requirements in a larger model that's split into various modules (conceptual, logical, physical, etc). Having the requirements in a separate project but linked to the architecture allows you to manage versioning/baselines better without disturbing the holistic model in the event you need to revert changes. Not to mention, it should not prevent you or your team from working while conducting simultaneous syncs.

It really depends upon the magnitude of the scope -- how big is the model? how many requirements? how many baselines are you attempting to manage utilizing MagicDraw?

Either way, there a various pros and cons to either option -- Managing Requirements Directly within the System Model vs. Managing Requirements in a Large Model Split into Modules. I think the requirements sync goes a bit smoother if you elect to manage requirements in a larger model that's split into various modules (conceptual, logical, physical, etc). Having the requirements in a separate project but linked to the architecture allows you to manage versioning/baselines better without disturbing the holistic model in the event you need to revert changes. Not to mention, it should not prevent you or your team from working while conducting simultaneous syncs.

Thank You, My project is extremely large. We have 4 levels of requirements, which change or are updated on different schedules, that's a mess in and of itself. Currently we are just working on how to tackle this. We are currently investigating creating each Requirement level in a separate model, and then using the share project option to import model into the main model, that's easy part. It get more complicated when we start linking requirements.In any event we have just begun investigating this topic. I've been working something similar however it is a much smaller scale and not as complicated. In this model we only have two baselines however we have requirement traced/relationships (in some fashion) to source (higher level requirements), test events, risk, functions, systems, Baselines. Through these relationships we were able to create a Test Evaluation Matrix which is very powerful. We've also been able to produce project documents using scripts and macros.

I've received some good information, please keep posting your thoughts, it will assist everyone.