|
 |
|
|
| DeviceSQL Starter Applications |
| The DeviceSQL™ Framework includes a collection user-extensible application components and interface modules. These DeviceSQL source code components can be combined and extended to simplify and accelerate development of many common device data management applications. Key features of DeviceSQL Starter Applications include: |
|
| With DeviceSQL, companies gain a competitive edge in the creation and delivery of superior products, innovative services, new business models and more compelling user experiences all while: |
|
 |
Common data and interface model (with APIs) to manage many types of data for many common types of applications (see potential applications list below) |
|
Flexibility to extend APIs or remove them entirely and have applications interface directly to the common component layer (Common Application Foundation) |
|
An equivalent of 10,000 lines of C source code featuring common data schemas, functions and interfaces to simplify data element configuration and use |
|
|
| Data storage elements within the DeviceSQL Starter Applications include: |
|
|
Actions (as associated with events, contacts, tasks and status) |
 |
Application information (such as name and title) |
|
Contact information (such as name, phone, fax and email) |
|
Events (such as name, timestamp, type, tasks and status) |
|
Messages (as associated with an application, contact and device) |
|
Preferences (such as application settings, device configuration, contact preferences, and metadata-enabled so data can be dynamic or static) |
|
|
| DeviceSQL Starter Applications can be configured to provide an application foundation that is divided into three separate layers: Application Layer: Creates the communication layer between the application and the data management API. The application layer (typically the control logic) controls the flow and feel of the entire application. The application layer typically handles the user input, output, overall control, startup, shutdown, non-data management activities and gives meaning to the underlying data. API Layer: The purpose of this layer to control re-entry into the data management layer. It interacts with the logging, tracing and remote calls (RPC) as well as database to object conversion. Foundation Layer: The functionality of the system is derived from DeviceSQL. The foundation layer provides for enhanced application portability by handling this data management functionality, including the relational data model and logic for the various modules. DeviceSQL Starter Applications provide extensible building blocks for the following types of applications: |
|
|
Address book |
|
Application trees (relating one application to another) |
|
Calendar |
|
Contact trees (relating one contact to another) |
|
Contact/Application trees (relating one contact to an application) |
|
Device phone book |
|
Device configuration information |
|
Intelligent device/application walkthroughs based on messages/sequences |
|
Message storage and retrieval |
|
Scheduler for system activities such as maintenance, backups, restores, firmware updates, etc. |
|
Step-by-step guides |
|
Tip-of-the-day |
|
To Do lists per device or contact |
|
Triggered Messages: |
| |
| – |
by date/time |
| – |
by input |
| – |
by state |
| – |
Triggered until dismissed (acknowledged) |
| – |
Triggered only once |
|
|
|
|
|
|
|
|
|
|
