[DUG] D2005/Architect

[Richard Vowles]

ECO is not modeling.  

It is:
Designtime Support Features 
	Persistence mechanism (RDBMS or XML file) 
	Database configuration 
	Database schema creation/evolution 
	Model validation 
	OCL expression editor 
	Object-relational mapping 
Runtime Support Features 
	Undo/Redo mechanism 
	OCL querying 
	OCL evaluation 
	Caching of objects 
	Subscription mechanism 
	Transaction support 
	Binding to data-aware .NET UI controls 

And even then, that doesn't even come close to indicating how good ECO
is. If I was to leave Borland, I would stiff for the Architect version
of Delphi in an instant. 
---
Richard Vowles
Borland Solutions Architect
DDI: +64-9-9184573, Cell: +64-21-467747
email and IM/MSN: richard.vowles at borland.com
Skype: rvowles

-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On Behalf Of JeremyN at FrontierSoftware.com.au
Sent: Tuesday, 21 June 2005 12:29 p.m.
To: delphi at ns3.123.co.nz
Subject: RE: [DUG] D2005

Well there are actually only 2 differences between the Enterprise and
Architect versions.
ECO and OptimizeIt. If you are not doing any modelling (ie. not using
ECO) then you are wasting your money. 

OptimizeIt is not the greatest profiler in the world (actually it's
pretty ordinary compared to some - AQTime, for instance (which Borland
use)).

> I got architect cos I did't want to downgrade.  
> Most features in the architect only I never use...  

> I think only the real geeks use.  

That's a strange statement. Perhaps there needs to be a book,
"Modelling, just not for geeks anymore!"