Author Topic: Evaluating EA  (Read 3497 times)

sd

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Evaluating EA
« on: March 17, 2003, 07:35:17 am »
Hi!

I am evaluating EA vs Rational Rose (I have extensive knowledge of it) ; but I have some problems.

1. I ran it once, but second time I try run it, it crashes the computer (win2k). Just bluescreen, nothing else.

2. How can one modify rtf documentation formats ? While not bad, I'd still would like to use my styles for them.

3. How requirements can be shared between objects ? I am able to create requirements for one object, but when I try to share them I find no way to do it.

4. How does one take a list of the requirements and the objects that match to them ?

5. My requirements are in Telelogic DOORS and I'd like to import and export these to this tool. How can I do that ?

6. Version control seems to be in package level like in Rose - Am I correct ? Or could it be done in object level ?

7. When the version control is to be implemented, shall there be a way to view different configuraitons at the same time. E.g. can I create version 1.0 from objects a and b and association between them and then create version 2.0 from b and association from a version 1.0 to b version 2.0 and still view both on the diagrammer ?

SD


CJ

  • EA User
  • **
  • Posts: 288
  • Karma: +0/-0
    • View Profile
Re: Evaluating EA
« Reply #1 on: March 17, 2003, 07:55:37 am »
G'day g'day,

1.  I've never run into that problem, either with demo or registered versions.

2.  It can be done ... I think if you search this forum you'll find the answer.

3.  Lookup (in the EA help index) the following:
    - Internal Requirements
    - External Requirements
    - Requirements
Any requirement that is meant to be shared amongst many objects, create the requirement as an external requirement (either make an internal requirement external or use the "Requirement" object.)

4.  Lookup (in the EA help index) the following:
    - Element Relationship Matrix

5-7.  Can't help you there.
Cheers and best regards.

PhilR

  • EA User
  • **
  • Posts: 87
  • Karma: +0/-0
    • View Profile
Re: Evaluating EA
« Reply #2 on: March 17, 2003, 06:53:10 pm »
I don't know what DOORS can export but the simplest way to import requirement into EA is to use the comma delimited (.csv) import.  If DOORS can produces a .csv file (likely) then you should be able to import it.

PhilR

sd

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Evaluating EA
« Reply #3 on: March 18, 2003, 12:55:01 am »
1.      Solved by renaming the diagram I just created. It was it that crashed the tool. When I reopened the diagram from EA it worked.

2.      Found it. Thanks!

3.      Moving them external does not work – it just says ‘there was an error performing requested action’ when I select package ‘View’ from Browse Project Window.  Otherwise associating was really neat – drag and drop to it  ;D. MUCH easier than in Rose.

4.      Neat!

5.      DOORS can make almost any kind of file. Including .cvs.  In order to test this, I made an .cvs export, but there is no data ?? I selected a package where I saw a requirement, then I selected <edit/new> from Specification from .cvs, then selected fields : Requirement Difficulty, Requirement Priority, Name, GUID, Type. Then I pressed Save and then Run and View File, but it contained only headers. Similar problem with XML export – XML export process stays blank and the file is not created. I’d rather not to try import before I have made an export – I’d like to find out first the required syntax.

SD

sd

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Evaluating EA
« Reply #4 on: March 18, 2003, 01:13:23 am »
As for version control, it seems to be the same as in Rose :)

XML control file can be placed (even in Rose format:) ) to a file that can be put to cvs externally of EA.

But what I'd like to see is to make a version of any object and then keep these in version tree. On enhacements there is a note of adding microsofts version control. Will this be on object level like in Rational XDE/Telelogic TAU or still on package level ? Having version control on object level would be great!

SD