What is coming up in EA 5.0?

[Bruno.Cossi]

Hi,

could someone from Sparx outline what is coming up in the next major release of EA, the 5.0? The few things mentioned here in the forum have been most interesting, and I am sure I am not the only one who would love to learn more!

Thanks,
Bruno

[AshK]

Hi Bruno,

I can give you a quick (and rather informal) overview of what's comming up:

- Model Level Transformations:  allowing the creation/mapping of PSM (Platform Specific Models) from PSI (Plaform Independent).  Eg PIM to DLL, PIM to Java, PIM to C#, XSD, DDL.  The mapping for each transform are highly customisable (similar to the code generation templates) allowing for custom user transforms.
- Comprehensive WYSIWYG RTF Report Writer
- Baseline support:  Store a model branch as compressed XMI as a baseline within a model.
- Model package diff tool:  Using the baseline functionality to compare stored baselines with the current model.
- Version control enhancements
- Import of .Net binary files (.exe, .dll, .il...etc)
- Element colour highlighting based on customisable requirement status types.
- Reverse engineering of Oracle and SQL server stored proceedures
- Various improvements to the UI, code generation, XSD generation, and XMI I/O.

If I think of any more I'll be sure to add them.  

Ashley

[mikewhit]

And of course, fixes for all known bugs !!

[Bruno.Cossi]

Thanks Ashley, that sounds great! :-)

Hi Bruno,

I can give you a quick (and rather informal) overview of what's comming up:

- Model Level Transformations:  allowing the creation/mapping of PSM (Platform Specific Models) from PSI (Plaform Independent).  Eg PIM to DLL, PIM to Java, PIM to C#, XSD, DDL.  The mapping for each transform are highly customisable (similar to the code generation templates) allowing for custom user transforms.
- Comprehensive WYSIWYG RTF Report Writer
- Baseline support:  Store a model branch as compressed XMI as a baseline within a model.
- Model package diff tool:  Using the baseline functionality to compare stored baselines with the current model.
- Version control enhancements
- Import of .Net binary files (.exe, .dll, .il...etc)
- Element colour highlighting based on customisable requirement status types.
- Reverse engineering of Oracle and SQL server stored proceedures
- Various improvements to the UI, code generation, XSD generation, and XMI I/O.

If I think of any more I'll be sure to add them.  

Ashley

[Bruno.Cossi]

It just struck me - this could probably be used for the transformation of conceptual/logical database models to the physical ones and vice versa. Something the database modellers on this site have been asking for. Great!

Model Level Transformations:  allowing the creation/mapping of PSM (Platform Specific Models) from PSI (Plaform Independent).  Eg PIM to DLL, PIM to Java, PIM to C#, XSD, DDL.  The mapping for each transform are highly customisable (similar to the code generation templates) allowing for custom user transforms.

[michael_rainwater]

Wow.  That is awesome stuff.  I am definitely excited.

[Eve]

It just struck me - this could probably be used for the transformation of conceptual/logical database models to the physical ones and vice versa. Something the database modellers on this site have been asking for. Great!

It definately could.  With the transformations that will be included from the start, you will be able to create from the one model, a DDL model, XSD model, java/ejb models.  Each of which could then be used to generate code (sql script/xsd schema/code).

What it really does is brings EA into the world of MDA.

Simon

[Paolo F Cantoni]

It definitely could.  With the transformations that will be included from the start, you will be able to create from the one model, a DDL model, XSD model, java/ejb models.  Each of which could then be used to generate code (sql script/xsd schema/code).

What it really does is brings EA into the world of MDA.

Simon

Simon, I would have prefered "It definitely WILL"  

Now, from the DDL model, will we be able to generate a SQL Server physical model, and an Oracle physical model (ala Embarcadero ER/Studio)?

Paolo

[Eve]

Simon, I would have prefered "It definitely WILL"  

Now, from the DDL model, will we be able to generate a SQL Server physical model, and an Oracle physical model (ala Embarcadero ER/Studio)?

Paolo

I would prefer "It definately WILL" too.  But what I said was correct.  Unfortunately, I can't see into the future.  So while I know that it could be used for that, I can't say for certain that it definately will.  The difference is up to you.

As for then transforming that to SQL Server/Oracle physical models... Well, I don't know anything about them.  But my answer would be that if you are currently able to model them in EA, they share common information with the DDL model and you are willing to write the necessary transformation templates then yes, you should be able to.

If you do, make sure that you post them to http://www.eausergroup.org/ so that everyone can benifit from them and help you improve them.

Simon

[Bruno.Cossi]

Hmm... in my world, DDL model equals database physical model. In fact, DDL scripts are an outcome of the physical model.
Sounds like DDL model means something else to you, Paolo. Am I mistaken?

Thanks,
Bruno

Simon, I would have prefered "It definitely WILL"  

Now, from the DDL model, will we be able to generate a SQL Server physical model, and an Oracle physical model (ala Embarcadero ER/Studio)?

Paolo

[Paolo F Cantoni]

Hmm... in my world, DDL model equals database physical model. In fact, DDL scripts are an outcome of the physical model.
Sounds like DDL model means something else to you, Paolo. Am I mistaken?

Thanks,
Bruno

Yes Bruno, it was a slip of the mind  

However, I don't think it's a good idea to cal it a DDL model.  It's the physical DB model.  DDL is only the syntax we MIGHT use to communicate with the DB.  As you say, an outcome...  One might also generate XML to communicate with the DB.

That having been said, I think there's still an issue I'd like clarifed by the Sparxians...

I have a conceptual model (composed of normal classes) I have a logical model (composed of entities) and a physical model (composed of tables) and a physical DB.  I need to be able to move seamlessly between all four environments.

With Embarcadero I can move relatively seamlessly between the last three ( for many, but not all DBMSs).

Actually, my metamodel is a bit more complicated than that, but if EA can do that much, that woud be great!

Paolo

[Eve]

What you should find is that you will be able to have all three models represented in EA at the one time.  The restriction that I currently see is that changes must be made to one model (probably your conceptual model) and then transformations done do update the other models.  (Changes need to be always propogated from a single source.)

Simon

[molla]

The feature I'm looking for is the WYSIWYG editor. I use EA to produce a lot of documentation to be used for peer reviews. (Yeah, we still use those instead of a Web-based documentation, since it's easier to find time to review documents for instance when you're travelling)

[Paolo F Cantoni]

What you should find is that you will be able to have all three models represented in EA at the one time.  The restriction that I currently see is that changes must be made to one model (probably your conceptual model) and then transformations done do update the other models.  (Changes need to be always propogated from a single source.)

Simon

Sounds great Simon!    Look forward to giving it a try!

Naturally, I totally endorse your point about propagating from a single source    - which was, in fact, the reason for my question.

Paolo

[ocomsoft]

Does this mean that from a single diagram I can generate basic Data Classes (ie Hibernate or EJB even NHibernate) ?

With XDoclet attributes ?

What about Basic JSP pages which List and Edit the data class?

Regards

Scott Warren