Mining Entities to Rules with MEntoR

transcript

Mining Entities to RulesMEntoR

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

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’

Motivation3/9

how to add a new action to the app?

let me see

Motivation3/9

how to add a new action to the app?here!

Motivation3/9

Source code is reliable

how to add a new action to the app?

Motivation3/9

are there other examples of actions?here!

Motivation3/9

which other methods should I add?here!

Motivation3/9

Source code is reliableIt condenses design knowledge

which other methods should I add?

Motivation3/9

are all actions implemented using the command pattern?

Motivation3/9

are all methods related to actions documented?

Motivation3/9

All developers need such knowledge to keep consistency

Motivation3/9

We need automatic support to detect design knowledge in the code

--------------------------CId>Action Impl>performAction -Impl>isUndoable -Hier>AddObjectAction -Ref>MenuService

AbstractAddAction ------X ----------------- X ------------------------X -----------------------X ---------------------X

AddObjectAction --------X ----------------- -------------------------------------------------------- ---------------------X

ImplicationsH>ArrayedCollection ==> Id>'Array'

True in a closed world

Subset relation in the FCA latticeH>ArrayedCollection

Id>Array

ArrayedCollection Array CharacterArray

Characterizing Collection Classes

AttributesAttributesAttributesAttributesAttributes

Collection * *

SequenceableCollection * * *

OrderedCollection * * *

ArrayedCollection * * * * *

Array * * * *

CharacterArray * * * *

ImplicationsH>ArrayedCollection ==> Id>'Array'

True in a closed world

Subset relation in the FCA lattice

AsssociationsH>Collection --83%--> H>SequenceableCollection

Most collections are sequenceable; but Collections is not

Superset or siblings relation in the FCA lattice

H>ArrayedCollectionId>Array

ArrayedCollection Array CharacterArray

H>Collection

H>SequenceableCollection

SequenceableCollection OrderedCollection ArrayedCollection Array CharacterArray

Collection

AttributesAttributesAttributesAttributesAttributes

Collection * *

SequenceableCollection * * *

OrderedCollection * * *

ArrayedCollection * * * * *

Array * * * *

CharacterArray * * * *

Condition*Conclusion

A regularity is a set of intersecting rules6/9

CId>ActionHier>IntensiVEAction

A regularity is a set of intersecting rules

. . . . . . . . . . . . . . . . . . . . . . .

Rule 1:CId>Action ==>Hier>IntensiVEAction

Impl>performAction

Impl>undoActio

. . . . . . . . . . . . . . . . . . . . . . .

Rule 2:Impl>undoAction ==>Impl>performAction

Impl>performAction

Impl>undoActio Hier>AbstractAction

Impl>name. . . . .

. . . . . . . . . .

. . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

Rule 3:Hier>AbstractAction -->Impl>name

Impl>performAction

Impl>undoActio

23 classes match

Hier>AbstractAction

Impl>name. . . . .

. . . . . . . . . .

. . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

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

MEntoR

. . . . . . . . . . .

MEntoR

. . . . . . . . . . .

the entity is classified as

MEntoR

. . . . . . . . . . .

an error

of the ruleThursday 16 December 2010

MEntoR

. . . . . . . . . . .

an error

MEntoR

. . . . . . . . . . .

an error

satisfied example

MEntoR

. . . . . . . . . . .

an error

satisfied example

MEntoR

. . . . . . . . . . .

an error

satisfied example a suggestion

8/9 MEntoR

MEntoR8/9

Context is given by the entity in focus

MEntoR8/9

Entityin

Context is given by the entity in focus

8/9 MEntoR

Selected rule

Shows the rules related to the entity in focus

MEntoR

Selected rule

Shows the rules related to the entity in focus

MEntoR

Rule pretty printed

MEntoR8/9

Entity in focus

MEntoR8/9

Entity in focus

Errors

MEntoRRules in which the entity complies with the condition

but not with the conclusion (errors)

MEntoR8/9

MEntoR

Entity in focus

Rules in which the entity complies with the condition and with the conclusion (satisfied)

MEntoR

Satisfied rulesEntity in focus

MEntoR8/9

MEntoR

Entity in focus

Rules in which the entity complies partially with the conclusion but not with the condition (suggestions)

Suggestions

MEntoR

Entity in focus

MEntoR

Entity in focusTag

options

MEntoR

Entity in focus

Rule View

IVAbstractEntityIVCheckeableEntity

IVComposableEntityDefinitonIVPersistentEntity

UncheckedEntityEditor

CId>EntityHier>Classifications2.AbstractClassification

Hier>Intensional.IVAbstractEntity

IVViewDef

......

MEntoR8/9

IVAbstractEntityIVCheckeableEntity

IVComposableEntityDefinitonIVPersistentEntity

UncheckedEntityEditor

CId>EntityHier>Classifications2.AbstractClassification

Hier>Intensional.IVAbstractEntity

IVViewDef

......

MEntoR8/9

9/9 Clairvoyant

Mining Entities to Rules with MEntoR

Technology