Messages

1

Automation Interface, Add-Ins and Tools / Import OWL/RDF option greyed out

« on: September 04, 2020, 07:32:38 pm »

Just installed EA v15.

Per instructions here...
https://sparxsystems.com/enterprise_architect_user_guide/15.1/model_domains/odm_commands.html
Created a new Project and an ODM RDF Model Package.
Selected the package and the Import and Export OWL/RDF options are greyed out.

Anyone else experienced this issue?

Note: I last used EA at v10 and still getting used to the new interface so this could well be due to my own unfmiliarity with the new interface.

2

Suggestions and Requests / Re: ORM 2

« on: May 31, 2012, 04:40:32 pm »

Yes, I too am keen to use ORM2 in EA. Any users or partners tried to develop a profile or keen to collaborate on one???

3

General Board / Re: How to Size an EA DB Repository

« on: August 11, 2010, 03:28:53 pm »

Good point. I'll ask in  my reply and post back to this topic.
Cheers
Steve

4

General Board / Re: How to Size an EA DB Repository

« on: August 11, 2010, 02:51:44 pm »

I posted this question to sparx and they advised that as well as the size of the model consideration should be given to the the inclusion of RTF document artifacts and images as these can more significantly impact the size of the repository than the model data.

Cheers
Steve

5

General Board / Re: How to Size an EA DB Repository

« on: August 10, 2010, 09:26:02 am »

Thankyou Geert.  
Much appreciated.
At least I have something to base my sizing on now.

Cheers
Steve

6

General Board / Re: How to Size an EA DB Repository

« on: August 09, 2010, 05:08:15 pm »

Hi Geert,

We are planning to deploy a central RDBMS EA repository to store all our project and baseline architecture models in the one location.

BAs and Solution Architects would connect to this repository to maintain their models and would use Subversion to version control packages within their project.

I'd like to know if there are some rules of thumb for how one would determine the size of the RDBMS. I understand of course that this would depend on the nature of the models however it would be useful to know , relative to the size of a project model what corresponding space would be required in the RDBMS repository.

For example there may be indexing on the relational model that isn't necessarily in place on the access(jet) model in the EAP file that may mean a 20Mb EAP would end up taking more than 20Mb when deployed into SQLServer or Oracle repository.

If I know the relativities of EAP vs RDBMS I can then do the rest in terms of estimating the size of the RDBMS.

Many thanks
Steve

7

General Board / How to Size an EA DB Repository

« on: August 09, 2010, 02:01:23 pm »

Anyone have any guidelines on how to size an EA RDBMS Repository?
I've searched the Sparxsystems site but to no avail.

Any help most appreciated.
Steve

8

General Board / Re: Two Data Modeling Questions

« on: August 10, 2010, 09:46:33 am »

All, Please post your request for this feature to Sparx !

It has caused me a huge amount of pain   as I've been unable for to reverse engineer directly from a DB2 z/OS db so have had to resort to importing the DDL extracted for me by the DBAs.

DDL went into erwin then exporting out as CSV then imported into EA using a custom automation script. Not an ideal process when most data modelling tools have the capability to import from DDL.

Ok, I've vented now. I feel better.  

9

Automation Interface, Add-Ins and Tools / Generating a UML Profile incompatible with TOGAF

« on: January 06, 2010, 10:20:08 am »

Being a newbie to EA , I followed the instructions to the letter in the Help File that described how to create a UML Profile.

After countless wasted hours I found that Saving a UML Profile isn't compatible with the TOGAF Add-In.

Every time I saved a UML Profile it would fail to generate the "AppliesTo" tags in the xml file.

Eventually I noticed that there is both an AppliesTo and Extends defined in the ACM Relationship section of the Toolbox for the TOGAF MDG plug-in which appear to affect the UML Profile xml file generation capability of EA.

I turned off the TOGAF Add-in, removed the existing extension relationships I created between the stereotypes and the Metaclasses and re-created them. I noticed the extends relationships now appeared as <<extends>> instead of <<Extends>> suggesting that the TOGAF MDG Add-in re-defines this relationship which is applied when you use the Profile Relationships in the Toolbox.

Now when I save the UML Profiles, the AppliesTo tags nicely appears in the xml and the UML Profile is able to be imported into EA.

I have since restarted EA with the TOGAF Add-In enabled and not experienced the same problem again.

Suggestions to SparxSystems :
1) Update the either the TOGAF Add-In or the Profile components to resolve the potential conflict between the <<Extends>> and <<extends>> relationships.
2) Provide a structured example in the form of a tutorial on the EA Support pages.

