Imo, this is not a quality article worthy of submission to HN.
> Instead of a static data model, we build services around a Modeling Engine that is purpose built to change dynamically.
This is one of those abstract sentences that's typical of marketing hype. If you go to their website to try and research the actual concrete details, you get another high-level overview[1] and clicking on a potential whitepaper is walled off by data-entry screen for contact info (email, phone#, etc.)[2].
If those shots are representative of their "dynamic model-based" product, then no, it will not eliminate "spreadsheet hell".
The article is naive about how and why spreadsheets are pervasive and why they will always outpace the speed of IT departments. Ideas such as 4GL, or DSL, or GUI workflow visualizers, or cloud-based tools, etc, etc will not eliminate spreadsheets.
> Instead of a static data model, we build services around a Modeling Engine that is purpose built to change dynamically.
This is one of those abstract sentences that's typical of marketing hype. If you go to their website to try and research the actual concrete details, you get another high-level overview[1] and clicking on a potential whitepaper is walled off by data-entry screen for contact info (email, phone#, etc.)[2].
[1]http://www.aras.com/technology/model-based-soa.aspx [2]http://www.aras.com/plm-software/100063.aspx
Googling around for actual screen shots of their product, I see the typical GUI type of tools for drag&drop flowcharts and process workflow:
http://plmalpha.wordpress.com/2012/05/31/bpm-workflow-serial...
If those shots are representative of their "dynamic model-based" product, then no, it will not eliminate "spreadsheet hell".
The article is naive about how and why spreadsheets are pervasive and why they will always outpace the speed of IT departments. Ideas such as 4GL, or DSL, or GUI workflow visualizers, or cloud-based tools, etc, etc will not eliminate spreadsheets.