A Method for the Unified Definition and Treatment of Conceptual Schema Quality Issues

CMA Incremental ConclusionsMotivation Formalization CatalogIntroduction

A Method for theUnified Definition and Treatment ofConceptual Schema Quality Issues

Thesis supervised byDr. Antoni Olivé

Dr. Cristina Gómez

David AguileraJune 6th, 2014Barcelona


We cannot run the modern worldwithout software

2


We cannot run the modern worldwithout software

Which means software's qualityhas become essentialto our society.

Introduction

3SOMMERVILLE, I. Software Engineering, 9 ed. Addison-Wesley, 2010


Quality

The degree up to which a set ofproperties are met.

It depends on the perspective: - Innate excellence - Product-based - User-based - Manufacturing-based - Value-based

Introduction

4GARVIN, D.A.. What does “product quality” really mean? Sloan Manag. Review 26, 1 (1984), 25-43


Quality in Software

It's been classically focused on evaluating the final product.

ISO standards - ISO 9000 - ISO/IEC 1926

Proposals in the literature

Introduction

5


Maintenance

Software Development Process

Requirements

Design

Impl. & Unit Testing

Integration & Testing

Introduction

Classic Waterfall Model

Agile Methodologies(like SCRUM, with iterations)

6SOMMERVILLE, I. Software Engineering, 9 ed. Addison-Wesley, 2010


Evaluating Quality in Software

Focusing on the Final Product ispositive and necessary...

...but is not as efficient as it could be.

numbercost

time

Introduction

7


Conceptual Modeling

Essential Activity in theRequirements Stage of the


Introduction

8OLIVÉ, A. Conceptual Modeling of Information Systems, Springer, 2007


Conceptual Modeling

Conceptual SchemaGeneral Knowledge for an Information Systemto operate.

Essential Activity in theRequirements Stage of the


Introduction



The Problem

Defining Conceptual Schemasis a complex and difficult activity,

but the support modelers get is scarce.

There's a lot of work in the literature,but it does not reach practitioners.

Introduction

9


Goal of this Thesis

Improve the Quality ofConceptual Schemas

We want to help conceptual modelers.We want their tools to assist them. - Study and characterize several quality criteria. - Create a catalog that unifies those criteria. - Implement a conceptual modeling assistant.

Introduction

10


Addressed Quality Dimensions

We focus on those dimensions that can be evaluated using the schema itself.

According to conceptual modeling quality frameworks: - Syntactical Quality - Empirical Quality - Other dimensions, such as semantic validity, comprehension, ...

Introduction

11


Motivation

Formalization of Quality Issues

Catalog of Quality Issues

Conceptual Modeling Assistant

outline

02

03

04

05Notes on Efficient Evaluation06Conclusions and Future Work07

Introduction01


MotivationWhat we want. What we have.

13


Goal of this Thesis

Improve the Quality ofConceptual Schemas

We want to help conceptual modelers to create conceptual schemas: - that are syntactically correct, - that are complete, - whose elements are relevant, - that follow a set of best practices...

Motivation

14


What we would like to have...

LandVehicle

MotorVehicle

CarplateNumber:String

motorcycleplateNumber:String

Person{disjoint, complete}

parent 23child

IsParentOf

Owns* 0..1

Motivation

15



I want it to be syntactically correct.e.g. generalization cycles

Motivation

LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

16OBJECT MANAGEMENT GROUP (OMG), Unified Modeling Language (UML), Superstructure, 2011




Motivation

LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Remove one generalization to break the cycle





Motivation

LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1




I want it not to have duplicated info.e.g. redundant generalizations

LandVehicle

MotorVehicle


MotorcycleplateNumber:String


parent 23child

IsParentOf

Owns* 0..1

Motivation





LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Remove redundantgeneralization

Motivation





LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Motivation




I want it not to have duplicated info.e.g. repeated attributes

LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Motivation

18FOWLER, M. Refactoring: Improving the Design of Existing Code, Addison-Wesley, 1999




LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Pull-Up PropertyRefactoring

Motivation





LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Pull-Up PropertyRefactoring

Incomplete GeneralizationSet

Motivation





LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Incomplete GeneralizationSet

Motivation





LandVehicle

MotorVehicle



Person{disjoint, incomplete}

parent 23child

IsParentOf

Owns* 0..1

Motivation




LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

I want it to be correct.e.g. non-empty populations

Motivation





LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Motivation





LandVehicle

MotorVehicle




parent 23child

IsParentOf

Owns* 0..1

Changemultiplicities

