September 25, 2017
Score 8 out of 10
Read Rajesh Telampudi's full review
Pros and Cons
- Source Code management: This tool is very good at source code management. I've seen some clients, where there are teams of more than 4 members, who have tough time identifying which team member is working on which code, and when the team has to consolidate, the team have to spend considerable time to understand the code changes. PTC Integrity is best at it, wherein each member can checkout and lock the file, so that other users can't use it. Also, Labeling a specific version of the code will help in easy identification, assuming that a common naming standard is used for labeling the files.
- Version Control: Even though version control is part of Source code management, this is an important aspect, since I had an instance when we wanted to identify the team who worked on a bug-fix in the code about 2 years back. Also, with the 4-digit versioning used, we were able to mark the specific version number based on the release, i.e., first digit for Major release, 2nd for minor, 3rd for Defect fix and 4th for very small bug-fix. Again, this versioning model is something we defined for our team. Versioning and branching of code is a very important aspect in IT.
- Change Management / Defect Management tool: The other feature we used was for raising and tracking defects, as well as Change Management, i.e., promoting code from Environment to environment. The process defined thru the tool was such that, a user raises a request which would be routed to another Manager for approval, after which another 2nd level Manager can approve, and then the request would be finally routed the Admin team to implement the change. This workflow can always be customized based on a team to team use. Similar workflow was also tried out for Access requests in one other team.
- Even though the tool has some cool features, the look and feel is more like an old JAVA applet view. If the GUI look and feel are improved, it would give the user a premium feel.
- One other feature as a Qlik Architect I would suggest is to implement a code merge feature for applications, so that developers can work parallel and then merge their code. This would diversify the teams to work on multiple issues in the same application/code. I did see multiple users complaining regarding this issue, and feel that this feature could be good to have.
- Integration with other servers, for easy deployment of code. Again from a QlikView perspective, if code had to be deployed, the code has to manually checked out to the administrator machine and then copied to the respective location, but this could be automated, the risk of manual intervention for promoting/migration of code will be much easier.