Book a Demo

Author Topic: Relationship Matrix - Requirements order  (Read 2933 times)

sdh

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Relationship Matrix - Requirements order
« on: July 05, 2013, 05:31:56 pm »
Hi,

In the relationship matrix, the requirements are not listed in the way they are in the package. They are somehow sorted (I have the doors identifier: requirement text in the name field, and they get seorted by the object identifier). Is there some way to see the requirements as they are stuructured in the package.

Helmut Ortmann

  • EA User
  • **
  • Posts: 970
  • Karma: +42/-1
    • View Profile
Re: Relationship Matrix - Requirements order
« Reply #1 on: July 05, 2013, 07:29:01 pm »
Hi,

the Relationship Matrix orders the elements in alphabetic order (name, short description).

If you want a different order you may use Model Searches. In your own Search you can cope with
  • nested elements
  • order stored in EA (TreePos)
  • different properties of requirements (alias, ..)
 
as you like it.

Helmut Ortmann
Coaching, Training, Workshop (Addins: hoTools, Search&Replace, LineStyle)

sdh

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Relationship Matrix - Requirements order
« Reply #2 on: July 05, 2013, 07:43:17 pm »
Can you give me some pointers on how to do this.

Helmut Ortmann

  • EA User
  • **
  • Posts: 970
  • Karma: +42/-1
    • View Profile
Re: Relationship Matrix - Requirements order
« Reply #3 on: July 05, 2013, 08:17:28 pm »
Hi,

1. Create your SQL Query
Select all elements of package with a given GUID of the package.
Code: [Select]
select o.ea_guid AS CLASSGUID, o.object_type AS CLASSTYPE, o.Name, o.object_Type As Type, [o.alias]
from t_object o inner join t_package pkg on (o.package_id = pkg.package_id)
where pkg.ea_guid = '<Search Term>'
order by [o.alias] Desc

2. Create your Relationship Matrix
Source:Apply Model Search
  Search GUID of source package (Right Click Package, Copy Reference, Copy Node GUID to Clipboard)
  Search: Select your created search
Target:Apply Model Search
  
3. Refresh

Be aware: A SQL to visualize nested requirements isn't a job of 5 minutes. Flat visualization (alphabetic order) ist mostly simple.

Helmut
Coaching, Training, Workshop (Addins: hoTools, Search&Replace, LineStyle)