Data Studio Application
Features
 | One button deliverable generates numerous deliverable types in parallel |
| Rapid design of templates to support different job types with numerous deliverable types |
| The Full Deliverable is displayed at all times in a what-you-see-is-what-you-get presentation |
| Fully integrated context sensitive help that instantly displays a description of the current selection |
| Bidirectional help not only shows how to do something, but can also do the function for the user |
| Built upon the Virtual Data Model (VDM) to support multiple data types and graphical output types |
| Self describing tables which allow application to rapidly adjust to schema changes |
| Single Integrated Application replaces legacy applications that I wrote in the past: Log Viewer, Log Manager, Plot Manager, Log Heading, Forms Editor, Dashboard, and Exchange |
| Drag-and-drop editing |
| Fully customizable user interface that allows tool bars to be defined by the user and docking windows customized to the user's preferences |
| Messaging Window provide constant status updates |
| Tabular data editor that can rapidly scroll through millions of data records with thousands of columns |
| User customizable presentation wizard |
| Rapid switching between measured depth, date/time and true vertical depth indices |
| Integrated Help Panel |
| Multiple Versions of the same telemetry data |
Additional Information
| Screen Shot of the Data Studio application. |
| Example of the printed output. |
Video
This video illustrates how Data Studio via
VDM handles different versions of the same telemetry data and how it
automates the splicing of the data for presentations and for creating customer
deliverable data.
Another feature of VDM is its sophisticated data dictionary component which has
non-standard information like short cuts to help information for the columns of
tables and the tables themselves. On the video, watch how the help panel updates
when different items are selected on the application. VDM supports hit testing
which tells the application what table, table column, and table row was hit.
Knowing this information, a request can be made to the data dictionary to find
the help document and the short cut within the document to provide the user help
about the current selection.
It was part of my work ethic to write the help for any new feature in the application. I did this because it was my way of recording the requirements as I understood them. When it was time to test the new feature, the help I wrote would allow me to easily verify the application behaved as I recorded it in the help.
