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

Pages: 1 ... 5 6 [7] 8
91
Bugs and Issues / XSD import for release 1006, UML attriibutes only
« on: March 18, 2013, 11:46:14 pm »
I imported several XSD schemas when I had version 9 installed and was able to select Import XSD Elements/Attributes as: Assocations or Attributes, and chose "Assocations".

I have since updated to version 1006.

Leaving the selection as the default "UML Assocations", or even manually selecting it (toggle to UML Attributes, then toggle back), the schemas are imported using the UML Attributes setting.

To make sure I wasn't forgetting someting, I reverted back to version 9.3 and the options behave as expected, showing the nested elements assocated to their parents.

92
Bugs and Issues / FlushRtfLine(B) Ran out of memory
« on: June 15, 2012, 03:13:45 am »
Occurred when trying to save a large (130meg) RTF document that I had imported.

It started out as a 6meg MS-Word Document, but grew considerably when I converted it to an RTF.

93
Thanks Phil, that should work.  We are transitioning from Archimate 1.0 to 2.0, so disabling 1.0 shouldn't be an issue.

94
Bugs and Issues / Re: Archimate 2 bug for creating
« on: May 24, 2012, 11:47:44 pm »
I tried with holding down the ctrl key and explicitly selecting "simple link" and got the same result.  The box version of the device element without the icon in the upper right.

What I've tried:
  • Created a device element using the project browser, mini-icon in project browser is correct.
  • Drag element to diagram (selecting simple link), element shown using rectangular notation, but without an icon in the upper right.
  • Right-click, selected advanced, the option "use rectangular notation" is not in the menu.

Comparing to creating the element using the toolbox:
  • Created a device element using the toolbox.  Everything works as expected. (icon in upper right)
  • Right-click, selected advanced, the option "use rectangular notation" is in the menu, and I can toggle it on and off.
  • Deleted the element from the diagram.
  • Re-added the element back by dragging from the project browser to the diagram.  Everything works as expected (icon in upper right)

Some property mustn't be set when the element is created in the project browser.

95
@Simon M
Yes, I get the correct icon in the project browser.  
I am definitely using the Archimate2 standard.  

I created a small EA script to compare the properties of an Archimate2 device created using the toolbox vs. one created using the project browser.  The have the same type, stereotype, and metatype, so I'm not sure why they display differently.

96
Bugs and Issues / Archimate 2 bug for creating "device" elements
« on: May 23, 2012, 03:59:59 am »
When I create an Archimate2 Device Element using the "create element" feature from the Project browser, the resulting element does displays as a plain box when dragged to a diagram (no icon in the top right).  The option "Advance -> use rectangular notation is also not available"

When I create the element directly in the diagram using the Toolbox, the element does display using as a box with the device icon in the top right.


97
Bugs and Issues / Re: Constraint Status - repeats
« on: May 23, 2012, 11:28:02 pm »
@Paulo, you might get multiple copies of constraints if someone has merged the "reference data" from multiple repositories in to a single repository.  I had something similar happen recently when I was merging two repositories in to a single repository.

98
Bugs and Issues / Re: Project Browser Synchronisation
« on: May 23, 2012, 11:09:15 pm »
@Doug
EA does not auto refresh the project browser.

You can manually refresh a specific package by "Select Package->Right Click->contents->reload package"

You can manually refresh everything in the project browser by "File->Reload Current Project"

99
Bugs and Issues / Re: Keyboard shortcuts missing from Model Search
« on: May 23, 2012, 11:02:51 pm »
@Paolo
I've found EA's shortcut keys to be very limited, so I've started using autohotkey http://www.autohotkey.com/ to create my own shortcutkeys.

I'll try to clean up my .ahk file this week and post for other EA users to use.

100
Bugs and Issues / Archimate 2 / Business Modeling conflict
« on: May 23, 2012, 05:45:28 am »
When creating or viewing an Extended Business Modeling Diagram, EA is incorrectly showing the Archimate2 Structural Concepts Toolbox instead of the Business Modeling Toolbox.

Not critical, but an annoyance when you need to create several of these diagrams.

101
Bugs and Issues / Archimate 2 / Business Modeling conflict
« on: May 23, 2012, 05:29:08 am »
When creating or viewing an Extended Business Modeling Diagram, EA is incorrectly showing the Archimate2 Structural Concepts Toolbox instead of the Business Modeling Toolbox.

Not critical, but an annoyance when you need to create several of these diagrams.

102
Uml Process / Re: modeling conditional business rules
« on: March 09, 2010, 01:40:40 am »
I'm hoping the the EA generated code can be used as part of the testing process.  

E.g given a set of inputs do I get the same outputs from both the component optimized by the developers and the component created from the EA generated code.

The example I gave is pretty simple, but represents the key data anaysis patterns I will be dealing with.

103
Uml Process / Re: modeling conditional business rules
« on: March 06, 2010, 07:10:03 am »
http://www.sparxsystems.com/uml_tool_guide/extending_uml/business_rule_modeling.html

Not all versions of EA have this feature.  I'm using the Business and Software Engineering Edition.

I purchased it specifically to make use of the Rule Composer.   Overall it's worked well, I'm just not sure how to model the examples I posted in a way that will generate useful code.

104
Uml Process / modeling conditional business rules
« on: March 06, 2010, 03:24:24 am »
I'm trying to find an elegant way to model some data quality rules for Meteorological observations (the rules are used to flag that something 'may' be wrong)

Simple range checks are easy.

For example, in Canada the observed temperature should be in general less than 40C, and greater than -55C.  That rule is pretty straight forward, and was easy to model with the Rule Composer in EA.

What I'm trying to model is the more complex checks we do:  customized range check, temporal check, multi-variable check, and spatial check. Ideally in a form that I can generate code from to help with system testing.  

Examples of each additional check:

Customized range check:  The upper and lower limits change depending on the location and time of year.  
E.g. in July the lower limit in Toronto is 10C,   But the lower limit in Regina could be 5C for July

Temporal check:  For the same location: In 1 hour the temperature should only increase or decrease by 6C.  In 2 hours temperature should have changed at least once (check for 'stuck' sensors)

Multi-variable check:  If the present weather sensor is reporting snow the temperature should not be greater than 5C

Spatial Check: The current temperature should not have a greater than +/- 5C difference from any other temperature observations measured within the past 30 minutes within a radius of 50KM and +/- 150m difference in altitude.

I'm going to keep working on this, and if I find a method that works, I'll pass it on.

105
Thanks Simon, I forgot about that option.

Pages: 1 ... 5 6 [7] 8