Workflow - Production of an operational FESA3 Class (Deploy-Unit) at GSI

• Generate a first design draft, in consideration of the FESA Development Guideline
• Arrange a meeting with all necesarry people and present your design-draft. You will need the following participants:
  • Udo Krause or Ludwig Hechler (class functionalities, hardware connection, services and general design)
  • Günter Fröhlich or Susanne Jülicher (property names, middleware interface and class services)
  • Alexander Schwinn or Solveigh Matthies (Fesa3 possibilities, class design, functionalities and code details)
  • The device-expert (hardware connection and device specialities / behaviour)
  • The end-user (interface and needed services)
  • Yourself of course
• After all participants agreed on how the class should look like, write an implementation proposal. This overview should contain information on the following issues:
  • Property - names and services
  • Realtime - actions and dependencies
  • Validation tests of the class (ideally and if possible with the real device (hardware))
  • Any other class-related information that could be relevant
• Send this proposal to all meeting participants (e.g. start on this wiki page: FESAclassDevelopmentSpecificEquipment) and wait for responses/change requests. If some fundamental points are still not agreed/fully understood, a second meeting could be necessarry.
• If everybody gave his/her ok, implementation may be started. You should begin implementation by using the GSIClassTemplate in order to follow the FESA Development Guideline. If any trouble arises you can use the Fesa3 help-sites or directly ask the GSI Fesa-Team for help (phone / email to the Fesa-support mailing list). We will support you on any problems regarding Fesa3. Don't forget to provide a proper documentation for your class: inside the code using doxygen as well as in a seperate document (e.g. Word, OpenOffice, LaTeX).
• You need to obtain a proper device name for your device. For this purpose, please contact Maria Kuehn or Volker RW. Schaa.
• As soon as you finished implementation, the GSI Fesa-Team will review your code and run your validation-Testclass. If any problem is found during review/test, the Fesa team will inform you about it. After you fixed the problem in your code, the whole process is repeated, until the class is fully functional and ready for operation.
• You can install and run your class at an operational frontend. Please also note, that your class will be added to the operational source-code control repository. Per default you will be one of the persons in charge if changes for this class should be needed (FWK-updates, user requests ...).
• To obtain a proper GUI for your class, please contact the LSA-group ( Raphael Müller/ Jutta Fitzek) If you have the feeling that an issue is missing on this list, please report it to the Fesa-Team. We will check if we should add the missing task to the list.