Motivation





LandVehicle

MotorVehicle




IsParentOf

Owns* 0..1

Changemultiplicities

parent 20..3child

Motivation




I want it to be complete.e.g. awareness of (possibly) missing information

LandVehicle

MotorVehicle




parent 20..3child

IsParentOf

Owns* 0..1

Motivation





LandVehicle

MotorVehicle




parent 20..3child

IsParentOf

Owns* 0..1

(ir)reflexive?(in)transitive?(a)symmetric?

Motivation





LandVehicle

MotorVehicle




parent 20..3child

IsParentOf

Owns* 0..1


Yes, all relevant constraints are in the schema.

Motivation





LandVehicle

MotorVehicle




parent 20..3child

IsParentOf

Owns* 0..1


Yes, all relevant constraints are in the schema.

Create an asymmetry constraint, which is missing.

Motivation





LandVehicle

MotorVehicle




parent 20..3child

IsParentOf

Owns* 0..1Create an asymmetry

constraint, which is missing.

Motivation





LandVehicle

MotorVehicle




parent 20..3child

IsParentOf

Owns* 0..1

context Person inv: self.child.child-> excludes( self )

Motivation



But, what do we have today?

Motivation

- Inspections, testing, reviews, …

- There are several quality properties pu- blished (and scattered) in the literature.

- There are also proposals for efficiently dealing with inconsistencies.

- Current modeling tools o er little toff no support for dealing with this stu .ff (ArgoUML, Rational Rose, USE, Poseidon, ...)

21


Overview of Our Method

Motivation

22



FormalizationA

Motivation

22



Formalization

Characterization of Quality Issues

A

Motivation

22



Formalization


A

Issue AScope, conditions...

Motivation

22



Formalization Catalog


A


Motivation

22





A


Issue AContext, conditions...


Motivation

22





A





Issue BScope, conditions...

Motivation

22





A







Issue CScope, conditions...

Motivation

22



Formalization Catalog CMA

Modeling Tool


A








Motivation

22





A








Motivation

CMA

Modeling Tool

22





A








1. This gen is redu2. Association has3. Constraint does

Motivation

CMA

Modeling Tool

22



1. This gen is redu2. Association has3. Constraint does

Catalog







Formalization


A


Motivation

CMA

Modeling Tool

22


Design Science Research

“its fundamental principle is that knowledge and understanding

of a design problem and its solutionare acquired in the building and

application of an artifact”.

Motivation

23HEVNER, A. R., MARCH, S. T., PARK, J., AND RAM, S. Design science in information systems research, MIS Q. 28, 1 (2004) 75-105


Design Science Research

Quality Properties

Characterization and Formalization

Catalog CMA

State of the Art

ChallengeAssist Modelers and Improve Quality

SearchingAdaptingTesting

Motivation

24


Characterization and Formalization ofConceptual Schema Quality Issues

25


What is an Issue?

“an important topic or problemfor debate or discussion”

Formalization

26


What is an Issue?

“an important topic or problemfor debate or discussion”

In essence, it is a condition the schema should not satisfy to: - be syntactically correct, - be complete, - ensure all elements are relevant, - follow a best practice...

Formalization

26


What is an Issue?

Formalization

An Issue Type describes the problem.

An Issue Instance is a concrete instanceof that problem in the schema.

27


What is an Issue?

An Issue Type describes the problem.

An Issue Instance is a concrete instanceof that problem in the schema.

Formalization

Type: “There are redun-dant generalizations”

Instance: “g1 is redundant”

g1g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle

{disjoint, complete}

27


Issue Type Definition

An Issue Type must be able to specify: - which kind of elements may raise an issue, - which elements do actually raise it, - how to fix that issue, and - when and how should that issue be addressed

Formalization

28



Ix = { Sx, Φx, ρx, Ox, Px, Kx, Ax }

An Issue Type must be able to specify: - which kind of elements may raise an issue, - which elements do actually raise it, - how to fix that issue, and - when and how should that issue be addressed

Formalization

28




Formalization

28



Ix = { Sx, Φx, ρx, Ox, Px, Kx, Ax }Sx (scope) and Φx (applicability condition)

determine the potential set of elements that may raise an issue of type Ix

Formalization

29





g1g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


Formalization

29





g1g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


Sx = { Generalization }

Formalization

29





g1g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


Sx = { Generalization }Φx (g) = “there are two generalizations ga and gb such that: g.general = ga.general g.specific = gb.specific

Formalization

29




