1. Decisive Themes, July, 2011 1 JL-1 ARTEMIS Decisive Theme for Integrasys Pedro A. Ruiz Integrasys July, 2011

2. Decisive Themes, July, 2011 2 JL-2 Theme In green our selected themes. I propose a new one (To Be discussed) 2 themerelevance for decisivesocietal relevance Consistent design data communication Modelling for design data communication the need for a fast design process for high quality systems Design for diagnosisUse of models during design to predict, monitor and analyse system behaviour at run-time Effective and efficient improvement of the quality of the system under development Predictable reliability and safety Modelling the security and safety aspects The need for safe and secure systems Simulating and predicting behaviour Models that are usable for simulation ensuring the correct behaviour of the system Evolution through variabilityModels to design the variability derived from evolution of products and tecnologies Tailored solutions to heterogenous client needs

3. Decisive Themes, July, 2011 3 JL-3 WP2: Modeling & Design Frameworks -Integrasys uses formal models as a basis to develop their products, Currently, it is not covered: -Model Analysis of system behaviour at runtime -Back-annotation to models according to system behaviour -Standard mechanisms to improve the products based on the real time behaviour -Other needs: -To handle the evolution of products with high variabilibity (System family): Reusability of models, Improving the production process, adapt design to new tecnologies, platforms and standards 3

4. Decisive Themes, July, 2011 4 JL-4 WP3: Monitoring & Analysis Framework -Techniques to monitor the behaviour of applications -Application specific properties -Usage of Hardware resources 4

5. Decisive Themes, July, 2011 5 JL-5 WP4: Model management and visualization -Tools for the management of models that involve multidisciplinary technologies 5

6. Decisive Themes, July, 2011 6 JL-6 WP5: Design for evolvability Automatic management the models according to: feedback from runtime behaviour New SW or HW platforms introduced New standards New versions 6

7. Decisive Themes, July, 2011 7 JL-7 WP6: Industrial Validation -Model driven evolutionary development a family of product used for real time monitoring and management of telecommunications networks. -Applied to network of different nature, such as wireless infrastructure, satellite networks or TV infrastructures -We need feedback from runtime behaviour -Usability -Resource consumption -Different platforms: PC, Servers, specific equipment for measuring -Bugs -Customization of products to client needs –> Response time is critical -To optimize the products -Evolution and variability of products from models. The combination of the different values of the following factors, lead to a huge number of final products: -Telecommunication domain (A number of potential cases ) -Different network terminals (B) -Measurement equipment (C) -Monitored Communication protocols () -Physical level (D) -Link level (E) -Network level (F) -Management level (G) -Operating systems in servers (L) -Operating Systems in mobiles (M) -Embedded Software platforms (N) -Software platform for servers and PC (P) -User interfaces (Q) -Standards (R) -Worst case of number of products: -A*B*C*D*E*F*G*L*M*N*P*Q*R -Normally the number is lesser due to constraints, that could be expressed as architectural constraint in the models (For instance if we are monitoring a DVB-RCS network, the network equipment, measurement equpment… are restrited ) 7