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

Pages: [1] 2 3 4
1
General Board / Re: Diagrams in report cropped!
« on: September 06, 2017, 04:36:07 am »
I have noticed similar behaviour when using EA from within a virtualised windows environment (like Parallels on Mac). Depending on the resolution set on the Windows desktop the images are cropped to a larger or lesser extent. Before generation of final documentation I sometimes need to change resolution.

/Hans

2
General Board / Re: ISO 80000-1 Quantaties and Units
« on: May 29, 2017, 06:44:19 pm »
if I have done it correctly, it doesn't look like the ISO Library  (ISO 80000-1 Quantities and Units).

Do you see the Quantities and Units? Maybe I've missed something.
I forgot to mention that the library is only available from the SysML 1.3 Technology which is the one I still use most of the time. Note also that there were some changes made to units in SysML 1.4. Tim Weilkiens has written a post about the changes here: http://model-based-systems-engineering.com/2015/04/13/whats-new-in-sysml-1-4-units/
/Hans

3
General Board / Re: ISO 80000-1 Quantaties and Units
« on: May 29, 2017, 05:24:10 pm »
Those are available from the model wizard (Right click on a package -> Add a Model using Wizard...). My first impression is that they work reasonably ok.

/Hans

4
I recognise the need that I think jankari is describing. My interpretation is that jankari needs to be able to include a tagged value, defined on the model document itself, into the generated report from that model document. Thus, analogous to Project Constants, but for each model document in a virtual document. The Report Constants setting on a virtual document overwrites any defined tagged values in a n individual model document. Also, it is not possible to include a custom defined tagged value of a virtual document.

With the above functionality it would be possible reduce the number of templates necessary in a model by reusing the same template for many different sections of a report. Consider for example a report with a standard template (look) for all chapters, except that the chapter heading is different for all chapters. With the possibility to include tagged values on the model document itself into the report, we could reuse one single template throughout the virtual document.

/Hans

5

  • In order to share a common page definition between two diagram types you need to have this common page definition extend the ToolboxPage meta classes in both profiles! The common page can be located in one of the toolbox page packages, it does not matter which. But it should be visible in the diagrams of both toolbox pages.

No, doesn't work. Page only displayed in one toolbox associated with profile where this page is located.

Then you must have generated the toolbox profile from a directory instead of the diagrams. Or, the toolbox page is NOT present in both toolbox profile diagrams before generating the toolbox profiles. (I use this method all the time and know for a fact that it works.)

