Book a Demo

Author Topic: allocated requirement not in relationship matrix  (Read 3423 times)

Peter @ BRACE

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
allocated requirement not in relationship matrix
« on: January 18, 2012, 12:22:14 am »
I use the relationship matrix to analyse which requirements I have allocated to which activities. But when changing the type of requirement to 'allocated' (according SysML) it is not identified in the relationship matrix anymore.

Possible cause could be the capital 'A' where SysML plugin uses lower case.

(EA 9.2, SysML MDG technologies: version 1.0)


rocketman

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: allocated requirement not in relationship matr
« Reply #1 on: January 21, 2012, 06:39:55 am »
Peter,

My understanding of the relationship matrix is that you can only matrix one type of object to one type of object with one type of relationship (at any given time).  That is to say, the relationships that exist in the model between TWO TYPES of objects.

Requirements would be one type of object, activities would be one type of object.  I assume the matrix you have created shows the relationships that exist between requirements and activities.  When you change the type from requirement to allocated, it is not longer one of the two types in the matrix.  You could create a separate matrix to show the relationships that exist between allocated and activities.

Alternatively, you could keep the type as requirement and just label the association as allocated.

Peter @ BRACE

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: allocated requirement not in relationship matr
« Reply #2 on: January 25, 2012, 02:03:26 am »
I agree but if I change the matrix to find 'Allocated' objects (since 'allocated' is not available in the pull-down menu) to 'Activity' objects it does not give any results. If I set the matrix to 'all' it does show both requirements and 'allocated' objects.