After I disabled the TOGAF Add-In.... (note the sections in yellow did not generate with TOGAF Add-In enabled....
UML Profile XML file

Code: [Select]

<?xml version="1.0" encoding="windows-1252"?>
<UMLProfile profiletype="uml2">
      <Documentation id="BD7E4F67-B" name="Solution" version="1.0" notes="Modelling profile for depiction of high level technical solutions within business domains.&#xA;"/>
      <Content>
            <Stereotypes>
                  <Stereotype name="Solution" metatype="Solution" notes="A solution is a set of off the shelf and bespoke components deployed across one or more systems in order to support a specific set of business functions.&#xA;" cx="90" cy="70" bgcolor="16777215" fontcolor="0" bordercolor="0" borderwidth="2" hideicon="0">
                        <Image type="EAShapeScript 1.0" xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64">UEsDBBQAAAAIALJ4JTwmkX6gEwEAAGoCAAAHABEAc3RyLmRhdFVUDQAHRVVDS0VVQ0tFVUNL
hZJBS8NAEIXftYL/YamXCAGr4EGkd3vyUBE8rk2aVqIJ3UiR0v/uN7upWg3IMJnZ7LyZNzMb
tJJXq1JOr3hrvWmnU51ohNcoxPsCb6upOm30TuxtHxG04LZGn/mWAxFrLcmc6Y6YoAe+Faex
ZlRrOS1AlOQfK0ef8AP2HDG8qTuSnS4Qp3vY1frAK6joYef6Wh2MrZsGTi94VsHFLgLWo4lF
Fes6PcYOjPPfaq6v9pvttGc6hBjCz4k2FgduS7jWiCNjg23o4f9cIWY5YL+Rma50jeS61A1+
rgnzSxs4zrD/muoIXJqNZ5JV3F4GzrCWZ/LDWq6ET8gWrL2Tjqnb7Nv4foq41zP+e6ZV4tke
E4s9+glQSwECFwsUAAAACACyeCU8JpF+oBMBAABqAgAABwAJAAAAAAAAAAAAAIAAAAAAc3Ry
LmRhdFVUBQAHRVVDS1BLBQYAAAAAAQABAD4AAABJAQAAAAA=</Image>
[highlight]                        <AppliesTo>
                              <Apply type="Component">
                                    <Property name="isIndirectlyInstantiated" value="true"/>
                              </Apply>
                        </AppliesTo>[/highlight]
                        <TaggedValues>
                              <Tag name="Impacted" type="enumeration" description="" unit="" values="Yes,No" default="No"/>
                        </TaggedValues>
                  </Stereotype>
                  <Stereotype name="SolutionDomain" metatype="SolutionDomain" notes="A collection of solutions that support a particular class of business problem or support a particular business function.&#xA;" cx="90" cy="70" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
                        <Image type="EAShapeScript 1.0" xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64">UEsDBBQAAAAIAMR4JTxgA89yEgEAAGgCAAAHABEAc3RyLmRhdFVUDQAHelVDS3pVQ0t6VUNL
hZJBS8NAEIXftUL/w1IvKRSsgiBI7+3JgyJ4XJs0rcQmdCMipf/db3ZTtRqQYTKz2Xkzb2Y2
aC2vRoWcXvE22mqvoc40wKsV4n2O966ZWu30RuxtFxG05LZCn/kWPREbrcicaU5M0APfktNI
C6o1nJYgCvKPNEGf8AN2jBje1J3IXheI0x3sKn3g5VT0sHNdrRbG1k0Npxc8q+BiFwHr0cSi
jHWdHmMHxvlvNddV+8121jHtQ/Th74k2FkduK7hWiCNjja3p4f9cIWY5Yr+Rma50jUx0iXeD
nTK/tIHTDIevqQ7Apdl4JlnG7WXgDGt5pj+s5Ur4hGzA2jtpmbrNvonvJ497Pee/Z1oFnu0x
sTjoE1BLAQIXCxQAAAAIAMR4JTxgA89yEgEAAGgCAAAHAAkAAAAAAAAAAAAAgAAAAABzdHIu
ZGF0VVQFAAd6VUNLUEsFBgAAAAABAAEAPgAAAEgBAAAAAA==</Image>
[highlight]                        <AppliesTo>
                              <Apply type="Component">
                                    <Property name="isIndirectlyInstantiated" value="true"/>
                              </Apply>
                        </AppliesTo>[/highlight]
                        <TaggedValues>
                              <Tag name="Impacted" type="enumeration" description="" unit="" values="Yes,No" default="No"/>
                        </TaggedValues>
                  </Stereotype>
            </Stereotypes>
            <TaggedValueTypes/>
      </Content>
</UMLProfile>

Cheers
Steve