Relationship Matrix in RTF generated template?

[Emilio]

I have used the wonderful Relationship Matrix to create realize relationships between Use Cases and Requirements.

So far in my current document (a cut and paste of the RTF) I have added a small subtitle to each Use Case document section (2.1 Sample Use Case) to state which Requirement(s) it implements. This I have to do manually to show as:

    2.1 Sample Use Case
    Requirement ID(s): GEN-FR-2.5

    description of the use case

Well, I was hoping to also generate the relationship matrix into an RTF document so that I could cut and paste it into my document. Unfortunately there seems to be no RTF document template for the Relationship Matrix

Anybody knows what is the best way to do it?

[«Midnight»]

Emilio,

The lack of reports for the Matrix was a known problem a while ago. Somehow I think this got addressed, but I could be wrong.

[If anyone knows for sure please post here, either way.]

If you are not using a very recent build I suggest you read the EA history page to see if an upgrade might be a solution.

David

[Dermot]

This has not been added to the RTF report templates, however I would suggest you send in a Feature Request for it.
Given you are wanting to place it in another document the option to export it to CVS and import to Word or a Spreadsheet can be used for this.  In the Matrix window is the Options buton: Matrix | Export to CSV
(using a spreadsheet - a table in Word 'Should' work the same)
- Open the csv file in a spreadsheet
- Format the first row text to 90 degrees
- Auto-format the cells with the 'x' to shrink them
- Ensure column A is broad enough for the text.

[Emilio]

Dermot,
   The CSV export does not work quite as you said. I did the CSV export and I see that each "record" contains the data such as name,,,,,x,,,x,,, etc.

The problem is ALL the data is placed by Excel in Column A, that means that before one can make the top row with vertical (90 degree) orientation, one has to manually split cell A1 into A1, A2, A3, A4.. An.

In other words the export as interpreted by MS Excel is just ONE column with each cell in that column containing the whole data of the record.

[Christian Herger]

Hi Emilio

The export works just well, I think...

The problem here is MS Excel:
Once upon a time csv meant comma seperated values but ....
Microsoft  one day decided that a semicolon is not as often used as a comma in text fields (what actually is true) and therefore they decided to open csv files by default with semicolon delimiter...

However, there is a solution:
Try Data --> Import External Data --> Import Data... (at least with Excel 2003) and then choose textfile types and then...   Hopefully the text is 'quoted'; otherwise a comma in it will mess your data...
But this seems the wrong forum for MS Office issues...  

[«Midnight»]

Excel 2007 seems to have two ways to go about this. You can do a 'real' import of data, which would involve a connection source or pulling in a 'raw' text file. In the latter case you could import the entire thing into a single column as we've heard described above.

Once you get the data into a single Excel column you can do a conversion of text to columns - similar to Word converting text to a table. This allows you to choose the delimiter. Excel will even read the first row and try to guess the delimiter, so you might see the comma suggested.

[Dermot]

Hello Emilio,
I must admit all I do is use Excel: File | Import  - but in the Open dialg box select -  Files of Type: (*.prn,*.txt, *.csv).
It does import with the correct cell/column relationship.

[«Midnight»]

Hello Emilio,
I must admit all I do is use Excel: File | Import  - but in the Open dialg box select -  Files of Type: (*.prn,*.txt, *.csv).
It does import with the correct cell/column relationship.

But which version of Excel?

In Excel 2007 the File | Import functionality is hidden somewhere else.

[Dermot]

My apologies - that was actually: File | Open | Files of Type: (*.prn,*.txt, *.csv).
(Excel is  2002)