The Cha-Q Meta-Model: A Comprehensive, Change-Centric Software Representation
1. The Cha-Q Meta-Model:
A Comprehensive, Change-Centric
Software Representation
Coen De Roover, Christophe Scholliers,
Angela Lozano, Viviane Jonckers
Javier Perez, Alessandro Murgia,
Serge Demeyer
2. Cha-Q Meta-Model
➜ to be shared by prototypes for analyzing, repeating, tracing changes
first interconnected representation of:
✓ state & evolution of the different entities of a software system
change
✓ each change to an entity that results in a new entity state
snapshots
✓ system snapshots under control of a VCS
object-oriented (i.e., each concept and relation is represented by a class)
driven by positive experience with FAMIX, RING/C/H, Cheops
memory-efficient tracking of states
driven by poor scalability reported for Hismo and Syde
4. Change: Overview of Representation
predecessor states are accessible
applying a change
results in a new
entity state
and might trigger derived
changes to other entity states
to enable reverting,
changes keep track of old state
of modified or deleted entity
PropertyChange hierarchy mirrors
PropertyDescriptor hierarchy
insert an entity at a particular position in a list of entities
5. Change: Change Dependencies
a change object c2 depends upon
another change object c1 if
applying c2 without c1 would violate
invariants of the meta-model
transactional dependency:
both are part of the same transaction which schedules c1 before c2
e.g., program transformations
containment dependency:
the subject of c1 is the owner of the subject of c2
e.g., owner of a field declaration is its declaring class
type/method/variable dependency
c1 creates a type/method/variable declaration referred to by c2
e.g., type of a parameter declaration
6. Evolution: Overview of Representation
accumulates the effect of one or more changes
represents the state of the system at a
particular point in time, as seen by a particular
developer
each EntityState knows in which
Snapshot to start looking up
EntityIdentifiers
the values of an EntityState’s
properties are EntityIdentifiers
subclasses
represent system
artefacts that are
subject to change, of
which the evolution is
to be tracked
modeled after languageindependent FAMIX3 meta-model
modeled after abstract
grammar of JDT (Java) and
OmniBrowser (Smalltalk)
enables tracking the
evolution of an entity
throughout its lifetime
PropertyDescriptor
describes the name, owner and
value type of each property
7. inheritance (ID12)
class Lion (ID4)
package Model (ID1)
subclass -> ID4
superclass -> ID3
Evolution: Memory-Efficient State Tracking
classes -> {ID2, ID3, ID4}
inheritance -> ID12
class Zoo (ID2)
class Animal (ID3)
attributes -> {ID5}
methods -> {ID6, ID7}
methods -> {ID8}
method eat (ID8)
copying an entity each time its state (ID6)
changes isaccess (ID9)
expensive
method addAnimals
accesses ->
->
for snapshot-centric Hismo {ID9}
model: 70minaccessor-> ID5
for fullID6
snapshot copy of 350MB
attribute animals (ID5)
references -> {ID10}
attribute
for change-centric Syde model: 3GB for SVN repo of 78MB created in
reference (ID10)
invocation (ID11)
method feedAnimals (ID7)
snapshot
source -> ID6
target -> ID3
sender -> ID7
receiver -> ID8
invocations -> {ID11}
selective cloning is difficult to implement
all entities are transitively interconnected
predecessor
pointer
Snapshot 2
snapshot's elements
Model
Zoo
animals
addAnimals
feedAnimals
access
refers
Animal
name
eat
invokes
modified
package Model
removed class
Lion (ID4)
identifier-based technique used by
Orion and Ring/H meta-models
ID1 -> package Model
ID2 -> class Zoo
ID3 -> class Animal
ID4 -> X
ID5 -> attribute animals
ID6 -> method addAnimals
ID7 -> method feedAnimals
ID8 -> method eat
ID9 -> access addAnimals::animals
ID10 -> reference addAnimals::Animal
ID11 -> invocation feedAnimals::eat
ID12 -> X
ID13 -> attribute name
performing a PropertyChange:
removed
inheritance
Lion::Animal
(ID12)
package Model (ID1)
classes -> {ID2, ID3}
attributes -> {ID13}
methods -> {ID8}
class Zoo (ID2)
attributes -> {ID5}
methods -> {ID6, ID7}
method eat (ID8)
method addAnimals (ID6)
accesses -> {ID9}
references -> {ID10}
attribute animals (ID5)
method feedAnimals (ID7)
invocations -> {ID11}
attribute name (ID13)
class Animal (ID3)
added attribute
name (ID13)
modified class
Animal
1/ clone EntityState
2/ update snapshot’s mapping
from ID to clone
3/ update property value
in clone
access (ID9)
accessor -> ID6
attribute -> ID5
invocation (ID11)
reference (ID10)
sender -> ID7
receiver -> ID8
source -> ID6
target -> ID3
created in snapshot
shared with a
previous predecessor
pointer
[Uquillas 12]
8. Versioning & Issues: Overview of Representation
revisions can be associated with a logical branch,
identified by a site-specific BranchIdentifier
a modification report
is associated with each
snapshot placed under
version control
multiple successors
and predecessors
accommodate physical
branching and merging
reports can mention and
close reported issues
issue-related information is
subject to change, and hence
represented by EntityState
subclasses
9. Implementation Highlight: Annotation Metadata
v1
public class BreakStatement extends Statement {
@EntityProperty(value = SimpleName.class)
private EntityIdentifier label;
!
annotation for properties of
which evolution is to be tracked
public EntityIdentifier getLabel() {
return label;
}
}
public void setLabel(EntityIdentifier label) {
this.label = label;
}
!
v2
public class BreakStatement extends Statement {
@EntityProperty(value = SimpleName.class)
private EntityIdentifier<SimpleName> label;
!
public EntityIdentifier<SimpleName> getLabel() {
return label;
}
}
public void setLabel(EntityIdentifier<SimpleName> label) {
this.label = label;
}
!
more typesafe version,
obtained through our own rewriting tool!
11. Implementation Highlight: Disk Footprint
evolution of Exapus project (http://github.com/cderoove/Exapus)
single revision: 194149 nodes, 223979 properties, and 194147 relationships of 32 distinct types
on average: 22,5 files per revision changed
4000"
3500"
3000"
Database'Size'(mb)'
'
2500"
2000"
confirms advantages of state sharing previously
observed in Orion and Ring/H meta-models
Naive"
Cha3Q"
1500"
1000"
500"
but for graph-persisted rather than Smalltalk-persisted meta-models
and for more fine-grained information (e.g., AST nodes)
0"
1"
2"
3"
4"
5"
6"
7"
8"
9"
10" 11" 12" 13" 14" 15" 16" 17" 18" 19" 20" 21" 22" 23" 24" 25" 26" 27" 28" 29" 30" 31" 32" 33"
Revision'
12. Conclusions
defines the first interconnected representation of:
✓ state & evolution of the different entities of a software system
change
✓ each change to an entity that results in a new entity state
snapshots
✓ system snapshots under control of a VCS
implementation highlights:
+
✓ memory-efficient
=
✓ familiar OO API for tool builders
http://soft.vub.ac.be/chaq/ for upcoming tools that share our meta-model!