ρx (issue condition) determines if an element in Pot(Ix) does actually raise an issue of type Ix

Formalization

30





g1g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


ρx (g) = “there is an indi-rect generalization path between g.general and g.specific”

Formalization

30





g1g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


ρx (g) = “there is an indirect generalizations path between g.general and g.specific”

Formalization

30




Ox is a set of actions that help the conceptual modeler to fix an issue instance

Formalization

31




g1g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


Ox = { “remove redundant generalization” }


Formalization

31




g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


Ox = { “remove redundant generalization” }


Formalization

31




g1g2

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


Ox = { “remove redundant generalization”,“break the indirect path of generalizations” }


Formalization

31




g1

g3, g4

LandVehicle

MotorVehicle

Car Motorcycle


Ox = { “remove redundant generalization”,“break the indirect path of generalizations” }


Formalization

31




Px is a set of precedents, which are issue types that must not have issues for considering Ix.

Formalization

32





Ia = “there is a cycle of generalizations”

Ib = “there are redundant generalizations”

Formalization

g1g2

g3

LandVehicle

MotorVehicle

Car32






Ib = “the generalization is redundant”

Formalization

g1g2

g3

LandVehicle

MotorVehicle

Car32






Ib = “the generalization is redundant”

Pb = { Ia }

Formalization

g2

g3

LandVehicle

MotorVehicle

Car32




Kx (kind) can either be Problem or Checking.

Formalization

33





Problem Issues can only be fixed by changing the schema, so that the issue does no longer exist.

Formalization

34





LandVehicle

MotorVehicle

Car Motorcycle


LandVehicle

MotorVehicle

Car Motorcycle


Formalization

34





Checking Issues require the conceptual modeler to manually check something.

There might be situations in which this checking will entail some changes in the schema.

Formalization

35





“Check whether the asso-ciation «IsParentOf» needs a constraint enforcing the symmetry property.”

Formalization

35

Personparent 0..2

*child

IsParentOf





Personparent 0..2

*child

IsParentOf

Formalization

35




✓




Personparent 0..2

*child

IsParentOf

Formalization

35






Ax (acceptability) indicates whether anissue type is Acceptable or Non-acceptable

Formalization

36





MotorVehicle




If non-acceptable,we must modify the schema in a way such that the issue disappears.

Formalization

37





MotorVehicle





Formalization

37

Pull-up Property





MotorVehicleplateNumber:String

Car Motorcycle



Formalization

37





MotorVehicle





Formalization

37

Change it to incomplete





MotorVehicle



{disjoint, incomplete}


Formalization

37





MotorVehicle




If acceptable,the modeler can simply state that he won't fix it the schema.

Formalization

38


✓




MotorVehicle




If acceptable,the modeler can simply state that he won't fix it the schema.

Formalization

38


Life cycle of an Issue Instance

Formalization

Non-AcceptableProblem Issue

AcceptableProblem Issue

Non-AcceptableChecking Issue

AcceptableChecking Issue

PendingPending

Accepted

Pending

CheckedChecked

Pending

Accepted

Deletion

Deletion Deletion Deletion

Acc

ept

Acc

ept

Chec

k

Chec

k

Rec

onsi

der

Rec

onsi

der

Rec

onsi

der

Rec

onsi

der

39


A Catalog of Quality Issues

40


The Catalog

Design Science Research requiresan artifact to be built.

Catalog

A Catalog of Quality Issues presents quality properties uniformly and

demonstrates the expressiveness and usefulness of our method.

41


Expressiveness

The catalog includes all metamodel constraints plus 65 additional non-syntactic quality issue types.

(from conceptual modeling books, papers, and IDEs)

Catalog

We defined them as Quality Issues using

our formalization.

42


Classification

Catalog

Syntactic Issue TypesAn integrity constraint defined in the UML metamodel.

For example,“There is a cycle of generalizations.”



Classification

Catalog

Syntactic Issue TypesAn integrity constraint defined in the UML metamodel.

LandVehicle

MotorVehicle

Car

Non-acceptable Problem = <Classifier> = true = self.allParents()-> includesSelf()

S Φ ρ

43


Classification

Catalog

Syntactic Plus Issue Types (11)Integrity constraints applicable when UML is used as a conceptual modeling language.

For example,“An attribute has no type.”

44MOODY, D.L., Metrics for evaluating the quality of entity relationship models. In ER, vol. 1507 of LNCS. Springer, 1998, pp. 211-225


Classification

Catalog

Syntactic Plus Issue Types (11)Integrity constraints applicable when UML is used as a conceptual modeling language.

