Using the Symbol Editor > Getting Started with the Symbol Editor > Understanding Symbols > Planning a Project for the Symbol Editor

Planning a Project for the Symbol Editor

 INDEX Gray bullet PREVIOUS NEXT

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 are the Key Performance Indicators. Symbols for such an application are graphics heavy and integrate many transformations to add intelligence. However, 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, best practice is to follow the use case shown in Figure 1.3.

images/diasym_symboleditorusecase.png

Figure 1.3 Use case for Creating Symbols
  1. The initial dashboard request is given by a manager.
  2. An application designer designs the application to be created and the symbols that will be needed.
  3. An application designer defines the parameters, constraints, and look and feel for each symbol.
  4. Graphics are created by a graphic designer.
  5. The symbols are created by a symbol designer using the Symbol Editor.
  6. A developer integrates the symbols into an application using the ILOG JViews application.

The application is approved by the application designer and the manager.

Copyright © 1987-2007 ILOG S.A. All rights reserved.   Documentation homepage.    Legal terms. PREVIOUS NEXT