Anne,
Enterprise level models often lack the detail your developers required to
buld/automate. Typically you would implement a lower level physical data model
and the tooling .Net/Java ide's can attatch to this use the metadata to build
objects.
As a basic example, you might have Customer as a single Entity in the
Enteprise model but actually implement a Customer schema with say 5 tables.
The tooling would see these tables and produce classes/method stubs etc.
You might also consider looking at converting a database schema to an XML
schema for similar purposes.
Regards
George
"annegian" <annegian@xxxxxxxxx> wrote:
> I'm responsible for enterprise level data models, which in turn are
> used to build common business objects. The technical architect was
> curious whether there was any automated support.
>
> Any clue where I should start looking? Is the XML export file of any
> value to me?
>
> thanks,
> anne
>
>
>
>
> To subscribe, send an email to:
> ERWin-DB-Modeling-subscribe@xxxxxxxxxxxxxxx
>
> To unsubscribe, send an email to:
> ERWin-DB-Modeling-unsubscribe@xxxxxxxxxxxxxxx
>
> Archives: http://groups.yahoo.com/group/ERWin-DB-Modeling/messages
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
George.
To subscribe, send an email to:
ERWin-DB-Modeling-subscribe@xxxxxxxxxxxxxxx
To unsubscribe, send an email to:
ERWin-DB-Modeling-unsubscribe@xxxxxxxxxxxxxxx
Archives: http://groups.yahoo.com/group/ERWin-DB-Modeling/messages
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ERWin-DB-Modeling/
<*> To unsubscribe from this group, send an email to:
ERWin-DB-Modeling-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|