CarplateNumber

Non-acceptable Problem = <Property> = it is an attribute = self.type()-> notEmpty()

S Φ ρ

44


Classification

Catalog

Basic Quality Issue Types (20)Fundamental properties for a schema to be correct, relevant, and complete.

For example,“The schema is not strongly satisfia-ble because of a recursive associa-tion.”



Classification

Catalog

Basic Quality Issue Types (20)

Personparent 2

3child

IsParentOf

Fundamental properties for a schema to be correct, relevant, and complete.

Non-acceptable Problem = <Association> = “is binary and recursive” = “the multiplicities are not strongly satisfiable”

S Φ ρ

45


Classification

Catalog

Best Practices (18)Issues that are recommended by some authors in some contexts.

For example,“An attribute repeated among all specific classes of an incomplete generalization set is correct.”



Classification

Catalog

Best Practices (18)Issues that are recommended by some authors in some contexts.

(Non-)Acceptable Checking = <gs:GenSet, s:String> = “gs is incomplete” = “every specific class of gs has an attribute named s”

S Φ ρ

MotorVehicle



{incomplete}

46


Classification

Catalog

Naming Guidelines (16)Special kind of best practices, focused on the names given to schema elements.

For example,“The name of a boolean attribute is not a third-person singular verb-phrase.”

47AGUILERA, D., GÓMEZ, C., OLIVÉ, A., A complete set of guidelines for naming UML conceptual schema elements.Data Knowl. Eng. 88, 0 (2013), 60-74


Classification

Catalog

Naming Guidelines (16)Special kind of best practices, focused on the names given to schema elements.

(Non-)Acceptable Problem = <Property> = “it is boolean” = “its name is not a verb phrase written in singular third-person form”

S Φ ρ

Personadult:Boolean

47


Usefulness

We analyzed 13 conceptual schemas developed by students as part of their

final projects in a Computer Science degree.

Catalog

Size of the schemas (median):- 17 Classes- 3 AssocClases- 12 Associations

- 56 Attributes- 8 Invariants

48


Usefulness

Catalog

All conceptual schemas presentedseveral Quality Issues!

Number of issues (median):- 0 Syntactic+- 111 Basic Properties

- 33 Best Practices- 24 Naming Guidelines

Size of the schemas: - 17 Classes - 3 AssocClases - 12 Associations

- 56 Attributes- 8 Invariants

49


Explore and Analyze current UML IDEs, comparing them with our catalog

Support by Current IDEs

29 Modeling ToolsFocus on the UML

Conceptual Modeling Tasks

Catalog

50

(ArgoUML, Rational Rose, USE, Poseidon, SDMetrics...)


- Do they control syntactic issue types?- What about other issue types?- How do they o er this support?ff- Do they provide assistance for fixing them?- Can they be extended with new issue types?

Support by Current IDEs

Catalog

Explore and Analyze current UML IDEs, comparing them with our catalog

51


What we found...

Syntactic Support3 Full

17 Partial

9 None

Catalog

52


What we found...

Syntactic Support Non-Syntactic Support

S+ BasProp BestPrac Naming

20

0

3 Full

17 Partial

9 NoneCatalogArgoUMLSDMetrics

CatalogCatalog

52


What we found...

Syntactic Support Non-Syntactic Support3 Full

17 Partial

9 None


20

0

CatalogArgoUMLSDMetrics

CatalogCatalog

Corrective Actions - 2 tools only

52


What we found...

Syntactic Support Non-Syntactic Support

Extension Mechanisms - 4 tools only

3 Full

17 Partial

9 None


20

0

CatalogArgoUMLSDMetrics

Catalog

Corrective Actions - 2 tools only

52


Support by IDEs vs. our Catalog

Best IDEs today ArgoUML and SDMetrics

The number ofissues detected by our catalog versus

those detected by these toolsis 10 times larger!

Catalog

53


Fair Comparison... (extensibility?)

- Only 4 tools can be extended

- They all deal with problem issues, thus ignoring checking issues

- The formalization they use is less expressive than ours

Catalog

54


Conceptual Modeling AssistantImplementation of a Prototype Tool

55


Eclipse

CMA based on Eclipse

Plugin

Plugin

Plugin

Workbench

Platform Runtime

WebTools

Java DevTools

CMA

Design Science Research requiresan artifact to be built.

56


Plug

ins

Architecture of our CMA

Eclipse

Workbench

Platform Runtime

CMA

57


Plug

ins


Eclipse

Workbench

Platform Runtime

