From: Configuration Control Board

CCB Meeting 25 June 2008

Attendees

Robyn Allsman
Tim Axelrod
Roc Cutri
Robert Lupton

Proposals Discussed

Meeting

C++ Static Analyzer Tool Selection Proposal

Robyn commented on the management ground rules provided by Jeff Kantor: $20K is available for this purchase prior to October. When new budget is provided, he will revisit to determine if additional funds are available.

Robyn reviewed the prospects for C++ Static Analysis Checkers able to provide: LSST Coding Standards compliance, syntactically correct but logically erroneous constructs checking, and security check checking. Three vendors have tools are avilable for our specific platform: Programming Research, Abrabas Software, Parasoft.

Parasoft has been dismissed due to lack of response to repeated queries over 2 months.

Programming Research tool: PRQA-C++ provides the features required. Enabling customer oriented Coding Standards enforcement is an add-on; using their command line interface is a costly add-on. They do provide a variety of common coding standards filters. Startup cost for a single floating command line license is ~$32K + 20% for yearly maintenance.

Abraxas Software tool: CodeCheck seems to provide the features required; we did not test the LSST DM software stack using it (just got demo tool this week). Abraxas will assist the customer in creating the customer oriented coding standard 'ruleset' at no extra charge. The usual complexity metrics are available. They only provide graphical interface for Windows systems; Linux systems use a command-line driven interface. The text output file is setup of easy filtering by user applications. The price is low: $595/floating license; good discounts for additional seats. Abraxas Support staff (Patrick) took the LSST DM Coding Standards yesterday and said "it will take a few days, to go over your material".

Decision: Given the funding constraint, the decision is two pronged:

  • First, Abraxas Software's tool will be integrated into the DM Build environment;
  • Second: The success/failure of the integration will be reviewed in mid-September to decide if we should stay with Abraxas or wait for funding to purchase the Programming Software's tool.

Since Robyn will be gone July, Roc Cutri will ask Tom Handley (or someone else) if they can take on this task in her absence.

Action Items

  • Roc Cutri will ask Tom Handley (or others) if they have time starting in July to pursue the integration of Abraxas into the DM Build environment.