6
I'm not sure I understand you but I think I do, and yes it is possible to achieve what you want. A couple of points:

  • Each diagram type can only be associated with one toolbox profile, which means you have to create two toolbox profiles if you have two diagram types. Each toolbox profile need to have its own ToolboxPage metaclass. To create a Toolbox Page you extend this metaclass in a "stereotype" which holds the definition of the different elements you wish to have in your toolbox page.
  • In order to share a common page definition between two diagram types you need to have this common page definition extend the ToolboxPage meta classes in both profiles! The common page can be located in one of the toolbox page packages, it does not matter which. But it should be visible in the diagrams of both toolbox pages.
  • Make sure you create you profile by right clicking in a toolbox page diagram -> choose Advanced -> Save as profile. (The definitions you wish to include in your profile must be visible in the diagram.) It is not possible to create the profile by right clicking in the browser since the common page can only be located inb one of the toolbox profile folders. It will be missing from one of the toolbox pages if you try to do so. (Unless you move it of course between creation of toolbox profiles. But don't do that. Much easier to use the diagrams.)

/Hans

7
Uml Process / Re: How to use IBD and properties
« on: November 30, 2016, 07:56:15 pm »
To be honest I haven't much experience with interfaces. I just think diagrams get cluttered with "lollipops". I haven't understood what interfaces add that cannot be achieved with ordinary blocks and interface blocks. If you turn to modern architectural frameworks such as the UAFP interfaces are not used.

I think you may have misunderstood my point about item properties. Everything is already in EA 12 (and EA 13). If you define your
properties on a block, item properties can be visualised exactly in the same way as item flows. No specials necessary. Follow these steps:
  • Define one or more flow properties under your block.
  • Create an item flow between two parts of the block.
  • Go to Properties | Tags of the item flow and choose your flow property created under step 1. (Only one item property is allows per item flow, as per the SysML spec.)
  • Add a connector between the parts of the block.
  • Right click the connector and choose Information Flows Realized...
  • Now select your item flows, and the item property will be displayed just lite any item flow.

/Hans

8
Uml Process / Re: How to use IBD and properties
« on: November 29, 2016, 04:50:05 am »
Helmut, I agree on what you wrote, with one exception:

In SysML you can put Flow Properties on the connector and in EA you can only put blocks like classifiers on the connector (Information Flow realized).

EA is actually capable of handling item properties. Look at tagged values of your item flow. There you will be able to assign an item property to the flow. The flow can subsequently be realized by a connector.

(Also, I could live without Interfaces. Why would you want to use them?)

/Hans

9
Automation Interface, Add-Ins and Tools / Achimate, definition vs use
« on: November 06, 2016, 02:25:23 am »
I'm trying to understand how to best use EA for Archimate modeling. Having a solid understanding of SysML, and appreciating the difference between definition and use, I find the Archimate implementation in EA lacks som important features. Say for example that you need to model a business process where one of the business functions appear more the once. This presents a problem in EA since more than one instance of an element on the same diagram is not allowed. This makes perfect sense when modeling SysML since you use call behaviour actions to modell process flows in activity diagrams. However, in the Archimate 3 profile that comes with EA 13 you are supposed to model all diagrams types using "Class diagrams" which is a diagram that is supposed to have elements of definition on them.

My guess is that other Archimate tools allows more than one instance of the same business function on the same diagram. In order to make EA more usable as an Archimate platform should't business processes be modeled in activity diagrams using call behaviour actions?

/Hans (Archimate beginner)

10
General Board / Re: Custom search queries not showing in model view
« on: October 30, 2016, 11:16:44 pm »
Hi Rick,

If you are trying to build model views from SQL-searches, I think you need to include the following two columns in your search:

Code: [Select]
SELECT req.ea_guid AS CLASSGUID, req.Object_Type AS CLASSTYPE, ...
FROM ...

The reason is that the model view list items have icons representing the object type found in the search and since the list items have a context menu which allows you to find the listing in the project browser etc.

/Hans

11
General Board / Re: Where is the 'roadmap' information stored.
« on: October 17, 2016, 03:11:20 am »
Most of the Roadmap information is stored in t_diagram.StyleEx. Look for <SEG></SEG> sections. Information such as background color (@BkgClr=) and size of the segment (@Size=) is set here.

/Hans

12
General Board / Copying ports from one element to another
« on: October 13, 2016, 08:20:57 pm »
Is there a way to copy the ports from one element to another element, without having to copy the entire element. Preferably, I'd like to selectively copy any number of ports from the source element to the target element.

I have tried copying the ports by dragging them from the browser and release them over an element in a diagram. (This is what you can do to copy operations between elements.) Not working for ports. I have tried dragging them within the browser, which allows you to MOVE ports from one element to another. But I haven't found a modifier key to invoke copying instead. I have tried the context meny in the browser efter selecting port to find a copy function that works, but cannot find anything that works.

The only workaround I have found is to copy the whole element containing the port that I wish to use. Then MOVE the port as suggested above. Then finally delete what is left from the copied element. Is there a better way?

/Hans

13
General Board / Re: How do I add reception to a SysML block?
« on: September 13, 2016, 01:57:16 am »
The current version of EA does not provide support for receptions.

You can somewhat create that appearance by creating a stereotyped operation. In SysML blocks must designate whether it makes requests or handles requests for the behavioural features it defines. Hence, you need to set the DirectedFeature stereotype on the operation. Then you can add the additional stereotype 'Signal'. Ideally this keyword should appear after (prov, reqd, or provreqd), but EA cannot do this. Instead the keyword is displayed at the compartment top comma separated like this: «DirectedFeature, signal». Not very nice.

/H

14
General Board / Re: MariaDB ODBC settings
« on: March 28, 2016, 04:17:49 am »
I have used MySQL ODBC Driver 5.1.13 together with several MariaDB instances. As far as I can see it works great. Make sure you don't use the driver version 5.2.x or above. I have had some strange issues using the driver versions above 5.1.13. If I remember correctly Sparx also do not recommend versions above 5.1.13.

/Hans

15
* I then create an IBD for A.  Onto that diagram I can drag, from the browser, part :B as a link.  I can also drag :C, as a link, onto the IBD to the side of :B.   This does not show the nesting, whole-part relationship.

* Alternatively I can drop :C over the rectangle of :B to show the nesting in the IBD.   At this point in the project browser, and on the BDD, the properties for B no longer shows :C. In the project browser :C is shown as a child of :B under block A.  And on the BDD :C is no longer in the properties compartment of B.
You should be very careful when dragging properties from the browser onto an ibd. The ibd displays the internals of a block and should only contain properties owned by that block. Consequently, you may drag properties from the browser onto an ibd the way you did with :A. Alternatively you may right-click on an ibd choose 'Synchronise Structural Elements' if you wish to add to the ibd all properties belonging to the block. Now, the correct way to include nested properties is to right-click on :B, choose 'Structural Elements...', tick the 'Show Owned/Inherited' box, and finally tick the box in front of the nested property.

Can someone explain why nesting the properties on an IBD removes the nested properties from the parent block's "properties" compartment in the BDD?
In EA you can move properties around by dropping them onto other elements in diagrams. This "feature" (or bug) is very dangerous. I would say it is one of those things (among many others) that Sparx should not allow the user to do. If you really would like to move a property from one element to another it is sufficient to enable this operation by drag and drop in the browser.

Pages: [1] 2 3 4