UML2Tools

OCLInterpreter

CMA

57


Plug

ins


Eclipse

Workbench

Platform Runtime

UML2Tools

OCLInterpreter

CMA Plugin

Issue Processor

Issu

e Ty

pe

Man

ager

Issue View(feedback)

CMA

57


Plug

ins


Eclipse

Workbench

Platform Runtime

UML2Tools

OCLInterpreter

CMA Plugin

Issue Processor


IssueTypeXML

Issu

e Ty

pe

Man

ager

CMA

57


Plug

ins


Eclipse

Workbench

Platform Runtime

UML2Tools

OCLInterpreter

CMA Plugin

Issue Processor


Remote Server

IssueCatalog

IssueTypeXML

Issu

e Ty

pe

Man

ager

CMA

57


The Catalog

CMA

58

The Catalog – Regular Issue Types

CMA

<issue nid=”038” id=”redundant-gen” kind=”problem” acceptance=”non-acceptable”>

<context>Generalization</context> <title>A generalization is redundant</title>

<applicability-condition> Generalization.allInstances()->select( g1, g2 | g1 <> self and g2 <> self and g2.specific = self.specific and g2.general = self.general ) ->notEmpty() </applicability-condition>



</issue>59


The Catalog – Black-Box Issue Types

CMA

60

UML2Tools

OCLInterpreter

CMA Plugin

Issue Processor


IssueCatalogIssue

TypeXML

Issu

e Ty

pe

Man

ager



CMA

60

UML2Tools

OCLInterpreter

CMA Plugin

Issue Processor


IssueCatalogIssue

TypeXML

Issu

e Ty

pe

Man

ager

«interface»IBlackBoxIssueType



CMA

60

UML2Tools

OCLInterpreter

CMA Plugin

Issue Processor


IssueCatalogIssue

TypeXML

Issu

e Ty

pe

Man

ager

«interface»IBlackBoxIssueType

BlackBoxIssueType

getPotentialSet()doesRaiseAnIssueType(Tuple)


CMA

CMA

61


Efficient Evaluationof Quality Issues

62


Computation of Issue Instances

Incremental

Personadult:Boolean

BookisABestSeller:Boolean

Sx = { Property }ρx(a) = “the name of a boolean attribute is not a verb phrase”

63



Incremental

Issues?Evaluate the Applicability and Issue Conditions for every instance of the scope.

Personadult:Boolean



63



Incremental

Personadult:Boolean



64



Incremental

Personadult:Boolean



The name of the boolean attribute «adult» is not a verb phrase.

64



Incremental




This evaluation takes time.

We want to detect quality issuesas fast as possible.

65



Incremental

“Not all changes that can be applied to the schema have an e ect on the ffevaluation of the expression”.

Incremental Methods

66


Incremental Methods

Possible changes:

Incremental

Personadult:Boolean




67


Incremental Methods

Possible changes: - Change the name of A1

Incremental

Personadult:Boolean




67


Incremental Methods

Possible changes: - Change the name of A1

Incremental

Personadult:Boolean

Bookfree:Boolean



The name of the boolean attribute «free» is not a verb phrase.

67


Incremental Methods

Possible changes: - Change the name of A1 - Change the name of A2

Incremental

Personadult:Boolean




67


Incremental Methods

Possible changes: - Change the name of A1 - Change the name of A2

Incremental

PersonisAnAdult:Boolean



67


Incremental Methods

Possible changes: - Change the name of A1 - Change the name of A2 - Change the name of C1

Incremental

Personadult:Boolean




67


Incremental Methods

Possible changes: - Change the name of A1 - Change the name of A2 - Change the name of C1

Incremental

Manadult:Boolean




67


Incremental Methods

Possible changes: - Change the name of A1 - Change the name of A2 - Change the name of C1 - Add a new attribute - Delete an association - Create a generalization

Incremental

Personadult:Boolean




67


Incremental Methods

Incremental

Possible changes: - Change the name of A1 - Change the name of A2 - Change the name of C1 - Add a new attribute - Delete an association

Personadult:Boolean



Sx = { Property }ρx(a) = “the name of a boolean attribute is not a verb phrase”The goal of an Incremental Method

is to determine the set of changesthat (might) change the result of

evaluating an expression.

68


Incremental Methods

Incremental

Possible changes: - Change the name of A1 - Change the name of A2 - Change the name of C1 - Add a new attribute - Delete an association - Create a generalization

Personadult:Boolean




69


Incremental Methods

Incremental

Personadult:Boolean




69

