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

Pages: [1]
1
Uml Process / Re: XML schema key/keyref problem
« on: April 11, 2018, 05:56:12 pm »
 :-\ 11 years later EA still does not support this according to the User Guide - Schema Models.

Modeling Restrictions - these XML Schema constructs cannot be modeled in Enterprise Architect:
- appinfo
- field
- key
- keyref
- notation
- redefine
- selector
- substitutionGroup
- unique

2
I round tripped an example and apparently EA does not support XML Schema 1.1. Generally v1.1 has not been widely adopted. E.g.  .NET does not support XML schema 1.1 (only 1.0).
Some XML frameworks available but all have quite high prices, see:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/c56fb485-cd6e-4bf3-b111-6aaff8c8008d/xsd-11-and-net-frameworks?forum=netfxbcl

In XML 1.0 validations on 'referential integrity' of xml data against an xsd are possible:
one can define a key (either using xsd:key or xsd:unique) and then reference it using an xsd:keyref
However, EA does explicitly not support this. See:
http://www.sparxsystems.com/forums/smf/index.php/topic,6837.0.html

3
Hi,

Does anyone know a way how to model a constraining rule between attributes and elements in Enterprise Architect? More specifically at the moment, I am trying to model conditional required elements in an XSDComplexType, very simpilar to this case here:
https://stackoverflow.com/questions/33504061/conditional-required-elements-in-an-xsd

To address these and other usage scenarios, XML Schema 1.1 provides more expressive constraints through assertions. Assertions are similar to those available in other schema languages such as Schematron and RelaxNG. Other example XSD's here:
http://www.datypic.com/books/defxmlschema/chapter14.html

4
Suggestions and Requests / Re: Business Rules Modelling Support in EA
« on: February 20, 2016, 09:57:42 am »
Unfortunately Sparx doesn't seem to offer a lot in the area of business rules & business decisions. After browsing the whole night I found two links that I'll include underneath. The reason I started was because I wondered if interfacing with tools like Agile Designer (now part of CA) or Hexawise would be possible.

Coarse grained: DMN Decision Models in EA
http://sparxsystems.com/enterprise_architect_user_guide/12.1/business_engineering/decision_models.html
Export possible to CSV + code engineering

Fine grained: Business Rules in EA:
http://www.sparxsystems.com/enterprise_architect_user_guide/12.1/business_engineering/modeling_business_rules.html
NO Export possible to CSV + very limited code engineering capability (only to C++)

5
Suggestions and Requests / Re: "The Decision Model" in EA
« on: February 20, 2016, 09:49:24 am »
Hi,

I was looking for similar functionality. Many BPM practitioners believe that DMN will become as important for automating decisions, as BPMN has become for automating processes.

Simon, if you're interested please read this article to see why this is a next big thing and why EA should want to keep up with it:
http://www.bpm-guide.de/2015/08/23/dmn-camunda/

At the moment EA┤s DMN support
http://sparxsystems.com/enterprise_architect_user_guide/12.1/business_engineering/decision_models.html
does seem very low profile (e.g. I see no possibility to export to reports, csv, limited code engineering support, no way to create testcases).

6
General Board / Re: EA and Use Case 2.0 'Slices'
« on: April 20, 2015, 06:28:53 am »
Hi Ian,

I really enjoyed reading your posting on EA and Use Case 2.0 'Slices'
https://groups.google.com/d/msg/sparx-enterprise-architect-general/UuwnD7m6kcA/kMiG3VtcO0wJ

Did you find a way to deal with Slices/Use Case 2.0 in EA?

As far as I know it's still possible to create a trace from Requirements to Use Cases, but not to any level deeper within UC's (e.g. Requirement to a specific Alternative flow). Very unfortunate for use in a project environment where several people are happy working with ('a kind of'..) User Stories and several others like me would like to take that to another level áby working towards a more Model Based approach in order to create a single truth to be used from several viewpoints/stakeholders.

Any insights on how to deal with this with EA would be welcome. Although for many people in the company I work for EA has a (too) steep learning curve I believe the results of a good approach van be rewarding.

All the best from The Netherlands,
 Huub van Burken

Pages: [1]