What is most valuable?
Data model development: This has built-in ways to create multiple, separate solution data models, including ways to link to an Enterprise Data Model (EDM).
Other objects are encyclopedia-wide and need a different approach for managing solution-specific diagrams with an ability to query, e.g. 'as-is' vs 'to-be'.
How has it helped my organization?
It has helped in supporting the development of an Enterprise Data Model.
What needs improvement?
The product is a very outdated software; complex to use, and the GUI is a fat client so no mobile or web access. It's not ready for the future.
For how long have I used the solution?
I've used this solution for eight years.
What do I think about the stability of the solution?
Performance can be cumbersome when foreign key updates run on large data models.
What do I think about the scalability of the solution?
We were required to split encyclopedia per business for large enterprises. We need to wisely think about how to scale.
How is customer service and technical support?
Internal service has been setup.
Which solutions did we use previously?
No, we did not use a different solution prior to IBM System Architect.
How was the initial setup?
I wasn't involved in installing the product.
What's my experience with pricing, setup cost, and licensing?
I wasn't involved in pricing-related matters.
Which other solutions did I evaluate?
Software evaluation was done nine years ago. This product was selected based on its flexibility; it can be configured to handle almost every model, but did not develop into the future since then.
What other advice do I have?
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Jul 12 2017