Eclipse Community Forums: DTP » DTP Consolidation Face-to-Face meetings: Day 1 and 2 summary

Help

Home

Home » Eclipse Projects » DTP » DTP Consolidation Face-to-Face meetings: Day 1 and 2 summary

Show: Today's Messages :: Show Polls :: Message Navigator

DTP Consolidation Face-to-Face meetings: Day 1 and 2 summary [message #200]

Thu, 28 April 2005 03:45

Eclipse User

Originally posted by: john.graham.sybase.com

Around twenty people representing seven companies have been hard at work the
past two days in the DTP consolidation face-to-face meeting. Concentrating
on offers for inclusion in DTP from a number of sources, the goal of this
meeting is to come away with an understanding of how existing Eclipse
projects -- WTP and BIRT -- along with offers from Sybase and ObjectNation
will merge tooling and effort to provide a best-of-breed data tooling
platform for Eclipse. We are very happy with the progress made in these two
days, and look forward to posting detailed consolidation plans for community
review. For now, while we collect and collate the various notes from the
meetings, I'd like to share some of the results from the first day's
discussions. The idea was to start with use cases and requirements for DTP,
to insure that we all share the same high-level vision and for structuring
the more detailed proposals to follow. (Special thanks to Sheila Sholars for
taking notes and providing them to the rest of the group!)

** We agreed that DTP would follow a model-driven approach to its problem
domains. These models, based on Eclipse EMF, will be vender neutral,
extensible, and provide for a consistent view of domain data. The enables
important capabilities such as online/offline usage, on-demand loading and
so on. **

General Themes/Requirements
-------------------------------

> Generic connection support and management (Including, but not limited to,
> database)
> Run time support for use in RCP and outside Eclipse entirely
> Model type extensibility support
> Model transformation extensibility support
> Model structure-based interaction, both online and offline
> On-demand loading of model content

Users (relative priority)
-----------------------

> Other Eclipse component developers (1)
> Developers
Java application developer (2)
Enterprise application developer
Application architect (modeling, use-case construction, etc)
> DBA
> Report writer/business domain experts (3)
> Application architect
> Data architect

General Use Cases/Requirements
---------------------------------
> Design query against generic connection, read, generate generic report
> <BIRT>
User: Java application developer incorporating reports into
application; Report developer (e.g. generate sales reports)
> Create, edit, debug, deploy server component (e.g. Stored procedures,
> functions, .) <relational database>
> Acquire, modify, write, validate metadata from data source
> Query Support: Create, edit, visualize, debug, execute sql query
> Working with live view
Change database table
Add index
Inspect data
> Lightweight administration
User: Non-operational (for developers as opposed to DBA)
Extensible
Limited to well-defined interfaces (e.g. JDBC)
> Obtain/discover capability metadata from a data source
User: BIRT

SQL Development Tools Use Cases/Requirements
---------------------------------------------------
> Use connectivity project components
> Associate query with connection
> Create, edit, debug/execute, deploy SQL Statements
> Use common SQL Query Model/Parser
User: SQL Query Tooling
SQL execution plan support
Retrieval, visualization
Extensibility for optimization
Support runtime parameterization
Complex parameters
> Team support
Q: how to persist SQL statements w/ associated connection
> Extensible persistence mechanism
> Multiple SQL statement support
> Create, edit, debug, save, deploy, etc of procedural objects
> SQL History view
> Result set support
Model : SDO
UI: extensible, handle vendor-specific data types
Edit in place, reapply to database
Handle large data sets
Persist data results
Multiple result set support
> Visual Query Builder
Modular/componentized (e.g. separate components for Expression
Builder, Conditions Builder, Joins Builder)
Consider novice and experienced user
> Debug Support
Vendor-neutral framework
Multi-language support (SQL, Java)
Extensible for debug support
Extensible for UI presentation

Report message to a moderator