Equipment software modeling FR1.2-50

1
Equipment software modelingFR1.2-50

• Michel Arruat, Stephen Jackson,
• Jean-Luc Nougaret, Maciej Peryt
• Contributors to FESA
• Accelerators Beams Department, CERN

see WE612 in 2003
see PO2.094-5
2
Outline

• Introduction
• Part one abstraction levels
• Part two findings
• Conclusions

3
Equipment softwares purpose
Interface module
Front-end crate
Timing receiver
CPU
Device
Field bus
Device model
4
Part one abstraction levels

• Climbing the pyramid of abstraction levels for
  modeling equipment-software

5
Equipment modeling
UML
modeling language ?
see WE612 in 2003
6
Equipment meta-modeling
7
A hierarchy of abstraction levels
Equipment specialist
steer
design
code
see MOF OMG
see W3C
8
Part two findings

• Raising abstraction brings concrete
  benefits

9
Modeling in a guided design-space
enforces constraints
validates against
edit interface
edit scheduling
edit actions
edit interactively
see PO2.094-5
10
Modeling frees C developers

• What goes on behind the hood
• Actions triggered according to scheduling rules.
• Devices collected according to sorting criteria.
• Data pushed to clients according to notification
  scheme.

see PO2.094-5
11
Modeling eases database integration
SQL
see PO2.094-5
12
Languages and equipment modeling
Language FESA usage Pros Cons
C Equipment Implementation Flexible and powerful Low-level
UML Framework model Universal Abstract
XML Schema Equipment Meta-Model Flexible for iterations and code-generation. Stretch XML beyond original intent
Data-flow control-flow ? Suits instrumentation Restricted, Performance issues, Graphical barrier
Formal ? Verification Mathematical barrier
13
Conclusions

• Modeling can be useful in embedded systems.
• XML Schemas help elaborate domain-languages.
• FESA has a meta-model of equipment software.