Implementation of an Eclipse-based Model Validation Plug-in for Papyrus-RT. Tuhin Kanti Das & Juergen Dingel

Transcription

1 Implementation of an Eclipse-based Model Validation Plug-in for Papyrus-RT Tuhin Kanti Das & Juergen Dingel

2 Outline } Background } Research Stages Analysis of UML-RT Models! Goal: Proposing a set of design guidelines ImplementaEon of a Prototype Model Validator! Goal: Providing tool support for a suitable set of the proposed EvaluaEon! Goal: " Providing support for the validity of the guideline catalog " Assessing the usefulness of the model validator } Demo of the Prototype Plugin 2

3 Background: UML-RT } Real Eme profile of UML } Specify and implement real-eme embedded sojware systems } Commercial tool support: IBM Rose RT, IBM RSA RTE } Open-source tool support: Papyrus-RT 3

4 Research Methodology Analysis of around 100 UML-RT models Academic Models Industrial Models Average size: 5 Capsules 35 States 71 TransiEons 3 Protocols Maximum depth of state neseng: 4 Mostly telecommunicaeon models More complicated Maximum depth of state neseng: 6 Discussion with UML-RT praceeoners Development guidelines for UML-RT models 4

5 SoJware Development Guidelines ConvenEons Principles Smells PaXerns AnEpaXerns Figure: ClassificaEon of SoJware Development Guidelines

6 Proposed Design Guidelines } Conventions: 8 } Patterns: 3 } Anti-patterns: 20 [1] T. K. Das and J. Dingel, "State machine anepaxerns for UML-RT", ACM/IEEE 18th InternaEonal Conference on MODELS'15 (2015). [2] T. K. Das and J. Dingel, "Model development guidelines for UML-RT: conveneons, paxerns and anepaxerns", SoJware and Systems Modeling (SoSyM) (2016). [3] T. K. Das and J. Dingel, "Model development guidelines for UML-RT", Technical Report , Queen's University, Canada (2016). 6

7 Proposed Design Guidelines Conventions: 8 CancellaEon of Emers ajer their Use TerminaEon of Created Capsules ajer Their Use Removal of Unconnected Ports Removal of Unreachable ArEfacts } Patterns: 3 } Anti-patterns: 20 Resource UElizaEon UML-RT TransiEons Proper Use of IniEal TransiEons Use of Internal Self-TransiEons instead of External Others ConjugaEon of Server-side Ports in a Binary Protocol Improving the VisualizaEon of UML-RT Diagrams 7

8 Proposed Design Guidelines } Conventions: 8 Patterns: 3 Behavioral Status Monitoring Scenario Proper Use of System Timers } Anti-patterns: 20 Structural SeparaEon of ResponsibiliEes 8

9 Proposed Design Guidelines } Conventions:8 } Patterns: 3 9 Anti-patterns: 20 Inspired by Fowler s Code Smells Refused Bequest in UML-RT Exclusion of Inherited Features Existence of Data Clumps in UML-RT Lack of Cohesion (Divergent Change) in UML-RT Feature Envy in UML-RT SpeculaEve Generality in UML-RT DuplicaEon in UML-RT Choice-Point (Behavior) Overlapping CondiEonals Choice-point with Non-exhausEve Guards UML-RT TransiEons (Behavior) Inappropriate Use of Self-TransiEons Misuse of Local TransiEons Incorrect Use of Group TransiEons Inheritance (Structure/Behavior) Absence of Inheritance Pihalls of Using Promote/Demote OperaEons in UMLRT Inheritance Guard CondiEons (Behavior) Misuse of Guard CondiEons Guards in JuncEon Points are affected by AcEon Code in Incoming TransiEon Others Incorrect Use of Asynchronous CommunicaEon (Behavior) Incorrect Use of One-shot Timers (Behavior) Hidden States (Behavior) Inappropriate Modeling Scope (Structure)

10 Implementation: Unreachable States No trigger exists! 10 Figure: Unreachable State

11 Implementation: One-shot Timer as Periodic Two Types of Timers in UML-RT } One-shot: timer.informin(umlrttimespec(2, 0)); } Periodic: timer.informevery(umlrttimespec(2, 0)); 11 Figure: Use of One-shot Timer as Periodic

12 Implementation: One-shot Timer as Periodic 12 Figure: Use of One-shot Timer as Periodic

13 Implementation: Dependency on Requirement Specs Figure: Incorrect Use of Group TransiEon 13

14 Implementation: Dependency on Requirement Specs 14 Figure: Refactored SoluEon for Group TransiEon

15 Evaluation Criteria } Application of the validator in a third party model repository } Feedback from UML-RT practitioners } User Study: a survey } Direct response: Acceptance of the guidelines among the community } Indirect response: Problem solving queries 15

16 Sample Survey Query: Direct Response 16

17 Sample Survey Query: Indirect Response 17

18 Please Help Evaluate the Research! } You will receive an once the survey is online } Approximate duration: minutes 18

19 Current State of the Prototype Validator } DEMO 19

20 20 Thank you!