- Teamwork support
- Price policy
- Support of many modelling languages
- Documentation generation incorporation
From the island of non managed analysis and design information to shared repositories with templates. It has helped us with real MDA and code generation directly into Visual Studio.
We've been using it for at least eight years, since v7.
We've had no deployment issues.
MS Office integration works only with local .eap repository files, not with our Postgres repository. Half a year ago they promised to fix this bug, but still no improvement.
We've had no issues scaling it to our needs.
It's sufficient.Technical Support:
Rational - no DB repository and it needed to be merged among the team members as XML files via external versioning system. Documentation, requirements, development all needed to be bought as separate tools which was too expensive. It crashes when a project (repo in files) is really big. There's no possibility to merge in real time and this can last hours, and often crashes.
It was straightforward.
We did it in-house.
It's sufficient, nothing to change with the pricing.