Messages - David

All those who need a one off import of RequisitePro data (not round trip) and have the same issue below, make yourselves known.

I have tried to import a large set of requirements, business rules and use case texts from CSV export files. This has been partly successful however I have been unable to keep the hierarchy of links for tracability.Has anyone cracked this or can advise how best to proceed.

Would Sparx Systems be willing to provide the required functionality if there are a fare number of users with this issue/request?

As we don't work with Business Rule functionality very often. We kept our existing Corporate Floating licences and just purchased one Ultimate Floating licence, which we share to access Business Rules and other useful functionality then the need arises.The user just need to select the Ultimate Floating licence from the licence manager.

When I moved from .eap to an ORACLE repository I had to install the Oracle 10g Client on my local PC before I could obtain a stable connection.I beleive you need to install the Oracle 10g Client and use the Oracle ODBC Driver 10.2.0.1.0.Then next time you connect to your Oracle repository use this ODBC driver before begining your schema import.

With regard to Auto Name Counters. I received the following reply from Sparx Support back in Oct 2008 for "Registered Support Request - Auto Numbering from merged .EAP files."

Unfortunately Auto Name Counters cannot be applied to individual Stereotypes (only element types), therefore only one can be applied to Requirement type elements. The Auto Name settings are saved in the EAP file. Unfortunately there is also no option to Export/Import the Auto Name settings. I will raise two feature requests on your behalf so that this functionality is considered for implementation in a future release of EA.

Currently the Auto Name setting would need to be manually changed (via Setting | Auto Name Counters) depending on which type of Requirements are being created. If necessary you can rename a number of elements fairly easily by exporting to CSV, editing in a spreadsheet and importing back into EA (see "CSV Import and Export" in EA help).

I am looking for suggestions on the best structure for an EA DBMS Repository and found this post.Jaime Gonzalez's entry back in Oct 2002 looks of interest, but I wondered if new EA functionality since then has opened the door for a better way that aids multi projects and RTF documentation creating.

Thanks for the detailed explanation of how you went about creating your addin.

Lets just hope "the management" at your company are willing to share your code

Otherwise my only alternative is to create a view in ReqPro of the elements (requirements, business rules, etc.) and export to CSV. Then do some major Excel transition of this data before creating an EA import template(s).

I know I really should keep it as simple as possible and use white boards for diagrams and small cards for user stories. The Product Backlog can be held in an Excel workbook (with filtering on priority).

I would like to keep an historial record of the User Stories and also thought the Element List View in EA could help with the Sprint Backlog.

Would this be possilble or should I keep it simple (if it 'ant broke don't fix it).

Has anyone using EA to record User Stories, if so do you use the Note or Requirement element with a tagged value to hold the story point value?

Also how have you managed to prioritize the Product Backlog (to allow for the shuffle of items as priorities change from month to month), so the SCRUM Team moves the highest priority items to the Sprint Backlog?