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 - Sparxs411

Pages: [1]
General Board / Re: Referencing external XSDs and elements in EA
« on: July 28, 2018, 01:00:52 am »
Thanks Geert. You were referring to importing the XSD as its own package, correct? Unfortunately when I import the XSD it seems to throw a lot of errors my way. I will try to bring it in again so then I am pointing to it locally.


General Board / Referencing external XSDs and elements in EA
« on: July 27, 2018, 11:39:39 pm »

  I am attempting to reference an XSD (via URL) and associated elements outside of the core model. Is there a way to do this in EA where you can reference the location of an external XSD and link them? Ideally I would like to make some of my elements point to those "types" in that schema.


I have done further research on this topic. So it appears that elements related to a ComplexType are ordered in the schema based on the date the "Connector" is added (?). Or perhaps it is based on an object ID? When I deleted a connector associated with a ComplexType from the model and then added it back to the model it changed the order of the elements. Any insight into this would be appreciated or ideas on a way to make alphabetical order the default. I know one workaround is adding a position tag to the "source" of the connector, but doing this for a large model is very cumbersome.



  EA allows for documentation/annotations/notes to be added to classes, connectors, attributes, etc via an annotation window. I would like to add additional documentation to my model and the resultant XSD.  Is there a way via EA to do this in a structured way rather than adding additional information in the annotation window? Specifically, I am trying to incorporate deprecation information into the model.


Thank you for the information. Based of further evaluation it appears that the order of elements within a schema (created by EA) are driven by the order in which they were "created" in  the model. Has anyone else experienced this? Below is an example of the order of elements from an EA schema; ideally I would like these to be alphabetical order.

                        <xs:element name="architecture" type="feat:ArchitectureData" minOccurs="0" maxOccurs="1"/>
         <xs:element name="operations" type="feat:Operations" minOccurs="0" maxOccurs="1"/>
         <xs:element name="blah" type="feat:Blah" minOccurs="0" maxOccurs="1"/>



  I am using EA to model drive schemas. I am able to produce schemas but would like to control the order elements and attributes appear in the schemas. I know one way of doing this is using the position tag on the source of the connector however that is a rather laborious task to do for the entire model. Is there a way to make the alphabetical order the default order?

Thanks in advance.

General Board / Globally Removing Author From Model
« on: May 19, 2018, 05:52:16 am »
Is anyone aware of a way to globally remove or change author names throughout the model? Can this be performed through project settings? I know the author can be changed on an individual basis (e.g., for each element created), but really interested in turn key solution for entire model.


Uml Process / Re: Enumeration of an Associated Name
« on: March 16, 2018, 11:52:47 pm »
Thank you for the response. Now that you mention it, you are right in that I am after a "Enum" tagged value to the connector. That is done in the stereotype of the target, but where would I define the enumerations?

Thank you for your help in advance!

Uml Process / Enumeration of an Associated Name
« on: March 16, 2018, 07:51:00 am »
Hello All,

  Question regarding the flexibility with defining associations within EA. Is it possible to enumerate or leave as free text a "target role"? If so, how is this achieved? The target role I am dealing with is "associatedWith" but this may be too constricting to user base. Ideally when generating a message from the schema I would like the user to define that relationship or choose from a list.


Pages: [1]