108-11-05 gui for development of remes models remes gui group
TRANSCRIPT
Summary of contents
208-11-05
• What is REMES
• GUI and Tools
• Project Group & roles
• Project Risks
• Communication
• Project Plan
308-11-05
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
408-11-05
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
608-11-05
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
8
Project Groups
23-04-19
Josip Maričević Krešimir Krečak
Anuradha Suryadevara
(Project Leader)
Bariša Obradović(Team Leader)
Aneta Vulgarakis(Main supervisor)
Vidar Rinne Guido DiodatoPablo Ibanez
Ana Petričić (Secondary supervisor)
MdH FER
923-04-19
Roles and Work Distribution
Names School Roles
Anuradha Suryadevara MdH Project Leader, document manager, domain acknowledgement
Guido Diodato MdH Design, testing, coding
Vidar Rinne MdH Design, coding
Pablo Ibanez MdH GUI
Bariša Obradović FER Team Leader, GUI
Josip Maričević FER SVN Manager, testing, coding
Krešimir Krečak FER Testing, coding
1023-04-19
• INTERNAL COMMUNICATION PROBLEMS.
• CUSTOMER COMMUNICATION PROBLEMS
• MEMBERS DROPPING OF
• TOOLS LACKING FUNCIONALITY.
• BEING LATE.
Project Risks
1123-04-19
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
1223-04-19
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.
Project Risks
1323-04-19
• Impossible to meet face to face
• Communication technologies are indispensable
Communication 1/4
1423-04-19
Many technologies are available for communicating...
• Chat and video conference (Skype)
• E-Mail (Gmail)
• Web group and mailing list (Google Groups)
Communication 2/4