XXXIII Annual Meeting of the Division of Particles y Fields of the Mexican Society of Physics APPLICATION OF A SOFTWARE ENGINEERING METHODOLOGY IN THE CONTROL SYSTEM DESIGN OF A SINGLE DETECTOR IN A HIGH ENERGY PHYSICS (HEP) EXPERIMENT Dr. Juan Carlos Cabanillas Noris Dr. Mario Iván Martínez Hernández Dr. Ildefonso León Monzón Dr. Solangel Rojas Torres May ay 28th, 201 019
CONTENTS DETECTOR CONTROL SYSTEM (DCS) OBJETIVE SYSTEM MODELING IMPORTANT ASPECTS IN DCS DESIGN METHODOLOGY CONCLUSIONS XXXIII RADPyC 2
DETECTOR BEAM/ENV INFO FSM CONTROL BIG SCREEN CONTROL LOG-IN EXPERT TOOLS SETTINGS SOUND SETTINGS SYSTEM (DCS) DETECTOR PANELS ❑ The DCS allows the control, configuration and monitoring FSM OVERVIEW of the elements that integrate FSM TREE BROWSER a High Energy Physics (HEP) experiment. MONITORING ZONE ❑ DCS oversees coordinating of all processes in the CUSTOMIZABLE experiment, according to the AREA FSM EXPERT TOOLS status of the systems and subsystems; AUX ZONE ❑ As well as monitoring data. ❑ Ensures safe, reliable, and uninterrupted operation of the experiment. XXXIII RADPyC 3
DETECTOR CONTROL SYSTEM (DCS) ❑ Serves as an important communication exchange point, providing: a) Data for detector operation b) Physics analysis c) Safety systems d) External services (including the accelerator). XXXIII RADPyC 4
OBJETIVE ❑ Due to the relevance of the previously mentioned is important to: o Develop a standardized methodology to model the design and operation process of a control software. o Using software-engineering techniques. ❑ This proposal uses Rational Unified Process (RUP) to model a control system of a detector considering the: o Workflow of requirements, o Analysis o Coding o Tests for all phases of this model; ❑ Through application of associated UML (Unified Modeling Language) models. XXXIII RADPyC 5
SYSTEM MODELING ❑ This methodology to model a DCS is presented from point of view of the three main actors** (stakeholders) involved in the software development process of this system. ❑ Applying five UML diagrams that contain the essentials of the system development. ❑ It is worth mentioning that the actors that participate in the use cases can be people or subsystems (software, modules, logbook, web browser, etc.). XXXIII RADPyC 6
SYSTEM MODELING ❑ Three main stakeholders defined are: a) Detector Expert (DE) b) Expert of the Central DCS of the Experiment (ECDCS) c) Operator of the Central DCS of the Experiment (OCDCS). ❑ Finally, the models provide insight into system requirements can generate an abstraction to simplify and gather the most important characteristics of this system; ❑ Despite huge conceptual and structural differences between one detector and another. XXXIII RADPyC 7
SYSTEM MODELING Actors / stakeholders: UML Diagrams ▪ Expert in the Detector (ED) ❑ Diagrams / Tables of Use Cases ▪ Expert in the Central DCS (ECDCSC) ❑ Context Diagram ▪ Operator in the Central DCS (OCDCS) ▪ Analysis Model ❑ UML Activity Diagrams For each actor were defined: ▪ Design Model (Static Structures) ▪ General Characteristics ❑ UML Class Diagrams ▪ Requirements Analysis ▪ Dynamic View o Functional → system should do ❑ UML Sequence Diagrams (elements) ❑ State Diagrams o No Functional → system as a whole ❑ Tree Diagrams (Hierarchy of nodes) (Efficiency) XXXIII RADPyC 8
IMPORTANT ASPECTS IN DCS DESIGN Hardware Elements Set up Alarms and User Interfaces and Communication Alarms Help Protocols Finite State Power System SCADA System Machine (FSM) Integration Archiving of Trending plots Requirements of Conditional Data the DCS Detector XXXIII RADPyC 9
General METHODOLOGY Characteristics Actor: Expe pert rt in in the Detector etector (ED) D) XXXIII RADPyC 10
General METHODOLOGY Characteristics Actor: Expert pert of f th the Central ntral DCS S of the Expe peri rimen ment t (ECDC CDCS) S) XXXIII RADPyC 11
General METHODOLOGY Characteristics Actor: Operator erator of f th the Central ntral DCS S of the Expe peri rimen ment t (OCDC CDCS) S) XXXIII RADPyC 12
METHODOLOGY Main Software Requir irem emen ents ts Actor: Expe pert rt in in the Detector etector (ED) D) XXXIII RADPyC 13
METHODOLOGY Main Software Requir irem emen ents ts Actor: Expe pert rt of the Central ntral DCS S of the Expe peri rimen ment t (ECDC CDCS) S) XXXIII RADPyC 14
METHODOLOGY Main Software Requir irem emen ents ts Actor: Operator erator of the Central ntral DCS S of the Expe peri rimen ment t (OCDC CDCS) S) XXXIII RADPyC 15
METHODOLOGY Ac Activities ivities Di Diagram am Actor: Expe pert rt in in the Detector tector (ED) D) Activi ivity y Dia iagram gram of the Use e Case se CU_R _RF01-05: 05: Model the Behavior of the DCS Nodes through Finite State Machine (FSMs) XXXIII RADPyC 16
METHODOLOGY Ac Activities ivities Di Diagram am Actor: Expe pert rt of the Central ntral DCS S of the Expe peri rimen ment t (ECDC CDCS) S) Activity ivity Diagram am of the Use Case e CU_RF02-01: 01: Use software and Tools Updated XXXIII RADPyC 17
METHODOLOGY Ac Activities ivities Di Diagram am Actor: Operator erator of the Central ntral DCS S of the Expe peri rimen ment t (ECDC CDCS) S) Activity ivity Diagram am of the Use Case e CU_RF03-03: 03: Attending Alarms and Help Instructions for Detectors/Subsystems XXXIII RADPyC 18
METHODOLOGY Se Sequenc nce e Diagra ram Actor: Expe pert rt in in the Detector tector (ED) D) Sequenc quence e Diagram am of the Use Case e CU_RF01-05: 05: Model the Behavior of the DCS Nodes through Finite State Machine (FSMs) XXXIII RADPyC 19
METHODOLOGY Se Sequenc nce e Diagra ram Actor: Expe pert rt of the Central ntral DCS S of the Expe peri rimen ment t (ECDC CDCS) S) Sequenc quence e Diagram am of the Use Case e CU_RF02-01: 01: Use software and Tools Updated XXXIII RADPyC 20
METHODOLOGY Se Sequenc nce e Diagra ram Actor: Operator erator of the Central ntral DCS S of the Expe peri rimen ment t (OCDC CDCS) S) Sequenc quence e Diagram am of the Use Case e CU_RF03-03: 03: Attending Alarms and Help Instructions for Detectors/Subsystems XXXIII RADPyC 21
Conclusions ❑ It is important the definition and documentation of the design process, commissioning and operation of a detector control system (DCS) in high- energy experiments in a general way, especially for the staff that initiate in these interest topics (detector on-call, DCS shifters, members of a detector collaboration, etc.). ❑ The design of this methodological analysis of the DCS of the ALICE experiment for what will be LHC Run-3 is being finishing. ❑ This analysis is expected to be applied in the development of the control system for new FDD detector in the new LHC run in ALICE. XXXIII RADPyC 22
Thanks! XXXIII RADPyC 23
Recommend
More recommend
