GUI for development of REMES models REMES GUI

GUI for development of REMES models REMES GUI group 08 -11 -05 1

Summary of contents • What is REMES • GUI and Tools • Project Group & roles • Project Risks • Communication • Project Plan 08 -11 -05 2

What is REMES? 1/4 • REsource Model for Embedded Systems • Graphical modeling language – Component behaviours • Formally analysable models by translation into priced timed automata models • Functional and extra-functional behavior of a system – Functional behavior – Component wise, resource consumption of systems • Various kinds of resources: memory, cpu, ports, bandwidth, etc 08 -11 -05 3

What is REMES? 2/4 • Language constructs – Modes • • Two types: atomic, composite Control interface: entry, exit, init Data interface: shared variables (global, local) Constraints: invariants over continuous variables • Urgent mode – Composite modes • Internal structure with inner modes and edges • Edge types: entry, exit, init, conditional top, conditional discrete, internal – System as composition of composite modes 08 -11 -05 4

What is REMES? 3/4 • Illustration 08 -11 -05 5

What is REMES? 4/4 • REMES Language Semantics • Executional behavior of modes • In terms of 'delay' and 'discrete' transitions – Delay transitions: occur at a mode and represents activeness of the mode – Discrete transitions: where action transitions i. e. Edges between modes execute and hence mode changes • Internal modes of a composite mode execute sequentially • Composite modes can be composed and execute in parallel 08 -11 -05 6

Tool and GUI • Java • Swing • SVN 08 -11 -05 7

Project Groups Aneta Vulgarakis (Main supervisor) Md. H Anuradha Suryadevara (Project Leader) Vidar Rinne Pablo Ibanez Guido Diodato 10/3/2020 Ana Petričić (Secondary supervisor) FER Bariša Obradović (Team Leader) Josip Maričević Krešimir Krečak 8

Roles and Work Distribution Names School Roles Anuradha Suryadevara Md. H Project Leader, document manager, domain acknowledgement Guido Diodato Md. H Design, testing, coding Vidar Rinne Md. H Design, coding Pablo Ibanez Md. H GUI Bariša Obradović FER Team Leader, GUI Josip Maričević FER SVN Manager, testing, coding Krešimir Krečak FER Testing, coding 10/3/2020 9

Project Risks • INTERNAL COMMUNICATION PROBLEMS. • CUSTOMER COMMUNICATION PROBLEMS • MEMBERS DROPPING OF • TOOLS LACKING FUNCIONALITY. • BEING LATE. 10/3/2020 10

Project Risks HOW TO AVOID THIS? ? • EVERYONE SHOULD USE GOOGLE GROUP TO SCHEDULE TIME FOR AVAILABILITY AND SHARE FILES. • TRY TO SCHEDULE MEETINGS WELL IN ADVANCE. LIMIT TO EMAILS WHEN THE COMMUNICATION ARE NOT POSSIBLE • KEEP GOOD WORKING ATMOSPHERE 10/3/2020 11

Project Risks HOW TO AVOID THIS? ? • MAKE THOROUGH ANALYSIS OF AVAILABLE OPTIONS BEFORE COMMITTING TO ONE TOOL. • DO AS MANY TASKS AS POSSIBLE IN PARALLEL. BE PREPARED TO WORK OVERTIME. 10/3/2020 12

Communication 1/4 • Impossible to meet face to face • Communication technologies are indispensable 10/3/2020 13

Communication 2/4 ØMany technologies are available for communicating. . . • Chat and video conference (Skype) • E-Mail (Gmail) • Web group and mailing list (Google Groups) 10/3/2020 14

Communication 3/4 Ø. . and for choosing the meeting day? • Doodle (opinion poll) 10/3/2020 15

Communication 4/4 10/3/2020 16

Activity plan 10/3/2020 17