What do you like best?
* Most everything you need in one place, yet cleverly designed and beautiful in its simplicity.
* The REST API makes it a breeze to integrate with in-house and third-party tools, which makes the transition process to codeBeamer much less painful.
* codeBeamer eats traceability for breakfast! You can literally track anything you desire by creating custom trackers.
* codeBeamer takes a lot of the sting out of the formal review process.
* Intland templates (e.g. DO-178) provide good guidance for engineers that are not familiar with rigorous regulatory processes.
* Innovative Kanban view for work management.
* Very decent document importation tools.
What do you dislike?
* Wiki markup: Basic document editing capability, compared to other Wiki platforms like Confluence.
* No built-in way to achieve traceability between low-level requirements and source code, down to function level. It is not common to need this level of traceability, but Level A software requires traceability down to object level code.
* No support for inline comments in live documents.
* Full text search not supported for old .doc format (however, it's easy to import these documents)
Recommendations to others considering the product
* Make full use of the evaluation period (even ask for an extension, if necessary)
* Try it on a real-world project, with a real team.
What business problems are you solving with the product? What benefits have you realized?
* Replacing fragmented in-house ALM tools with an integrated solution.
* Implementing centralized, paperless engineering requirements management.
* Facilitate tighter collaboration between the various engineering departments.
* Streamline our already onerous processes and align it more with current best practices and methodologies.