Before creating a symbol, you must know what sort of
application a symbol will be used for. For example, a BAM application
will present only small amounts of specific data that is updated infrequently.
An example of this data is the Key Performance Indicators. Symbols
for such an application are graphics heavy and integrate many transformations
to add intelligence. On the contrary, a SCADA application will use
hundreds of symbols to present enormous amounts of data that is updated
in real time. In this case, it is essential to create light symbols
with as small a memory footprint as possible.
To ensure that you produce symbols that match your application
requirements, the best practice is to follow the use case shown in
the following figure.
A manager issues the initial dashboard
request.
An application designer designs the
application to be created and the symbols that will be needed.
An application designer defines the
parameters, constraints, and look and feel for each symbol.
A graphic designer creates the graphics.
A symbol designer creates the symbols
with the Symbol Editor.
A developer integrates the symbols into
an application using the Rogue Wave JViews
application.
The application is approved by the application designer
and the manager.