Skip to topic | Skip to bottom
Home
Main
Main.RequirementsForFrameworkr1.1 - 30 May 2005 - 14:26 - PrebenGrosboltopic end

Start of topic | Skip to actions
This page provides a summary of high-level requirements for the Execution Framework in the FASE architecture. Below is a rather basic version:

  1. It must transfer the information to/from the Application layer in an implementation neutral way i.e. not depending on a specific choice of language or interprocess communication. The information must include:
    1. Type and name of the task to be executed. The type will be used to indicated the container type e.g. language (C, FORTARN,...) or system (IRAF, MIDAS, ...).
    2. Parameters to be passed on to the task/component to be executed.
    3. Specifications for the execution of the task e.g. synchronous or not, preferred location of execution.
    4. Results produced by the execution must be communicated back to the Application layer.
    5. Status information on how the execution of the task went.
  2. It must schedule an appropriate container which can execute the actually the task/component requested.
  3. It must track the execution status of the container
  4. It must transfer relevant parameters to/from the container/component layer in an implementation neutral way. This includes:
    1. Input parameters required for the execution of the task
    2. Result parameters generated by the task
  5. It must provide a logging mechanism
  6. Events must be supported.
    1. Any task must be able to general events and listen to events produced by other tasks.
    2. Application layer scripts must be able to generate and consume events.
    3. System events will be generated by the Framework when the execution status of tasks is changed.
  7. It must be possible to schedule multiple containers
  8. It must be possible to handle containers which execute multiple components
  9. It must be possible for tasks being executed in one container to use services provided by components associated to other containers.
  10. It must be possible to schedule containers on other systems
  11. Security must be provided so that data and execution of tasks are private if a user wishes so.
  12. Information on the general load on the system should be provided.

Please, add comments below the line

-- PrebenGrosbol - 30 May 2005



to top

You are here: Main > EnvironmentRequirement > RequirementsForFramework

to top

Copyright © 1999-2009 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OPTICON TWiki? Send feedback