Filter Ratings and Reviews
Filter 19 vetted PTC Windchill RV&S reviews and ratings
Reviews (1-15 of 15)
September 25, 2017
Nice Source code and Version Control tool
PTC Integrity was used by one of my client, and it is being used for past 8 yrs. PTC previously known as MKS Integrity, is used as a version control, source code management, change management and defect tracking tool. This tool is used throughout the IT Organization globally. I've been using this tool since 4-5 years, and comparing it with other tools in the market, I did initially have some problems using the functionality, but once I got used to it, I liked it a lot. The version controlling of the source code is very nicely organized, and helps in managing the code optimally. In one specific instance, we did see the tool help identifying an issue in code which was checked-in about 2 years prior. There are other features in PTC Integrity, but my main purpose was for version control of source code, and change management, used for labeling the code and promoting.
- 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.
With 20 different teams of 8 developers each working on different paced projects with one single code base, our company decided MKS Integrity would be a great solution to purchase. MKS Integrity was chosen after reviewing products by IBM, Atlassian and a few other open source products. The great thing about MKS Integrity is that it is more of a toolbox of components rather than a tool. You can take components and make them work exactly the way you want your solution to work. For example, we started off by using this strictly for an SVN replacement. We only needed a couple of projects with many sandboxes. Then we used the toolkit to migrate away from another project management tool and track all change requests through customized screens in MKS. The change requests had strict workflows, allowing better management and control over changes. Then the company designed a QA process and issue tracking within MKS. Then came the help desk software replacement with further build out of Integrity. Over time, we replaced almost all of the one off applications/solutions used by Dev, QA, HelpDesk, Business Development & Project Management into one single solution MKS.
- Independent development sandboxes that allows each team to work on projects without affecting the delivery of other projects.
- Change packages - identifying exactly what artifacts were changed for a given request (bug fix, enhancement, user story).
- Integrity objects - "building blocks" - ability to create any type of container for help desk, QA, development, requirements. These are highly customizable and some simple javascript code can help with validation and workflow triggers.
- Connectivity/client loading issues - probably not as often as I would deem a show stopper for the solution, but we had experienced a lot of connectivity issues when trying to merge or perform a backfill. Or when trying to open the integrity client, we would experience some type of configuration file corruption. We had to keep a few command prompt scripts ready to go on our desktops to kill off the old corrupted files so that integrity would launch.
- One of the selling points for Integrity was the quick rollback functionality. Yes, rolling back code was easier than other solutions with tools to inspect change packages, etc, but it required mostly manual effort.
MKS Integrity is used by one of our retail clients to store the deliverables and the ETL Codes. It is used throughout all the departments by all the teams like development, QA, UAT, Production. The biggest problem it addresses is it stores all the deliverables(whether it is document, model or Code) at a single location and assures the same codes are being deployed across the environments.
- As a Data Modeler when I created the DDL and pass it to DBAs to deploy or I deploy thru the Deployment tool, I need assurance that the same code is deployed in all the environments and it makes easy to manage all the packages in Integrity.
- As a Data Analyst If I need to provide documentation to other teams or I need to open the previous versions of the same document, it is very easy to manage hsi in MKS Integrity.
- As a Project Manager it helps us to assign the Version number to the document which is unique and assigned with in Integrity, makes easy to track the deliverables.
- I do not see any area where Integrity requires room for improvement.
PTC (MKS) Integrity is used as our Configuration/Change Management tool by our program. The problems it is addressing are: having data in one location for access by all team members; helping in the management of workflow processes involving change processes, construction, logistics, software version tracking, document version tracking.
- PTC (MKS) Integrity is a great for adapting your business processes to a tool.
- The dashboard and reporting tools are very helpful.
- Importing data is not difficult
- Development of types and fields are not difficult.
- The workflow view for each record type is very helpful when training new users.
- The reporting tool could be easier to edit when it comes selecting how output is viewed.
July 09, 2014
MKS Integrity: To use or not to use.
It is used by the engineering department primarily for software development.
- Graphical file history representation
- Release management of software builds
- Change set management
- Hot fix and feature releases
- Main trunk is not protected and has no pre-conditions before committing a fix or feature to it.
- Conducting reviews is not possible. there is no avenue for people to comment on a check in
- When working with multiple snadboxes, the client seems to freeze up and needs to be started.
MKS is used for:
- Storing documents
- Requirement Management
- Feasibility Analysis
- Test Management
- Release Mangement
- Requirement Mangement
- Feasibility Analysis
- Test Mangement
- Useability
- Ease of access
- Functionality
- Speed
July 21, 2014
MKS Review- A fairly good experience
We Used MKS Integrity at Intersections Inc (my previous workplace) basically for change control and version management for application code.
- Easy to Use
- Sometimes it was hard to roll back.
February 18, 2014
Good configuration management tool
We use MKS in my company to do several things:
- Configuration Management
- Comply with SPICE level 2.
I have found it very powerful and user friendly. Very different than PVCS or CM-Synergy.
- Configuration Management
- File control version
- Creating and assigning tasks between project members
- Share common files among several projects
- Connectivity issues sometimes becomes a problem.
PTC Integrity is being used by the Engineering Department for DO-178 and DO-254 projects.
- PTC Integrity provides full traceability from requirements down to the source code that implements the requirement.
- The GUI interface is relatively easy to understand.
- Requirements entry is easy to manage.
- Configuration of PTC Integrity can be intimidating.
- Would be nice if importing from Excel was available.
- Would be nice if more canned import wizards were available.
PTC integrity is used by couple of division at my company. It is a single access point for requirement management and traceability.
- Tracing. I can trace right from the requirement until the unit test.
- Automating the tracing based on the category.
- Simple to use.
- Editing is cumbersome.
- Cannot directly import the documents into Integrity.
- Configuring PTC integrity is not easy.
September 14, 2015
great tool for software development life cycle
It streamlined the software development life cycle.
- Code repo, traceability of the code
- Sprint planning
- Spec change/risk management
- Light weight desktop client
- Better/improved web application
September 09, 2015
The Good the Bad and the Ugly....Kinda
PTC Integrity is being used by the company that I am contracted to. As a systems engineer I help users globally to become proficient with the tool, as well has how to correctly use the tool in a systems environment capacity. Meaning we use the tool to develop requirements for the product and then verify and validate the requirements/product. It has taken the ISD (Integrated Systems Development) team two years but the software has now been adopted by the company globally. The problems that PTC Integrity helps address is the one of having project teams scattered all over the world working on the same project. PTC Integrity helps these groups to communicate and work together better and more efficiently.
- PTC Integrity helps engineers write better requirements. Better written requirements mean less issues for warranty.
- PTC Integrity provides a database that is virtually limitless. Product size or scope no longer has to be an issue.
- You don't have to save.....PTC Integrity does this for you.
- PTC Integrity lacks design and flow. It could be presented better.
- PTC Integrity does not do a good job at linking items and tracking results.
- PTC Integrity error messages do not make sense to the average user.
Integrity is being used by specific groups within our organization. Primarily it is used by analysts for requirements tracking and by QA for testing. It addresses the need to have complete organization and documentation as required by the FDA, for certain groups.
- It allows the user the ability to link all aspects of the SDLC together so that there is only one source of documentation and information rather than having to search in multiple places.
- It is very customizable to suit a particular businesses needs.
- It is helpful for all areas of software development.
- It can be overwhelming with the number of tabs, functions and ways to achieve the same result. The average user may struggle with learning the tool.
- The text editing in Integrity is weak and does not provide many options. Because of this, many user decide to use MS word instead, to document requirements.
MKS Integrity is used across the whole organization and allows our product development team to track all aspects of day to day development work .
- Version Control
- Reporting
- Traceability
- Requirements Management
- Software Build Management
- It will be nice if MKS could include features such as inline editing of documents such as a word file or an excel file, Mind-map, tagging and searching using tags
We use it to support our software development process. It is used in software development department. We keep records of all activities, task, code outputs, code review, requirements and documents. Most of the time we do not use it directly since we have a custom internally developed tool that automates a lot of actions.
PTC Windchill RV&S Scorecard Summary
About PTC Windchill RV&S
Categories: Agile Development, Application Lifecycle Management (ALM)
PTC Windchill RV&S Competitors
Rally Software (formerly CA Agile Central)
PTC Windchill RV&S Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |