Quality Assurance of Software Models within Eclipse using Java and OCL

Transcription

1 Quality Assurance of Software Models within Eclipse using Java and OCL Dr. Thorsten Arendt Modellgetriebene Softwareentwicklung mobiler Anwendungen Wintersemester 2014/ Dezember 2014

2 Outline Why model quality assurance? A structured model quality assurance process Tailoring the process for a given modeling project Specification process Application process Tool support: EMF Refactor 2

3 Why model quality assurance? Problems Model Metrics Model Smells Risks Model Refactorings 3

4 Why model quality assurance? Model Metrics Problems Model Smells Model Refactorings Risks Model Quality Assurance Process 4

5 Software quality software model quality [ISO/IEC 9126] 5

6 Software quality software model quality Software quality 6C model quality goals Correctness Completeness Changeability Comprehensibility Confinement Consistency [ISO/IEC 9126] [Mohagheghi] 6

7 Model smells Adopted from the concept of code smell Smells are parts of the model that contain symptoms of poor model quality are worthy of an inspection are potential candidates for improvements by refactoring Smells are not synonyms for problems smells don't always indicate a problem.... You have to look deeper to see if there is an underlying problem there - smells aren't inherently bad on their own - they are often an indicator of a problem rather than the problem themselves. [Fowler] 7

8 A structured model quality assurance process (1) Specification process Manager Designer Application process 8

9 Discussing important quality aspects Specification process Changeability Comprehensibility Correctness Completeness Changeability Comprehensibility Confinement Consistency 9

10 Specifying relevant model smells (1) Specification process Changeability Comprehensibility Question: Are there equally named classes in different packages? Smell: Multiple definitions of classes with equal names 10

11 Specifying relevant model refactorings (1) Specification process Smell: Multiple definitions of classes with equal names Refactorings: Merge Classes, Rename Class 11

12 Specifying relevant model smells (2) Specification process Completeness Confinement Question: Are there abstract classes without any concrete subclasses? Smell: No concrete Subclass 12

13 Specifying relevant model refactorings (2) Specification process Smell: No concrete subclass Refactoring: Insert Concrete Subclass 13

14 UML specific refactorings Refactoring: Change Attribute to Association End Refactoring: Change Association End to Attribute 14

15 UML class attribute specification Refactoring: Change Attribute to Association End [OMG: UML] 15

16 A structured model quality assurance process (2) Specification process Manager Designer Application process Modeler Reviewer 16

17 Tool environment for model quality assurance Model Metrics Problems Risks Model Smells Model Refactorings Model Quality Assurance Process 17

18 Quality Assurance and Textual Modeling in Eclipse 18

19 Scenario: Vehicle Rental Company Project Development of a web application for renting vehicles using MDD Semantic domain Company with vehicles, customers, services,.. Technical domain Web application Modeling purpose Modeling of the semantic domain as well as the information mandatory for code generation using a (textual) DSML Credo The better the model, the better the code 19

20 Xtext Grammar for SWM 20

21 Scenario: Xtext Model Vehicle Rental Company Is the model complete? Is the model comprehensible, correct,? 21

22 Metrics calculation Is the model complete? 22

23 Reporting and interpreting Is the model complete? variously interpretable 23

24 Smell detection Is the model complete? 24

25 Locating and interpreting Is the model complete? refactoring as quick-fix 25

26 Refactoring application Is the model complete? Model partially completed 26

27 EMF Refactor: Architecture Specification Language Generation module Application module metrics, smells, refactorings extension points Eclipse Modeling Framework (EMF) 27

28 Configuration of relevant quality assurance techniques 28

29 Smell-Refactoring relations 29

30 EMF Refactor: Architecture Specification Language Generation module Application module metrics, smells, refactorings extension points Eclipse Modeling Framework (EMF) 30

31 Specification languages Metrics Generation module Application module metrics, smells, refactorings + Refactorings Eclipse Modeling Framework (EMF) 31

32 Integration of EMF Refactor tools Specific tools use each other Metric-based model smells Refactoring invocation from within model smell results view Model smell analysis during refactoring application Each tool can be used directly on the model within a certain EMF-based modeling environment EMF instance editor Unified Modeling Language (UML) Eclipse Plugin Papyrus IBM Rational Software Architect Textual Xtext editors 32

33 Flexible specification mechanisms in EMF Refactor Usage of existing quality assurance techniques Combination of existing model metrics Metric-based model smells Composite model refactorings Usage of concrete specification languages Java OCL EMF model transformation language Henshin further languages can be integrated by new adapters 33

34 Conclusion Quality assurance for software models is an important project management task Software quality software model quality A structured model quality assurance process can be adapted to project and domain specific purposes The application sub-process is performed during the modeling task, e.g., in a model review The specification sub-process should be performed before (as far as possible) Tool support in Eclipse is given by EMF Refactor 34

35 References ISO/IEC :2001 Software engineering Product quality Part 1: Quality model, P. Mohagheghi, V. Dehlen, T. Neple: Definitions and approaches to model quality in model-based software development - A review of literature. Information & Software Technology, Martin Fowler: Code Smell. Object Management Group (OMG): Unified Modeling Language (UML), Thorsten Arendt and Gabriele Taentzer: A tool environment for quality assurance based on the Eclipse Modeling Framework. Journal Automated Software Engineering, Thorsten Arendt: Quality Assurance of Software Models - A Structured Quality Assurance Process Supported by a Flexible Tool Environment in the Eclipse Modeling Project, Dissertation, Eclipse: EMF Refactor, 35