Why Use Build Analyzer:

It is essential to know what is in your software before the product is shipped. Detecting unwanted code in your software product after it hits the market can result in financial and legal consequences.  Protecode Build Analyzer™ (BA) is part of the Protecode System 4 solution, and the  Open Source Software Adoption Process, that ensures that unwanted open source or third party code is not included in products that are shipped to customers. BA monitors the build process, creates a list of files that are used during the build (after the pre-processing stage), and analyzes the files that are used in the build process.

How Build Analyzer Will Benefit Your Organization:

• BA and Enterprise Server (ES) can run on the same platform.
  
• Multiple BAs can use the services of the same ES within an organization.
• BA is lightweight, easy to deploy, and works with all other reporting and management capabilities of Protecode System 4.
• It couples with all existing build processes through a simple scripted interface, can reside on a separate machine from the build servers, and does not impact the build operation.
• BA is a platform-independent application.
• BA has been formally validated by IBM and integrates with Rational Team Concert.

How Build Analyzer Works:

• BA analyzes only those files that are actually consumed during a build operation, including source files that are compiled into the final code, or object files that are linked by the core software application.
• It ensures the files used in a build process satisfy the organization’s licensing policies around open source licenses or third party copyrights.
• BA then provides a software bill of materials (BOM) and a licensing and copyright obligations report for software products.
• Working with ES, analysis results can be viewed online with a browser, or reports can be printed or exported to other applications within the organization.