Book a Demo

Author Topic: Heading requirements and traceability  (Read 13077 times)

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Re: Heading requirements and traceability
« Reply #15 on: July 24, 2009, 03:53:55 am »
OK, I am including an image (from another application) of what I would like to see.  We input requirements from DOORS.  The application understands the difference between headings and actual requirements and their relationships correctly and displays them differently.  It also displays uncovered requirements differently from covered requirements (EA already does this in the diagrams.)  We can easily find uncovered requirements (exlamation points and red text in the example).  All the reports and views reflect the types of relationships.  In this case (in another view) I can readily see that I have covered 94% of the requirements in the code.  This coverage is based on how many actual requirements have links to the code.


Of course EA need not have the same presentation but it should be able to accomplish the same thing.

Paul

Graham_Moir

  • EA User
  • **
  • Posts: 749
  • Karma: +10/-15
    • View Profile
Re: Heading requirements and traceability
« Reply #16 on: July 28, 2009, 07:04:14 pm »
I fully agree that this would be a very useful enhancement to EA

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Heading requirements and traceability
« Reply #17 on: July 28, 2009, 09:12:57 pm »
Yes, absolutely.

The discussion here has pretty much established that EA has nothing like this. No workarounds seem to be emerging either.

Have you made the feature request Graham?
No, you can't have it!

Graham_Moir

  • EA User
  • **
  • Posts: 749
  • Karma: +10/-15
    • View Profile
Re: Heading requirements and traceability
« Reply #18 on: July 29, 2009, 12:45:03 am »
I've just put in a feature request referencing this thread.

In terms of workaround, does anyone know if a search could be set up using SQL to pull out all elements that have zero relationships ?


Dermot

  • EA Administrator
  • EA User
  • *****
  • Posts: 591
  • Karma: +7/-0
    • View Profile
Re: Heading requirements and traceability
« Reply #19 on: July 29, 2009, 11:53:43 am »
Here is a simple SQL statement for this.  It might help to add a reference to t_package to view this data as well:

SELECT ea_guid AS CLASSGUID, Object_Type AS CLASSTYPE,t_object.Object_ID, t_object.Name
FROM t_object
WHERE  t_object.Object_Type  <> "Package" and  (((t_object.Object_ID) Not In (SELECT t_connector.Start_Object_ID
FROM t_connector) And (t_object.Object_ID) Not In (SELECT t_connector.End_Object_ID
FROM t_connector)))  ;

Graham_Moir

  • EA User
  • **
  • Posts: 749
  • Karma: +10/-15
    • View Profile
Re: Heading requirements and traceability
« Reply #20 on: July 30, 2009, 12:50:40 am »
Thanks Dermot,  although I obviously didn't specifiy my requirements very well  :) !    

Can you modify the SQL to exclude
- Notes/Text elements
- Legends
- Boundaries
- Model documents
- Master documents
- Hyperlinks

Many thanks !
Graham
« Last Edit: July 30, 2009, 12:51:47 am by Graham_Moir »