Mining Entities to Rules with MEntoR

Mining Entities to Rules
MEntoR
Angela Lozano,
Andy Kellens,
Kim Mens,
Gabriela Arevalo
Thursday 16 December 2010

source code regularities
• Implementation standards
e.g. idioms, naming conventions, design patterns....
• Encode design decisions
• Facilitate comprehension, maintenance, & evolution
• Are implicit = often not fully respected
2/9

source code regularities
• Implementation standards
e.g. idioms, naming conventions, design patterns....
• Encode design decisions
• Facilitate comprehension, maintenance, & evolution
• Are implicit = often not fully respected
We can mine for regularities BUT
their usefulness might be ‘entity-dependent’
2/9

Motivation
3/9

Motivation
3/9
how to add a new
action to the app?
let me see

Motivation
3/9
how to add a new
action to the app?
here!

Motivation
3/9
Source code is reliable
how to add a new
action to the app?

Motivation
3/9
are there other
examples of actions?here!

Motivation
3/9
which other methods
should I add?
here!

Motivation
3/9
It condenses design knowledge
which other methods
should I add?

Motivation
3/9
which other methods
should I add?
are all actions implemented
using the command pattern?

Motivation
3/9
which other methods
should I add?
are all methods related to
actions documented?

Motivation
3/9
All developers need such knowledge to keep consistency
which other methods
should I add?
actions documented?

Motivation
3/9
All developers need such knowledge to keep consistency
We need automatic support to detect design knowledge in the code
which other methods
should I add?
actions documented?

4/9
--------------------------CId>Action Impl>performAction -Impl>isUndoable -Hier>AddObjectAction -Ref>MenuService
AbstractAddAction ------X ----------------- X ------------------------X -----------------------X ---------------------X
AddObjectAction --------X ----------------- -------------------------------------------------------- ---------------------X

Implications
H>ArrayedCollection ==> Id>'Array'
True in a closed world
Subset relation in the FCA lattice
H>ArrayedCollection
Id>Array
ArrayedCollection Array CharacterArray
5/9
Characterizing Collection
Classes
Classes
AttributesAttributesAttributesAttributesAttributes
Classes
Classes
Collection * *
SequenceableCollection * * *
OrderedCollection * * *
ArrayedCollection * * * * *
Array * * * *
CharacterArray * * * *
H>Collection
H>SequenceableCollection
H>ArrayedCollection
Id>Collection
Id>Array
Classes

Implications
H>ArrayedCollection ==> Id>'Array'
True in a closed world
Subset relation in the FCA lattice
Asssociations
H>Collection --83%--> H>SequenceableCollection
Most collections are sequenceable; but Collections is not
Superset or siblings relation in the FCA lattice
H>ArrayedCollection
Id>Array
H>Collection
SequenceableCollection OrderedCollection
Collection
5/9
Classes
Classes
AttributesAttributesAttributesAttributesAttributes
Classes
Classes
Collection * *
SequenceableCollection * * *
OrderedCollection * * *
ArrayedCollection * * * * *
Array * * * *
CharacterArray * * * *
H>Collection
H>ArrayedCollection
Id>Collection
Id>Array
Classes
Condition*
Conclusion

A regularity is a set of intersecting rules
6/9

CId>ActionHier>IntensiVEAction
.
. . . . .. . . . .. . . . .. . . . .. . .
6/9
Rule 1:
CId>Action ==>Hier>IntensiVEAction

Impl>performAction
Impl>undoActio
.
. . . . .. . . . .. . . . .. . . . .. . .
6/9
Rule 2:
Impl>undoAction ==>Impl>performAction

Impl>performAction
Impl>undoActio Hier>AbstractAction
Impl>name
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . .
.
.
. . . . .. . . . .. . . . .. . . . .. . .
6/9
Rule 3:
Hier>AbstractAction -->Impl>name

Impl>performAction
Impl>undoActio
23 classes
match
Hier>AbstractAction
Impl>name
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . .
.
.
. . . . .. . . . .. . . . .. . . . .. . .
6/9

7/9
. . .
. . .
MEntoR
. . . . . .
. . . . .
. . . . . .
. . . . .
If the entity in focus is
here
The usefulness of a rule might be ‘entity-dependent’
MEntoR is based on the entity in focus
Condition properties → Conclusion properties

7/9
. . .
. . .
MEntoR
. . . . . .
. . . . .
. . . . . .
. . . . .
here
the entity is classiﬁed as

7/9
. . .
. . .
MEntoR
. . . . . .
. . . . .
. . . . . .
. . . . .
here
an error
of the rule

7/9
. . .
. . .
MEntoR
. . . . . .
. . . . .
. . . . . .
. . . . .
here
an error
satisﬁed example
of the rule

7/9
. . .
. . .
MEntoR
. . . . . .
. . . . .
. . . . . .
. . . . .
here
an error
satisﬁed example a suggestion
of the rule

8/9
MEntoR

MEntoR
8/9
Context is given by the entity in focus

MEntoR
8/9
Entity
in
focus
Context is given by the entity in focus

8/9
Selected
rule
Shows the rules related to the entity in focus
MEntoR

8/9
Selected
rule
Shows the rules related to the entity in focus
MEntoR
Rule pretty
printed

MEntoR
8/9

Entity in
focus
MEntoR
8/9

Entity in
focus
Errors
MEntoR
Rules in which the entity complies with the condition
but not with the conclusion (errors)
8/9

MEntoR
Entity in focus
8/9

Rules in which the entity complies with the condition
and with the conclusion (satisﬁed)
MEntoR
Satisﬁed rulesEntity in focus
8/9

Rules in which the entity complies partially with the
conclusion but not with the condition (suggestions)
Suggestions
MEntoR
Entity in focus
8/9

MEntoR
Entity in focus
Tag
options
8/9

MEntoR
Entity in focus
8/9
Rule
View

IVAbstractEntity
IVCheckeableEntity
IVComposableEntityDefiniton
IVPersistentEntity
UncheckedEntityEditor
CId>Entity
Hier>Classifications2.AbstractClassification
Hier>Intensional.IVAbstractEntity
IVViewDef
......
MEntoR
8/9

9/9
Clairvoyant

Mining Entities to Rules with MEntoR

Recommended

Recommended

More Related Content

Similar to Mining Entities to Rules with MEntoR

Similar to Mining Entities to Rules with MEntoR (20)

More from kim.mens

More from kim.mens (20)

Recently uploaded

Recently uploaded (20)

Mining Entities to Rules with MEntoR