ESUG 2011, Edinburgh

1. humane
assessment
with Moose
Stéphane Ducasse
clearVue
INRIA
Wednesday, August 24, 2011

2. ology.org
ooset echn
Wednesday, August 24, 2011
m

3. s ment .com
m ane- asse
Wednesday, August 24, 2011
hu

4. Wednesday, August 24, 2011

5. Wednesday, August 24, 2011

6. feedback is key
Wednesday, August 24, 2011

7. feedback is key
Wednesday, August 24, 2011

8. contextual
continuous
feedback is key
Wednesday, August 24, 2011

9. complex, large
{ {
{ {
}
}
}
} { } =
Wednesday, August 24, 2011

10. = 250’000 lines of code
Wednesday, August 24, 2011

11. = 250’000 lines of code
* 2
= 500’000 seconds
Wednesday, August 24, 2011

12. = 250’000 lines of code
* 2
= 500’000 seconds
/ 3600 140 hours
~
Wednesday, August 24, 2011

13. = 250’000 lines of code
* 2
= 500’000 seconds
/ 3600 140 hours
~
/ 8 ~ 18 days
Wednesday, August 24, 2011

14. = 250’000 lines of code
* 2
= 500’000 seconds
/ 3600 140 hours
~
/ 8 ~ 18 days
/ 20 ~ 1 month
Wednesday, August 24, 2011

15. Maintenance is continuous
Development
4% Other
18% Adaptive
20% (new platforms) 4%
18%
60%
80% 18%
18% Corrective
(fixing reported errors)
Between 50% and 80% of
global effort is spent on 60% Perfective
(new functionality)
“maintenance” !
“Maintenance”
Wednesday, August 24, 2011

16. Software is like geranium...
when dead, it does not bloom!
Wednesday, August 24, 2011

17. Software is a living entity...
Early decisions were certainly good at that time
But the context changes
Customers change
Technology changes
People change
Wednesday, August 24, 2011

18. fo
rw
g
rin
ar
d
ee
en
in
ng
gi
ne
ee
er
rs
in
ve
g
re
{ {
{ { { {
} { {
}
} actual development } }
} { } } }
Wednesday, August 24, 2011

19. engineering
reverse
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

20. engineering
reverse
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

21. engineering
reverse
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

22. assessment
engineering
reverse
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

23. assessment
what is the current situation?
what can we do about it?
engineering
reverse
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

24. Current
practice
s
Wednesday, August 24, 2011

25. 50% of maintenance is spent reading code!
20%
20%
40%
80%
Between 50% and 80% of 40%
global effort is spent on
“maintenance” !
We spend a lot of money at the wrong place
with the wrong tools!
Wednesday, August 24, 2011

26. Current
practice
s
Wednesday, August 24, 2011

27. manual automatic
tailored generic
Wednesday, August 24, 2011

28. manual automatic
tailored generic
Wednesday, August 24, 2011

29. We need dedicated
tools to help us!
We need
customable tools to
control and give
feedback
Wednesday, August 24, 2011

30. apply
hypothesize
analysis
confident? interpret
act
Wednesday, August 24, 2011

31. existing apply
hypothesize analysis? analysis
confident? interpret
act
Wednesday, August 24, 2011

32. craft
analysis
existing apply
hypothesize analysis? analysis
confident? interpret
act
Wednesday, August 24, 2011

33. craft
analysis
existing apply
hypothesize analysis? analysis
confident? interpret
act
Wednesday, August 24, 2011

34. h um ane
sessm ent craft
as analysis
existing apply
hypothesize analysis? analysis
confident? interpret
act
Wednesday, August 24, 2011

35. An example: who is really behind that package?
(4) Visualisation
(3) Analyses
(2) Modèle
(1) Extraction
Wednesday, August 24, 2011

36. (2) Define a model for code ownership
(4) Visualisation
(3) Analyses
(2) Modèle
(1) Extraction
Wednesday, August 24, 2011

37. (3) Use adequate Map
Wednesday, August 24, 2011

38. Distribution Map
shows properties
over structure
(4) Visualisation
(3) Analyses
(2) Modèle
(1) Extraction
Ducass
e et al 20
06
Wednesday, August 24, 2011

39. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

40. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

41. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

42. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

43. Wednesday, August 24, 2011

44. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

45. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

46. Wednesday, August 24, 2011

47. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

48. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

49. os eboo k.org
themo
Wednesday, August 24, 2011

50. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

51. What is this made of?
Wednesday, August 24, 2011

52. Wednesday, August 24, 2011

53. What is this made of?
Wednesday, August 24, 2011

54. Class A method M
package 1
Class B method N
package 2
... ...
...
source code
Wednesday, August 24, 2011

55. Wednesday, August 24, 2011

56. classes sel
McCabe
ect:
= 21
C
#isGod
=
75
3,0
00
...
LO
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

57. assessment
what is the current situation?
what can we do about it?
engineering
reverse
{ {
{ {
}
}
}
} { }
Wednesday, August 24, 2011

58. Handling Moose
5 days to get up to speed
21 days to get proficient
Wednesday, August 24, 2011

59. Software engineers that extended Moose
Delphi/Java programmers
customized models
extended meta models
defined specific rules
Smalltalk programmers
new tools to support code integration
Wednesday, August 24, 2011

60. Moose supports Your definition of quality/risk
Example
(1) Getting bug maps
(2) What info to collect?
(3) How to present it?
Wednesday, August 24, 2011

61. Moose gives you the opportunity to control
your process.
Wednesday, August 24, 2011

62. Wednesday, August 24, 2011

63. identify
concern
Wednesday, August 24, 2011

64. identify create
concern rule
Wednesday, August 24, 2011

65. identify create
concern rule
discuss
results
Wednesday, August 24, 2011

66. identify create
concern rule
discuss
agree?
results
Wednesday, August 24, 2011

67. identify create
concern rule
discuss
agree?
results
Wednesday, August 24, 2011

68. identify create
concern rule
discuss
agree?
results
small
task?
Wednesday, August 24, 2011

69. identify create
concern rule
discuss
agree?
results
solve small
now task?
Wednesday, August 24, 2011

70. identify create
concern rule
discuss
agree?
results
solve small plan
now task? later
Wednesday, August 24, 2011

71. d ailyent
as sessm
identify create
concern rule
discuss
agree?
results
solve small plan
now task? later
Wednesday, August 24, 2011

72. Wednesday, August 24, 2011

73. Wednesday, August 24, 2011

74. asses sment
continuous
Wednesday, August 24, 2011

75. feedback is key
specific feedback is better
Wednesday, August 24, 2011

76. explicit
humane
assessment must be tailored
trained
Wednesday, August 24, 2011

77. Tudor Gîrba Stéphane Ducasse
www.tudorgirba.com stephane.ducasse.free.fr
creativecommons.org/licenses/by/3.0/
Wednesday, August 24, 2011