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

Pages: [1] 2 3 4
General Board / Re: generate JSON attributes with the schema composer
« on: April 18, 2017, 12:12:06 am »
Found the info I needed on pages 16-17 in this document:

General Board / Re: generate JSON attributes with the schema composer
« on: April 01, 2017, 10:31:34 pm »
Additional question:
- the schema composer generates JSON schemas with properties (class attributes) ordered by name. Is there a way to preserve the order of the properties - e.g. the order to be the same as the order of the class attributes in the class model?

General Board / generate JSON attributes with the schema composer
« on: April 01, 2017, 08:43:40 pm »
Hello All,

the schema composer generates JSON properties from a class model as follows:
- JSON property name = attribute name
- JSON property type = attribute type
- JSON property description = attribute description

Question: can the schema composer generate JSON attributes minLength, maxLength, pattern, format? How to specify these attributes in the class model?

Many thanks,


Suggestions and Requests / Re: Support for ISO20022
« on: November 23, 2015, 01:21:59 pm »

Yes, the links work now. Thank you.


Suggestions and Requests / Re: Support for ISO20022
« on: November 19, 2015, 11:33:12 am »
I did get an in principle approval for starting work on this. But I can't see anything being done here until 12.1 is out of beta.

Simon, thanks for the update. I am able to contribute with validation of use cases & requirements, and likely can help to organise a pilot in an FI, if you are interested.

Suggestions and Requests / Re: Support for ISO20022
« on: November 19, 2015, 11:01:01 am »

I am interested to see what's at the links, but unfortunately they do not open for me. Linkedin says "page not found". Can you post here as attachments perhaps?

Thanks, Alex.

Suggestions and Requests / Re: Support for ISO20022
« on: October 08, 2015, 12:39:48 am »
Yes, support for NIEM is a good example. I have had no need to use NIEM in my projects yet, but based on the videos published by Sparx Systems it looks like the recent versions of EA allow to manage full project lifecycle starting from importing of NIEM published repository and then progressing all the way to generating XML schemas through modelling and model transformations in Sparx EA. I think the level of adoption of ISO20022 in the financial industry has already passed the tipping point, hence my advice to Sparx Systems to pay as much attention to it as they do to NIEM recently.

The ISO 20022 standard books define in detail what ISO 20022 compatible tool should be capable to do.

In short, this should include some or all of the following:
- support for ISO 20022 meta-model
- implementing ISO 20022 UML profile
- ability to import the ISO 20022 published repository,
- forward model transformations between model levels and traceability between levels, as defined in the ISO 20022 metamodel
- ability to generate XML Schemas as per the standard
- ability to reverse-engineer existing XML schemas back into the model
- ability to do round-trip - e.g. reverse-engineer, update message definitions in the model, and forward engineer into ISO 20022 compatible message Schema variant
- ability to export the repository/model in ISO 20022 meta-model XMI (e.g. in the format as currently used for publishing of the ISO 20022 repository on ISO20022 web site

Suggestions and Requests / Support for ISO20022
« on: October 07, 2015, 06:37:03 am »
ISO20022 is number one standard in the financial industry, it is time to implement support for it too!

Suggestions and Requests / Re: Add 'Show InformationFlow <<flow>> Lab
« on: December 01, 2015, 07:10:45 am »
Thank you, smendonc.

Suggestions and Requests / Re: Add 'Show InformationFlow
« on: December 01, 2015, 01:44:58 am »
I do not impose anything on anyone. I suggest a convenience feature that (a) will allow to achieve something, that I already can achieve in Sparx EA, but with less hassle and (b) will make Sparx EA to appear more useful and Sparx UI features more consistent from perspective of a wide customer segment (think new licence buyers) who do not know UML well enough to tell a difference between stereotype of a connector and <<flow>> label of an InformationFlow.

Suggestions and Requests / Re: Add 'Show InformationFlow <<flow>> Lab
« on: November 30, 2015, 11:25:07 pm »
Hi Paolo, I do not disagree with Thomas nor with you. Seems however the world you model is more complicated than the one I am talking about here, and this causes misunderstanding. I will make another attempt to explain.

Information Flow is the only relationship concept in the DSL I am talking about. Nothing needs to be done to implement this DSL in Sparx EA.  The diagrams are understood consistently without special labels,  stereotypes, MDG, etc.
The <<flow>> labels is the only issue - need to hide them one by one.

Suggestions and Requests / Re: Add 'Show InformationFlow
« on: November 29, 2015, 10:21:12 pm »
Whether it is bad idea or not depends on context where/how the tool is used. In your context it might be bad (and I am perfectly fine with that), in my context hidden <<flow>> labels is exactly what is often needed and it makes a lot of difference!
Imagine a diagram with 10 elements and 20 flows connectors and _only_ flow connectors in it. You present this diagram to an audience that does not expect any connectors other than flows. Having <<flow>> labels in such diagram causes only nuisance -- the labels clutter the diagram and distract the audience. Someone in the audience usually picks on the labels and asks what they are for? And you need to explain that this is the tool that forces the labels to be there... And then someone picks on subject of tools and so it goes on distracting from the subject of the presentation. And if someone mentions that this is actually a UML tool and that <flow>> is a standard representation of an abstract concept called InformationFlow that in this diagram we mean what you (in the meeting) understand anyway... it is almost guaranteed that by that time majority of normal people out there in the offices (not the UML nerds in this forum) will be already confused to the extend that ruins the meeting.  And you think hey I'd better remove these labels next time. So, in such context hiding these labels is actually a very good idea.
Hopefully this explanation is convincing enough? :)

Suggestions and Requests / Re: Add 'Show InformationFlow
« on: November 29, 2015, 08:00:19 pm »
Following your logic, not showing a stereotype label on a connector makes it to appear as something completely different too. Sparx EA however supports 2 ways already that allow to hide connector stereotype labels.

So, I would suggest that whether to use hiding of labels or not is a different subject for discussion, and of course a modeller need to be careful not to confuse the reader.  

Suggestions and Requests / Add 'Show InformationFlow <<flow>> Lab
« on: November 29, 2015, 09:16:15 am »
Feature Diagram > Properties > Connectors > Show Stereotype Labels does not work on InformationFlow connectors - I guess this is because InformationFlow is NOT a stereotype.

The <<flow>> labels however often need to be removed to reduce clutter in diagrams. At present, I am forced to hide the labels one by one with Hide Label from the context menu on right click on a label.

Suggest to add feature Diagram -> Properties -> Connectors -> Show InformationFlow <<flow>> Labels, in "checked" state by default.

Thanks, Geert.

Have just submitted.

Pages: [1] 2 3 4