- Storing documents
- Requirement Management
- Feasibility Analysis
- Test Management
- Release Mangement
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of PTC Windchill RV&S, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
- Helps to advance carefully through complicated and delicate process hives.
- Improve thereby our time-to-market knowledge transfers along our portfolio.
- Enhances the performances of single step in processes as well as the processes.
- Allows for unprecedented overview in broads and in depths.
- Decent inspecificiencies give reason for double efforts emotions.
- The software replaces activities feedback to in computer alone.
- As usual certain processes can not be modeled with such software per default.
- There is the danger that steps might not be performed at all that were considered necessary before.
- Source code administration.
- Managing the version.
- Best tool for change management and defect management.
- Editing is time-consuming.
- The papers cannot be imported directly into integrity.
- It is difficult to configure PTC integrity.
- 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.
Though the UI could be better, and integration with some application servers could be better implemented, this tool is a good tool.
- 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.
- 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.
- Code repo, traceability of the code
- Sprint planning
- Spec change/risk management
- Light weight desktop client
- Better/improved web application
- 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.
What are you spending currently for this type of software solution?
How could a tool of this nature be used by your company to save money lost due to poor or inefficient design?
- 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).
- 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.
- 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.
- 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.
- Version Control Management
- Deployment is easy through the tool
- Single Repository for all the Documents, codes, deliverable.
- Easy to manage the Projects, Folders with in Projects.
- Ability to support multi users, multi projects, availability thru Citrix,
- Ability to create the new version of the same deliverable when edited which assures availability of the history of the deliverable.
- 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.
2. Have the tool representative talk to how each requirement can be addressed.
3. What other third part tools can PTC "talk to" (data transfer requirements)?
4. How can we transfer info (data, documents) to third party vendors or partners?
- Version Control
- 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
- Easy to Use
- Sometimes it was hard to roll back.
- 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.
2. Is there an offshore team as well ?
3. Are people okay with having a centralized server storing all the file information and history ?
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.