Book a Demo

Author Topic: Duplicated requirements - data intregrity checker  (Read 4992 times)

MaxRussell

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Duplicated requirements - data intregrity checker
« on: June 18, 2011, 12:23:25 am »
Hi,

we have a script that makes use of the API to pull requirements out of EA and copy them into HP Quality Center. The script looks for new/updated requirements and compares them with Quality Center. Where there is an update to be made, or a change in the structure (e.g. containing project), this is carried out.

Recently the DB folks ran the Data Integrity checker tool. Now, when the script is run, we see duplication of the requirements in Quality Center. This would seem to be because at the EA side, the refreshed items are seen as new - so when added into Quality Center, they are duplicated.

Does the data integrity checker refresh GUIDs? If the script is making use of the EA Element to perform the functionality above and the ID of the element has changed, what amendments would be required to alleviate this situation?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Duplicated requirements - data intregrity chec
« Reply #1 on: June 21, 2011, 05:27:49 pm »
Max,

I'm not sure, but I believe indeed that the integrity checker does change guid's from time to time. (in case of duplicates for example).
What I would do in your case is try to identify the requirements by their fully qualified name and eliminate the duplicates that way.

Geert

bch

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: Duplicated requirements - data intregrity chec
« Reply #2 on: July 16, 2011, 02:06:06 am »
Quote
Hi,

we have a script that makes use of the API to pull requirements out of EA and copy them into HP Quality Center. The script looks for new/updated requirements and compares them with Quality Center. Where there is an update to be made, or a change in the structure (e.g. containing project), this is carried out.

Recently the DB folks ran the Data Integrity checker tool. Now, when the script is run, we see duplication of the requirements in Quality Center. This would seem to be because at the EA side, the refreshed items are seen as new - so when added into Quality Center, they are duplicated.

Does the data integrity checker refresh GUIDs? If the script is making use of the EA Element to perform the functionality above and the ID of the element has changed, what amendments would be required to alleviate this situation?


Would you be willing to share the script?  This is precisely what I was looking for.

MaxRussell

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Duplicated requirements - data intregrity chec
« Reply #3 on: July 18, 2011, 08:03:16 pm »
Unfortunately I can't.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Duplicated requirements - data intregrity chec
« Reply #4 on: July 19, 2011, 07:43:45 pm »
Quote
Would you be willing to share the script?  This is precisely what I was looking for.
How about SELECT * FROM T_OBJECT WHERE TYPE = "Requirement" and evaluate the results?

q.

MaxRussell

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Duplicated requirements - data intregrity chec
« Reply #5 on: July 27, 2011, 10:46:33 pm »
Quick question - is the an Element determined by quid? That is to say, within the EA API, when I reference via Element, is the actual identification occuring on the GUID?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Duplicated requirements - data intregrity chec
« Reply #6 on: July 27, 2011, 11:09:06 pm »
I don't think so. If you log all database calls when using the API I think it mainly uses the regular ID field to identify the elements.

Geert