Datrix™ source code model and its interchange format: lessons learned and considerations for future work

Authors:
Sébastien Lapierre;Bruno Laguë;Charles Leduc
Affiliations:
Bell Canada, Quality Engineering and Research, Montréal, Canada, H2Z-1S4;Bell Canada, Quality Engineering and Research, Montréal, Canada, H2Z-1S4;Bell Canada, Quality Engineering and Research, Montréal, Canada, H2Z-1S4
Venue:
ACM SIGSOFT Software Engineering Notes
Year:
2001

Citing 5
Cited 5

Experiment on the Automatic Detection of Function Clones in a Software System Using Metrics

ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
Selecting a Model Interchange Format: The SPOOL Case Study

HICSS '00 Proceedings of the 33rd Hawaii International Conference on System Sciences-Volume 8 - Volume 8
Assessing the Benefits of Incorporating Function Clone Detection in a Development Process

ICSM '97 Proceedings of the International Conference on Software Maintenance
An Analysis Framework for Understanding Layered Software Architectures

IWPC '98 Proceedings of the 6th International Workshop on Program Comprehension
Parsing C++ Despite Missing Declarations

IWPC '99 Proceedings of the 7th International Workshop on Program Comprehension

Predicting risky modules in open-source software for high-performance computing

Proceedings of the second international workshop on Software engineering for high performance computing system applications
Measuring size, complexity, and coupling of hypergraph abstractions of software: An information-theory approach

Software Quality Control
An Extensible Meta-Model for Program Analysis

IEEE Transactions on Software Engineering
A tool chain for reverse engineering C++ applications

Science of Computer Programming
CScout: A refactoring browser for C

Science of Computer Programming

Quantified Score

Hi-index	0.00

Visualization

Abstract

The Datrix team within Bell Canada has been offering its source code analysis tools to the research community for a number of years. These tools perform a number of analyses that revolve around a central model (Datrix-ASG) developed by the Datrix team, and use an interchange format similar to TA, which we call Datrix-TA. This paper intends to communicate the modeling choices that were made when creating this information model, and the lessons learned over a few years of usage.