Messages

1

General Board / Re: Problems with Import Source Directory feature

« on: April 27, 2010, 02:19:51 am »

Perfect - the Local Paths trick did the trick.
Thanks!
Beth

2

General Board / Problems with Import Source Directory feature

« on: April 24, 2010, 09:39:56 am »

We have an EA project that we keep under source control.  We are trying to use the Code Engineering | Import Source Directory  feature to keep the model updated with the current code at the end of each iteration.  However it seems that only the developer that originally created the EA project can successfully reverse engineer the code.  We I try to update it, all the objects that were in the original model are duplicated.

We have imported our code so the EA project matches our namespace.  As an example, the project contains a package 'src' in the main project.  Under that package we have a package structure that matches our namespace Ims.Efb.Fls.EfbObjectLibrary. In EfbObjectLibrary we have many different objects used by the application.  When I first open the project, there is only one of each class.

Now if I right-click on src and choose the Code Engineering | Import Source Directory option, and import the code from my machine, I will have a single class representing any new objects in the model.  But all the other classes are duplicated.  Here are the options I choose:
Root Directory ==> set to my location of 'src'
Source Type ==> C#
File Extenstions ==> .cs
Recursively Process Subdirectories
Create Logical Diagram
Package Structure ==> Create Package per namespace
Remove classes ==> Prompt for action

For the Synch option, I have tried both the "Synchronize existing classes" and the "Overwrite existing classes" options and they both behave in the same way.

I have also tried the Code Engineering | Synchronize Package Contents option:
Update Type ==> Reverse engineer (source -> model)
Include child packages

This did not duplicate my classes in the model, but it did not import anything new either (in other words, it looked the same as it did prior to running this).

Is there an issue with reverse engineering the code from different machines?  The starting location of the 'src' directory may be different on different machines, but the structure from 'src' down is guaranteed to be the same on every developer's machine.  Since that is the starting location of the import, I would hope that would work.

I am using EA 7.1.833, Database Version 4.01.  This is a C# project.

Thanks,
Beth

3

Uml Process / Test Case Traceability

« on: October 20, 2009, 11:07:00 am »

I read through this thread (http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1254125691/0) with interest as it seems to be related to what I'm trying to do - provide some traceability between my Requirements and Use Cases to Test Cases.  It is not obvious to me on how to do this with EA.

What we have are our System Requirements, which we are modeling in the tool as the Requirements.  We decompose those further into Use Cases.  I can provide bi-directional traceability between the Reqs and the Use Cases without any problem.

Now I want to create TestCases within EA that will allow me to see the traceability to either the Reqs or Use Cases.

We have "System" Test Cases which make up our System Verification Test, which need to test at the Requirement level.

We have "Integration" Test Cases which test the various scenarios of a Use Case.

I see how I can create and document the different types of Test Cases with the Testing View (that has the 5 tabs).  But I don't see how I can map between these Test Cases and either the Reqs or Use Cases.

When I look at the diagram in the post referenced above (the one that models the scenarios as operations on the Use Case) - am I correct in assuming you are doing this entirely with the Use Case modeling, and you are NOT defining Test Cases (as defined by the Test View)?

I've read through the Testing Support page on the web, and also read the help on Testing.  But I don't see anything that tells me how to setup the models to provide that traceability.

Can anyone give me some pointers?
Thanks,
Beth

PS. We are currently using v7.1.833