����
Dr. S. Ducasse rmod.lille.inria.fr stephane.ducasse.free.fr
Towards a “Tools/Process” Team for LAM !2014
1
Software is key at Lam
• Surprisingly there is no “Better Process and Tool” Team? • Just because it worked like that, does not mean it will work! • How to control changes? • How to ensure evolution?
You need dedicated tools!
It is advantageous to carry out dedicated analysis
!
!
!
!
!
règles dédiées
règles standard
Use “The” Platform to build analysis tools: Moose
Representation Transformations
Reverse
Engineering
Analyses
Evolution
5
Java C / C++ Smalltalk .NET
Data !
Model
Develop Analysis
Take decision
Dedicated Tools
!
Analysis
“an analysis should lead to a decision”
My first job
• I will connect VW to newest version of Moose!
Potential axes
• Represent Changes - Supporting merge? - Understanding changes? - Notification change center? RSS feed
• Develop your own maps • Build regression tests DB
- DSL for behavioral test? - Domain specific rules - Integrated into the commit
• Start small, agile and learn
Changes
• We developed several change model (PhDs of Uquillaz, Dias) !
• Make objects your focus of attention
Maps
!• What is key for you? • Recent activities? • Recent bugs? • Communication between packages?
Example : Who is behind package X ?
(1) Extraction
(2) Modèle
(4) Visualisation
(3) Analyses
Step : 3 - Creating the Map
JBoss at a glance !
Interactive tool Data in perspective !
(1) Extraction
(2) Modèle
(4) Visualisation
(3) Analyses
Activity Maps
Custom rules can be captured and checked daily for you.
Dedicated Analysis reports with Moose provide pertinent analysis for software elements
Reports can integrated into software process: Automated, continuous reports with integration servers
Custom RulesRule followers and breakers
green: followers orange: break < 2 rules
Red: break > 2 rules
Java Smalltalk C/C++ .NET
Moose Meta-‐Model To represent program
informa=on
...
Tudor Gîrba
����
http://stephane.ducasse.free.fr http://www.synectique.eu