Book a Demo

Author Topic: Auto Packages from Requirements?  (Read 3426 times)

wstidolph

  • EA Novice
  • *
  • Posts: 15
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Auto Packages from Requirements?
« on: March 24, 2013, 05:41:11 am »
I have a tree of mixed Packages and Requirements (a Package can contain Packages and/or leaf Requirements). Many of the leaf Requirements are very poorly written and need decomposition and I'm wondering what's the most efficient methods of dealing with getting individual Requirements I can allocate/test/trace to classes and components.

One thought I've played with this morning is to create a transformed tree with all the original Packages and diagrams:

For each Requirement
   * create Package with same name and notes as the Requirement, in the tree where the Requirement was
   * move the Requirement into the Package, appending "_0" to its name

Then I go through the new Packages, copying the existing Requirement_0 and making _1, _2, etc that are aggregation parts of the _0; then the _1, _2... are what I'll allocate/test/trace at the Class/Component level.

This is really awkward manually (opening and closing lots of elements and such) so I'm wondering about how to automate it. I feel like this might yield to a "MDA Transform" solution, but that's new to me and I don't see a lot of tutorials ... so I'm wondering if anyone has already done/seen something like this.

(Another very useful script-ish thing would be some way to clone a Requirement into N copies with names suffixed "_1", ..., _<N> all aggregation-linked to the _0. Perhaps N could be a fixed attribute I set while reviewing the _0 Requirements ... is there already a way to do this, or do I need to write/invoke a bit of script?)

[edit - fixed typo]
« Last Edit: March 24, 2013, 12:51:22 pm by wstidolph »

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Auto Packages from Requirements?
« Reply #1 on: March 24, 2013, 09:44:36 am »
A transformation sounds reasonable. You can indeed (quite easily) create a transformation which creates a copy. But once you launched it the source and target package are internally connected via the transform script. That means that if you want to create multiple copies you have to create a single transform script for each. Not too hard, but it might feel strange. Creating a copy via scripting is definitely a bit harder since the learning curve is a bit steeper. But once you mastered that you'll have a great tool at hand for various purposes.

q.