170 likes | 255 Views
Learn about REMES, a modeling language for Embedded Systems. Discover REMES components, behaviors, language constructs, modes, and system composition. Explore Project Group roles and risk management strategies. Get insights into effective communication and project planning.
E N D
REMES GUI group GUI for development of REMES models
Summary of contents • What is REMES • GUI and Tools • Project Group & roles • Project Risks • Communication • Project Plan
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
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
What is REMES? 3/4 • Illustration
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
Tool and GUI • Java • Swing • SVN
Project Groups Ana Petričić(Secondary supervisor) AnetaVulgarakis(Main supervisor) MdH FER AnuradhaSuryadevara(Project Leader) BarišaObradović(TeamLeader) Vidar Rinne Pablo Ibanez Guido Diodato JosipMaričević KrešimirKrečak 2014-10-13
Project Risks • INTERNAL COMMUNICATION PROBLEMS. • CUSTOMER COMMUNICATION PROBLEMS • MEMBERS DROPPING OF • TOOLS LACKING FUNCIONALITY. • BEING LATE.
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
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.
Communication 1/4 • Impossible to meet face to face • Communication technologies are indispensable
Communication 2/4 • Many technologies are available for communicating... • Chat and video conference (Skype) • E-Mail (Gmail) • Web group and mailing list (Google Groups)
Communication 3/4 • .. and for choosing the meeting day? • Doodle (opinion poll)