Highlighting some of our research lines (March 2015 Edition)
Learn more about what we do on : http://modeling-languages.com , http://som-research.uoc.edu and http://jordicabot.com
Global Identity Enrolment and Verification Pro Solution - Cizo Technology Ser...
Research lines on MDE and SE (March 2015
1. What we’re working on –
Research lines on MDE and SE
(March 2015 Edition)
Inria Lillle
March 2015
Jordi Cabot (and colleagues)
jcabot@uoc.edu
http://modeling-languages.com
15. Define cardinality variables
Constraints on cardinalities
Assign cardinalities
Define attribute variables
Constraints on attributes
Assign attributes
Proof
Resolution of the CSP
16. Trade-offs in verification
• Decidability/termination: is
automation possible? Yes
• Completeness: proof for any input?
No, bounded verification
• Expressiveness: input language?
UML class diagram + full static
OCL
• Basic Property: Satisfiabililty
17. Exists? Post?
Find legal
final state
Find legal
initial state
Inconsistent Model Proving
Example
UML Model
OCL
invariants
OCL
precondition
OCL
postcondition
Pre?
NO
YES
NO
YES
YES
NO
Verification of the Weak Executability Property
Also applied to
machine
op1
NAC:
machine
LHS:
machine
op2
RHS:
c :Class t :Tablec2t :Cl2Tb
name
persistent
name{new}
{new} {new}
{new} {new}
74. GILA: What can labels teach you about your project?
Three simple yet powerful visualizations to better understand WHO is doing WHAT
Label Usage
User
involvement
Label
timeline
Visualize the labels used in your
GitHub project, their frequency and how
they relate to each other
Discover the most active users and
contributors per label: who opens
them? who closes them?
Understand the typical evolution of
issues under each label: when are they
discussed?, solved?, etc.
75. What can issue labels teach you about your project?
Three simple yet powerful visualizations to better understand WHO is doing WHAT
Label Usage
User
involvement
Label
timeline
Visualize the labels used in your
GitHub project, their frequency and how
they relate to each other
Discover the most active users and
contributors per label: who opens
them? who closes them?
Understand the typical evolution of
issues under each label: when are they
discussed?, solved?, etc.
76. What can issue labels teach you about your project?
Three simple yet powerful visualizations to better understand WHO is doing WHAT
Label Usage
User
involvement
Label
timeline
Visualize the labels used in your
GitHub project, their frequency and how
they relate to each other
Discover the most active users and
contributors per label: who opens
them? who closes them?
Understand the typical evolution of
issues under each label: when are they
discussed?, solved?, etc.
77. What can issue labels teach you about your project?
Three simple yet powerful visualizations to better understand WHO is doing WHAT
Label Usage
User
involvement
Label
timeline
Visualize the labels used in your
GitHub project, their frequency and how
they relate to each other
Discover the most active users and
contributors per label: who opens
them? who closes them?
Understand the typical evolution of
issues under each label: when are they
discussed?, solved?, etc.
78. GitHub Analysis
GHTorrent
RQ1. Label Usage
How many labels are used in Github? How many labels are
used per project? What are the most popular ones?
RQ2. Label Influence
For those projects using labels, does its usage influence the
evolution of the project?
GiLA
Early Research Achievement
Can we detect group of labels commonly used together? Are
there label families?
79. Label Usage in GitHub
Using Labels
122,012
3%
Not Using labels
3,635,026
97%
Lesson: Labels are scarcely used in GitHub
80. Label Influence
26.93
46.18
74.92
101.3
111.8
145.7
116.4
127.2
116.4
70.4
306.4
148.1
22.53
43.51
48.76
53.21
55.27 56.3
58.82 57.95 59.28
63.23
47.59
60.19
0
10
20
30
40
50
60
70
0
50
100
150
200
250
300
350
0 1 2 3 4 5 6 7 8 9 10 >10
# labels used in the project
Med. Time to solve % solved
On average, the percentage of solved labeled issues
tends to increase together with the number of labels
used in the project
It might come at the cost of taking more time to solve
those labeled issues
ρ = 0.80
ρ = 0.73
82. Calculating the bus factor?
“Number of key developers who would need to be
incapacitated (hit by a bus), to send the project into
such a disarray that it would not be able to proceed”
83. Why it is important?
Measuring the concentration of
information per developer
Assessing the employee
turnover risk
84. Why it is important?
Measuring the concentration of
information per developer
Assessing the employee
turnover risk
Identifying the key
developers in the project
85. Why it is important?
Measuring the concentration of
information per developer
Assessing the employee
turnover risk
Identifying the key
developers in the project
Identifying the developers
that can be lost