Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - David Rains (bioform)

Pages: 1 [2] 3 4 ... 6
I am back to using EA in my new job :)  Starting creating some profiles (stereotyped packages and classes) in 14.1 (last build) and switched to 15...
Problem (tested in 14.1 and 15) is when I extend my stereotype "package" to the package metaclass, and my stereotype "class" to the class metaclass; export/import I get:

- Class Icon represented as Package, but when dragged onto diagram - it IS a stereotyped Class (ok, can live with that... I guess)
- Package Icon represented as Package, but when dragged onto diagram - it IS a stereotyped Class (umm, can't live with that....)

Anyone else experiencing this... Any workarounds... I can live without some of the tagged values on the packages, and such if I have to... and just define the Stereotypes manually...

BTW: Was going to stay in 14 as an add-in I am trying out (OntoUML) works in 14.1 but not in 15. But is it worth jumping into 15 at this time? Might not be a bad time for me (or my client as this will be totally new to them...)

Thanks as always... (this seems to be a common issue with releases if memory serves me...)

David "Back in the EA space" Rains

Bugs and Issues / Re: Glossary matching options
« on: July 31, 2019, 07:13:16 am »
And yet years have gone by with no action...

"a full-fledged scripting experience" - gave me hope... Last time had to install MS Studio app and uninstall to get the script debugger to be retained... your link saved me a lot of trouble and uninstalls. Thanks

Like a charm!!  Added to my karama debt and my EA download collection! (New Laptop, so still doing installs)... Having some fun with Python/nltk and NLP of requirement and engineering documents at work :); and well playing/learning with corpus of Holy Grail... keep getting sidetracked on quotes about swallows and coconuts...

Hmm... edited link in my post that should work now...

"If you just need the Debugging Tools for Windows 10, and not Windows Driver Kit (WDK) for Windows 10 or Visual Studio 2017, you can install the debugging tools as a standalone component from the Windows SDK. In the SDK installation wizard, select Debugging Tools for Windows, and deselect all other components."

WinDbg Preview is a new version of WinDbg with more modern visuals, faster windows, a full-fledged scripting experience, built with the extensible debugger data model front and center. WinDbg Preview is using the same underlying engine as WinDbg today, so all the commands, extensions, and workflows still work as they did before.

So do we know if this will work with EA scripting as the debugger?

Okay, so I did some other work on my new laptop, reopened the EA 14.1 file and it is fine?! <sigh>

Using EA 14.1 (Just upgraded, was using 13.5)

Problem 1: All of my stereotypes are being displayed as 'Packages' in the 'Loaded Profile' and regardless of stereotype selected (attribute, operation, class, package) they are ALL sterotyped 'Classes' when I use the profile created from the Package

Problem 2: Created from Diagram (... displayed as 'Packages", but unable to drag to diagram...)

I created them the way I always have (Drag stereotype and name it, drag metaclass, connect stereotype to metaclass with extend), tried using create profile (as package and as diagram) using "new" ribbon method (specialize, publish as...)...

I also noticed that I have to add ".xml" to the file name otherwise it is NOT being saved as an XML file (? e.g. not reconginized by Win 10 as XML file, just 'file")

Seems like this would have come up in the search IF THIS WAS A BUG.... Is the world just after Bioform for upgrading to 14.1?  :)

<?xml version="1.0" encoding="windows-1252"?>
<UMLProfile profiletype="uml2">
   <Documentation id="E372ADF2-C" name="TestAsDgm" version="" notes="TestAsDgm"/>
         <Stereotype name="asAtrb" notes="" cx="90" cy="70" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
               <Apply type="Attribute"/>
         <Stereotype name="asCls" notes="" cx="90" cy="70" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
               <Apply type="Class">
                  <Property name="isActive" value=""/>
         <Stereotype name="asOpr" notes="" cx="90" cy="70" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
               <Apply type="Operation">
                  <Property name="isOrdered" value=""/>
                  <Property name="isQuery" value="false"/>
                  <Property name="isUnique" value=""/>
                  <Property name="lower" value=""/>
                  <Property name="upper" value=""/>
         <Stereotype name="asPkg" notes="" cx="90" cy="70" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
               <Apply type="Package">
                  <Property name="URI" value=""/>


I think you also 'Might' have to have security enabled for that feature?  Remember something like that...
"However IF you do have security enabled, just ignore this..." :)

