1 The CERN project for a common Front-End Software Architecture A. Guerrero (2), J.-J. Gras (2), J.-L. Nougaret (1), M. Ludwig (2), M. Arruat (1), S. Jackson.

Slides:

Advertisements

Similar presentations

© Telelogic AB Modeling DoDAF Compliant Architectures Operational Systems Technical.

Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design 1.

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,

1 Advanced Embedded Systems, BAE 5030 Presentation Topic: Rate Monotonic Analysis By Aswin Ramachandran

Software Reuse SEII-Lecture 28

Design Patterns in Web Programming Nathan Wallace March 2000 Introduction About Me Why listen to me? What am I talking about? Disclaimer Design Patterns.

Sept-Dec w1d21 Third-Generation Information Architecture CMPT 455/826 - Week 1, Day 2 (based on R. Evernden & E. Evernden)

Unified theory of software evolution Reengineering – Business process reengineering and software reengineering BPR model – Business definition, process.

Nadia Ranaldo - Eugenio Zimeo Department of Engineering University of Sannio – Benevento – Italy 2008 ProActive and GCM User Group Orchestrating.

ROI When Web Content Management Meets Knowledge Management

Architectural Investigation of XCTL by URCA Miloš Cvetanović, Dragan Bojić Faculty of Electrical Engineering University of Belgrade {cmilos,

FESA Vs 2.0 AB/CO TC - 12 Feb July 2004 FECOMSA FESA2 2.0β.

Introduction To System Analysis and Design

ATSN 2009 Towards an Extensible Agent-based Middleware for Sensor Networks and RFID Systems Dirk Bade University of Hamburg, Germany.

Modeling and Validation Victor R. Basili University of Maryland 27 September 1999.

Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Design Patterns.

Vrije Universiteit amsterdamPostacademische Cursus Informatie Technologie Themes and Variations abstraction -- the object metaphor modeling -- understanding.

SwE 313 Introduction to Rational Unified Process (RUP)

Vakgroep Informatietechnologie – Breedbandcommunicatienetwerken (IBCN) Dynamic and generic workflows in.NET Bart De Smet.

Page 1 Building Reliable Component-based Systems Chapter 17 - Architectural Support for Reuse Chapter 17 Architectural Support for Reuse.

PRESENTED BY SANGEETA MEHTA EECS810 UNIVERSITY OF KANSAS OCTOBER 2008 Design Patterns.

1 An introduction to design patterns Based on material produced by John Vlissides and Douglas C. Schmidt.

Accelerator Complex Controls Renovation, LHC Excluded Purpose and Scope M.Vanden Eynden on behalf of the AB/CO Group.

Intranets Lessons from Global Experiences J Satyanarayana Chief Executive Officer National Institute for Smart Government Hyderabad, India.

New Task Group CRIS Architecture & Development Maximilian Stempfhuber RWTH Aachen University Library

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.

The Rational Unified Process

“Enhancing Reuse with Information Hiding” ITT Proceedings of the Workshop on Reusability in Programming, 1983 Reprinted in Software Reusability, Volume.

REVIEW OF NA61 SOFTWRE UPGRADE PROPOSAL. Mandate The NA61 experiment is contemplating to rewrite its fortran software in modern technology and are requesting.

Mihir Daptardar Software Engineering 577b Center for Systems and Software Engineering (CSSE) Viterbi School of Engineering 1.

Introduction To System Analysis and Design

Log analysis in the accelerator sector Steen Jensen, BE-CO-DO.

© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.

© ABB Group October 24, 2015 | Slide 1 Dynamic Software Updates for Real-Time Systems Michael Wahler, Stefan Richter, Manuel Oriol Michael Wahler, ABB.

The Roadmap to Software Factories Tools, Patterns and Frameworks.

Rational Unified Process Fundamentals Module 5: Implementing RUP.

LHC Cryogenics Control: INTEGRATION OF THE INDUSTRIAL CONTROLS (UNICOS) AND FRONT-END SOFTWARE ARCHITECTURE (FESA) APPLICATIONS Enrique BLANCO Controls.

Design Patterns Introduction General and reusable solutions to common problems in software design SoftUni Team Software University

Abstraction CMPS Abstraction Abstraction mechanisms are techniques to deal with creating, understanding and managing complex systems Abstraction.

1/26 On-demand Learning Series Software Engineering of Web Application - Object-Oriented Development & UML Hunan University, Software School.

1 UP MBT Extending the Unified Process with Model-Based Testing Fabrice Bouquet, Stéphane Debricon, Bruno Legeard and Jean-Daniel Nicolet MoDeV 2 a 2006.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14Slide 1 Chapter 14 Design with Reuse.

SOFTWARE DESIGN AND ARCHITECTURE LECTURE 13. Review Shared Data Software Architectures – Black board Style architecture.

SCHOOL OF ELECTRICAL AND COMPUTER ENGINEERING | SCHOOL OF COMPUTER SCIENCE | GEORGIA INSTITUTE OF TECHNOLOGY MANIFOLD Manifold Execution Model and System.

OBJECT ORIENTED AND FUNCTION ORIENTED DESIGN 1 Chapter 6.

Abstract A Structured Approach for Modular Design: A Plug and Play Middleware for Sensory Modules, Actuation Platforms, Task Descriptions and Implementations.

Security Patterns Template and Tutorial - Darrell M. Kienzle, Ph.D., Matthew C. Elder, Ph.D., David S. Tyree, James Edwards-Hewitt Presented by Dan Frohlich.

FESA FRONT-END SOFTWARE ARCHITECTURE [FESA] Michel Arruat, Leandro Fernandez, Stephen Jackson, Frank Locci, Jean-Luc Nougaret, Maciej Peryt, Anastasiya.

1 2.1 Software Engineering Software engineering is a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software;

SOFTWARE DESIGN AND ARCHITECTURE LECTURE 15. Review Interaction-Oriented Software Architectures – MVC.

PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)

