My team is using the IBM's Rhapsody tool to do real-time embedded development. Unfortunately, we are unhappy with our current review process.
More specifically, we've had difficulty because:
- there is a lack of a good diff tool for diagram changes
- the Rhapsody diff tool doesn't generate reports that you can use in a review
- source file history is spotty because source files are products in MDD thus not configured in a VCS at a high granularity
- running diffs on source code sometimes pulls in unrelated changes made by other devs
- sometimes changing a property of a model element changes dozens of source files
- it's easy to change a source file through a property change and not know it
Does anyone have any tips for making peer reviews on Rhapsody development robust but low-hassle? Any best practices and lessons learned you would like to share? I'm not looking for a mature process write-up; tidbits I didn't know about would be great.