PTC Integrity Review

We were evaluating PTC Integrity for the deployment for one of my clients. The major problem we faced regarding Integrity are the developments.

We found the requirement management and the version control features to be the most useful for our client. We missed out on the traceability part. For traceability, you need to develop a lot of scripts and you need a lot of background work.

The development environment is only on JavaScripts but other languages are not. For example, .NET platforms. It's not so customizable. Compared to other tools, defining user stories is a slightly more cumbersome process as an ALM engineer.

It is quite mature. 

I don't find it that scalable. Scalability is a concern for this particular tool.

The client that we have worked with for the department that we have deployed this particular solution has 120 to 140 members.

It's used on a regular basis. 

Technical support is excellent from PTC.

The initial setup was slightly complex. When we decided to have an isolated solution, PTC was not that user-friendly.

The complete deployment took around nine months to one year.

It requires four engineers for deployment and maintenance.

I head the complete ALM department at my organization. We have a team of ALM engineers across different tools, not only for PTC Integrity but also for IBM codeBeamer. 

Requirement management and software configuration management had better options. We found that they're more stable though they're not so scalable. During production time or during work time we don't have many production delivery issues.

My advice to someone considering this solution is to prepare yourself by having a good programming team that has good customization engineers. It requires a lot of programming skills.

I would rate it a seven out of ten. 

In the next release, I would like for there to not be so many scripts and programs to do workflow customization. It should be easily customizable.