Yeah, sleep is VERY good!  Changing gear for the rest of the day... creating UML profile to support metamodel from Lambsweerde's Requirements Engineering book (the one I grab when the building catches fire!!) - Of course I have yours on digital :)


David "I think this is my BEST profile, umm UML speaking" Rains

I have not used this feature in awhile, and went ahead and defined a new one... the behavior was the sturctured tagged value did NOT display the child tags as expected... I was using an older release of EA (13.0) at work (don't ask why...) and installed and tried version 13.5 on my laptop (new file, simple example using the reference below) - same result, seems to be no longer working?

Has anyone noticed this behavior is version 13 or 14?  I will reinstall 14 at home and try it out there... new file, same example... and follow back with my results...

Any help appreciated. (BTW did a global search, found a lot of hits but nothing on a bug or behavior like this in the other forum groups)



Okay, so I am hearing that their recommendation might not really be worth worrying about right now? (engine not up to date, etc.)  I will take that to heart... Since I am learning Python, it would be nice to start migrating from VBScript... so finding a way to leverage my training from python into a related lanaguage seems like a good idea...

Querty, you mentioned a Python environment you like using... (I am currently learning with Sublime and Jupyter Notebooks, so now is a good time to get introduced to an IDE that might help me move forward - Wing from WingWare will take a look at that!)

What about the Hybrid Scripting document from Sparx? That looked interesting... but is it restricted to MS NET languages... (integration with VS) in 14.1 I see as in the example Java, C#, and C++... it is possible to work with other languages? If so HOW would I give them visibility within that Model Wizard | Application Patterns window... is this a 'feature' from Sparx or a series of configuration settings?

From EA's automation help ... Sparx Systems now recommends creating any new scripts in JavaScript. Our JavaScript implementation is based on the Mozilla Spidermonkey implementation... The advantage of using JavaScript is that it is wholly built and distributed by Sparx Systems, meaning we are able to actively support both the execution and debugging of scripts into the future.

My question - I am finally getting back to using EA again at work and supporting some automation/customizations... also I am learning Python so I can make use of some NLP toolkits in my requirements engineering work... So jumping to JavaScript.... what "source" should I be looking for to try to match my learning to EA's implementation? Am I going to run into issues.... e.g., ScriptLib examples are in JScript(?)  vs. what they are calling JavaScript correct?  I just need a little advice to make sure I get started on the right foot...

Any links, etc. appreciated...

General Board / Re: Importing glossary terms
« on: October 18, 2018, 03:34:14 pm »
Okay, sorry for the delay. I am running EA 13.1 due to work environment. Will swap my build to 14.1 and give it a try and post back to here. also will try install on my backup Win 10 HP vs. Dell and see how things work out there... Thanks Querty and Geert!

BTW having SO much fun at my new job - helping an gov. org implement MBSE using EA (don't ask why 13.1, but will be moving to 14 soon...) Right now I am working on moving them OFF DOORS 9.5 for ReqMan to EA...

Model On!

General Board / Re: Importing glossary terms
« on: October 16, 2018, 08:09:37 am »
Nope, have all of those references 1:1 match. Any other ideas? Should/Could I try an earlier version?
I verified that the importing of a class works... seems to be specific to EA.Term, throws error BEFORE getTermByName I believe... as the breakpoint does not go into that function...

Thanks... been fun looking at VBA code again :)

Pages: 1 [2] 3 4 ... 6