HYBRID APPROACH TO INTERFACE ADAPTATION.  Computing power anywhere and everywhere  Need interfaces that can adapt to different device conditions and.

Rational Unified Process Fundamentals Module 5: Implementing Rational Unified Process Rational Unified Process Fundamentals Module 5: Implementing Rational.

BE – RF CLEX TBM Cooling System Software Perspective (DAQ and analysis) A. Zelios, BE - RF1 A. Zelios A. Vamvakas.

Online Software November 10, 2009 Infrastructure Overview Luciano Orsini, Roland Moser Invited Talk at SuperB ETD-Online Status Review.

Outline Object-Oriented Concepts Modeling Components Structured Method Evaluation Procedure Object-Oriented Methods Structured Methods Review of Object.

Modeling of Service Oriented Architecture: From Business Process to Service Realization Petr Weiss and Marek Rychlý Brno University of Technology, Faculty.

FESA Overview Leandro Fernandez On behalf of the FESA Team 6/22/2010FESA Overview1.

Software Development Framework

CHaRy Software Synthesis for Hard Real-Time Systems

Design Patterns: MORE Examples

The Five Secrets of Project Scheduling A PMO Approach

State pattern – A logical ‘Finite State Machine’

1.Introduction to Rational Unified Process (RUP)

FESA evolution and the vision for Front-End Software

Designing Software for Ease of Extension and Contraction

Possible Topics: Real-Time Scheduling

CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE

Chapter 7 –Implementation Issues

Presentation transcript:

1 The CERN project for a common Front-End Software Architecture A. Guerrero (2), J.-J. Gras (2), J.-L. Nougaret (1), M. Ludwig (2), M. Arruat (1), S. Jackson (2) CERN (1) Accelerator & Beams Division / Control Group / FE&C (2) Accelerator & Beams Division / Beam instrumentation Group

2 CERN Front-end software architecture Outline 1.FESA framework project presentation 2.Model 3.Method & Software tools

3 1. Project A framework to rationalize front-end software development…

4 CERN Front-end software architecture Front-end software role On-demand updates RT reflect each-other

5 CERN Front-end software architecture Front-end software framework  Motivation  Overcome diversity of front-end software that emerged over many years.  Homogenize equipment software development as part of a organizational structure change (all accelerators managed by a single division).  Abstract common layer to hide some accelerator discrepancies.

6 CERN Front-end software architecture Front-end software framework  Objective  Encapsulate recurrent aspects of FE-software development as reusable code to be tailored on a case-by-case basis (beyond pattern & templates)

7 2. Model Overcoming front-end software diversity through abstraction…

8 CERN Front-end software architecture Static view FesaEventSourceFesaAction FesaServerAction ConcreteServerActionConcreteRtAction 10..n clone0..n FesaDevice ConcreteDevice FesaRtAction ConcreteScheduler 0..1 listens to triggering 0..* orchestrates FesaScheduler consuming producing FesaEvent FesaSubscriptionEventSource FesaRequestEventSource FesaRtEventSource FesaSubscriptionEvent FesaRequestEvent FesaRtEvent

9 CERN Front-end software architecture EventSourceSchedulerActionDevice Dynamic view Event produces consume access for ever execute( event *) device loop fesaWaitEvent() apply scheduling algorithm access context (optional)

10 3. Method State equipment-software specification in standard-form and rely on productivity tools…

11 CERN Front-end software architecture Workflow

12 CERN Front-end software architecture Conclusions  Work in progress…  Already adopted by instrumentation specialists.  Will be applied to new equipment software development.  More work ahead on device-data model, communications and tools.  … that brings short-term benefits…  Modern OO environment for front-end software programming.  Share knowledge on front-end programming and make it explicit.  Encapsulate some tedious, recurrent programming tasks.  … and long-term prospects…  Ease maintenance by structuring equipment-specialist code.  Infrastructure and specialist code evolve independently.  Pave the way for formal analysis of real-time software.