Messages

1396

Automation Interface, Add-Ins and Tools / Element status setting???

« on: November 17, 2004, 05:57:52 pm »

What am I doing wrong - after excecution the element is entered, the name,notes and type etc is correct but the status is set to Proposed?

Function addreq(desc As String, dets As String) As String
   Dim rr As Object
   Set rr = reqtspkg.Elements.AddNew(desc,  "Requirement")
   rr.Notes = dets
   rr.Status = "Approved"
   rr.Type = "Functional"
   rr.Update
   reqtspkg.Elements.Refresh
   addreq = rr.ElementGUID
End Function

tia
Bruce

1397

Automation Interface, Add-Ins and Tools / Re: Automation Model as EA model??

« on: September 20, 2004, 04:17:21 pm »

Happy with the plenty of documentation - just lazy enough to want an actual EAP model or XMI or XML or even csv file to import it!  

Bruce

1398

Automation Interface, Add-Ins and Tools / Re: Automation Model as EA model??

« on: September 15, 2004, 06:00:51 pm »

Just want to float this to the top again - is there one?
B

1399

Automation Interface, Add-Ins and Tools / Re: System Emulation

« on: July 11, 2004, 05:02:43 pm »

There is support for STATIC analysis of runtime behaviour through the use of run state and object state used in instance diagrams.

EA does not dynamically model the impact of state/value changes across objects.  However we have successfully used these instance models to successfully analyse a complex behaviour situation for design purposes.

I see no reason why such instance models cannot be used in the same manner for debugging use.

hth
Bruce

1400

Automation Interface, Add-Ins and Tools / Re: Automate Reverse Enginering?

« on: May 18, 2004, 03:56:55 pm »

Dear jflowers,

Please note that this is a user forum.

rgrds
Bruce

1401

Automation Interface, Add-Ins and Tools / Re: configuration for C#

« on: March 24, 2004, 12:07:26 pm »

We have NT4 as the operating system here.  You cannot install the .Net SDK on anything less than Win2000, only the framework.  I use #D as the IDE.

So I was wondering if there was another way to generate the Interop assembly.
B

1402

Automation Interface, Add-Ins and Tools / Re: configuration for C#

« on: March 23, 2004, 03:33:52 pm »

Hi Kopi,

Any idea of how it could be done for an NT based system (SDK wont run only the .net environment)

tia
Bruce

1403

Automation Interface, Add-Ins and Tools / Re: Trouble Getting AddIn Loaded

« on: March 22, 2004, 04:54:55 pm »

I'd love to see a copy of #D addin!
'm running #D 99b 1.1
tia
Bruce

1404

Automation Interface, Add-Ins and Tools / Patterns for virtual documents

« on: January 21, 2004, 02:36:48 pm »

I am trying to create a set of standardised documentation items for use across many models.
I have created a set of virtual document items that work really well for the various standard models we are using (Requirements Model, Analysis Model, Design Model, Implementation Model) and now I want to make them available for ease of use by the various teams.

Each model contains (amongst other things) a Documentation package, set to be excluded from RTF reports, for containing the virtual doco classes.  I tried to save each doco as a pattern, which the team could import as needed for their component.  This seemed to work fine - they can add the doco pattern and give it a name to suit them. However, when we try to generate the rtf report all we get is the report template notes - none of the report elements (i.e. the virtual doc class attributes) are generated.

Looking at the EA database I see that the attribute classifier for the original virtual doco is set to the object ID of the included package but the attributes of the virtual doco created from the pattern do not have a classifer.  This makes sense, the created element attributes need to be pointed to the proper elements in the current repository.

Now to the question(s).

Is it possible to make the class attributes "prompt for classifier"?
If so, when I create the pattern, how do I tell the system that they are t be prompted for?

tia
Bruce