Possible changes: - Change the name of A1 - Change the name of A2 - Change the type of A2 - Delete A2 - Delete an association - Create a generalization


Efficient Detection of Issues

We selected Egyed's method and applied it toour algorithm, taking into account: - Applicability and issue conditions - Precedents

Modify the algorithm forcomputing issue instances with an

instance-based incremental approach.

Incremental

70EGYED, A. Automatically detecting and tracking inconsistencies in software design models.IEEE Trans. Softw. Eng. 37, 2 (2011), 188-204


Improvements in Efficiency

Regular approach (schemas <500 elems)

Incremental approach

Avg. 9 seconds Max. over 5 minutes

Max. 250 millisecs

Incremental

The results are conclusive.

71


Conclusions and Future Work

72


Conclusions

The ProblemDefining Conceptual Schemas is a complex and difficult activity, but the support modelers get is scarce.

Conclusions

73


Conclusions

The ProblemQuality in Conceptual Modeling is important,but the support modelers get is scarce.

The SolutionA method for defining and treating Quality Issues,

whose goal is to assist conceptual modelers.

(based on current literature)

The ProblemDefining Conceptual Schemas is a complex and difficult activity, but the support modelers get is scarce.

Conclusions

73


1Formalization

Conceptual Schema Quality Issues- Definition- (Efficient) Detection- Solution

Conclusions

AGUILERA, D., GÓMEZ, C., AND OLIVÉ, A.A method for the definition and treatment of conceptual schema quality issues.In ER (2012), vol. 7532 of LNCS, Springer, pp. 501-514 74


2Catalog

Issues from the literature- UML/OCL- Syntactic correctness- Best practices and guidelines

Conclusions

AGUILERA, D., GÓMEZ, C., AND OLIVÉ, A.A complete set of guidelines for naming UML conceptual schema elements.Data Knowl. Eng. 88, 0 (2013), 60-74

AGUILERA, D., GÓMEZ, C., AND OLIVÉ, A.Enforcement of conceptual schema quality issues in current Integrated Development Environments. In CAiSE (2013), vol. 7908 of LNCS, Springer, pp. 626-640

75


3CMA

Conceptual Modeling Assistant- The Eclipse Platform- Implements the method- Integrates the catalog

Conclusions

AGUILERA, D., GARCÍA-RANEA, R., GÓMEZ, C., AND OLIVÉ, A.An eclipse plugin for validating names in UML conceptual schemas. InER Workshops (2011), vol. 6999 of LNCS, Springer, pp. 323-327

AGUILERA, D., GÓMEZ, C., AND OLIVÉ, A.An eclipse plugin for improving the quality of UML conceptual schemas. InER Workshops (2012), vol. 7518 of LNCS, Springer, pp. 387-390 76


What's next?

77

Conclusions


What's next?Extending the Catalog

78

Conclusions


What's next?Integration with Testing

79

Conclusions


What's next?Validation with Real Users and Projects

80

Conclusions


What's next?Automatic Reparation

81

Conclusions


Publications

AGUILERA, D., GÓMEZ, C., AND OLIVÉ, A.Enforcement of conceptual schema quality issues in current Integrated Development Environments.In CAiSE (2013), vol. 7908 of LNCS, Springer, pp. 626-640

AGUILERA, D., GÓMEZ, C., AND OLIVÉ, A.An eclipse plugin for improving the quality of UML conceptual schemas.In ER Workshops (2012), vol. 7518 of LNCS, Springer, pp. 387-390

AGUILERA, D., GARCÍA-RANEA, R., GÓMEZ, C., AND OLIVÉ, A.An eclipse plugin for validating names in UML conceptual schemas.In ER Workshops (2011), vol. 6999 of LNCS, Springer, pp. 323-327

AGUILERA, D., GÓMEZ, C., AND OLIVÉ, A.A complete set of guidelines for naming UML conceptual schema elements.Data Knowl. Eng. 88, 0 (2013), 60-74

AGUILERA, D., GÓMEZ, C., AND OLIVÉ, A.A method for the definition and treatment of conceptual schema quality issues.In ER (2012), vol. 7532 of LNCS, Springer, pp. 501-514

82

Conclusions


David AguileraUPC - Barcelona

Dr. Olivé and Dr. Gómez

A Method for theUnified Definition and Treatment ofConceptual Schema Quality Issues

A Method for the Unified Definition and Treatment of Conceptual Schema Quality Issues

Education

Transcript of A Method for the Unified Definition and Treatment of Conceptual Schema Quality Issues