Messages

1

Automation Interface, Add-Ins and Tools / Re: How utilize EA models in development process

« on: March 09, 2021, 11:37:05 pm »

thanks qwerty and Geert,

- Logical data model => compare and transform to physical database model (using Database Transformer addin) => generate DDL code for database (standard DDL transformation)
- Canonical XML schema model => message XML schema model (using schema composer + Message Composer add-in) => XSD code (standard XSD generation)
- Canonical Logical data model (UPCC3) => message model (using schema composer + Message Composer add-in) => XSD code (using Vienna.Be addin)

These processes are using in actual production systems, but they all required a significant investment in the tooling (which is good for me of course

These are exactly the things which I have done in my past with the help of EA models + plugins and therefore I was eager to learn if there are any tooling for swagger and JSON.
It is a bummer that we would loose a lot of information from our domain model since we have already a lot of things done within EA models like aliases which act as translations between documentation language and implementation.

Sine some kind of a JSON export option exists + VS paste JSON as classes, I will utilize that one as a one time option when moving from design to implementation.
And perhaps will import DDL from deployed Entity Framework model back to EA when first implementation phase is over.

2

Automation Interface, Add-Ins and Tools / How utilize EA models in development process

« on: March 05, 2021, 12:05:15 am »

I am total newbie with EA have done few illustrations several years ago without any linking or automation what so ever.
As I understood there are more efficient ways to get more out from EA therefore I

As .NET developer my workflow has been something like this.

(Reverse Engineer from DB) --> C# Classes --> EF code First model with migrations --> Web API --> Swagger (OpenAPI)
Benefits of this approach is that I can do a change in one place and it is reflected from design to documentation
Now I would like to add EA as a part of this toolset while doing a greenfield project so that when I create a design document I could generate implementation based on it OR should I just put in the development effort and just import the results for documentation purposes

EA Model --> DB Model And Swagger

How would you create such a workflow? And what plugins or extensions one would need for that?
Are there any decent tutorials regarding this have found some but not really useful or up to date?

Few examples:
EA Model --> Generate Json --> Paste as Classes in Visual Studio + current work flow
OR
EA Model --> Interface --> Swagger (OpenAPI) --> Reverse engineer a client classes from swagger