Be Advised: Classified, FOUO, and PII Content is Not Permitted

  • Replies 8 replies
  • Subscribers 461 subscribers
  • Views 38465 views
  • Users 0 members are here
Related

Requirements Management using MagicDraw

Felipe Arredondo

I am investigating MBSE to support system requirements. We have multiple baselines and I am currently investigating how or if it’s possible  to manage them within magicdraw. Just wondering anyone has attempted this and if it was successful how was it implemented.

Parents

  • Tim Weilkeins discusses variant modeling using custom stereotypes at https://mbse4u.com/2012/05/07/variant-modeling-with-sysml/. In characterizing an existing system with variants we have taken a similar approach using disjoint generalizations.

  • in reply to Robin Felix
    Robin
    I second Mike's point of keeping them in a separate model if possible. Especially if you have a large number of them.

    Also, NAVAIR is working with NAVWAR to develop a Requirements Profile for managing requirements in Magic Draw. It's still in development but they've made a ton of process over the last few months. I'd recommend reaching out to Barbara Lawson at barbara.d.lawson@navy.mil for more info. Not only is she developing this profile she's also a requirements expert and former DOORS instructor.
  • in reply to David Fields
    While not germane to the original question of requirements variants, it may be of interest to some that we are using Jama as our requirements manager, bringing the set of Jama requirements into a separate Cameo model as Mike suggests. The requirements model is then a project usage for traceability of requirements within the operational, functional, and system Cameo models.

    We have been using Syndeia now for a couple of years for that linkage, but Syndeia continues to lag behind its feature promises. Specifically, it is not enabling full exchange with Cameo of the relationships kept within Jama. As a result, we're investigating TaskTop as a more mature requirements integration tool between Jama and Cameo.
Reply
  • in reply to David Fields
    While not germane to the original question of requirements variants, it may be of interest to some that we are using Jama as our requirements manager, bringing the set of Jama requirements into a separate Cameo model as Mike suggests. The requirements model is then a project usage for traceability of requirements within the operational, functional, and system Cameo models.

    We have been using Syndeia now for a couple of years for that linkage, but Syndeia continues to lag behind its feature promises. Specifically, it is not enabling full exchange with Cameo of the relationships kept within Jama. As a result, we're investigating TaskTop as a more mature requirements integration tool between Jama and Cameo.
Children
No Data