Avolution ABACUS vs. AWS CloudFormation

Well suited scenarios include IT portfolio management, project portfolio management, enterprise architecture planning, modeling of business capabilities, using standard frameworks that ship out of the box such as TOGAF, and integration with SharePoint. Less appropriate scenarios would be detailed data modeling and using the tool expecting to get model drive code execution.

Incentivized

AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.

Incentivized

• Modelling the Enterprise through the creation of catalogues and matrices of Enterprise information
• Creation of views to supports strategy execution and decision making
• Central storage of Enterprise information
• Management of a agreed meta model

Incentivized

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• More standard connectors for integration with other modeling tools could be beneficial for companies having legacy tools/fragmented toolsets.
• Better automated diagramming features would be useful.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

Highly knowledgable team and fast response times

Incentivized

- Microsoft tools are manual and data is not centralized

- ARIS is not as flexible as Avolution

- LeanIX is close, but lacks business content/accelerators that Avolution provides

- LeanIX is in the cloud and multi-user

Incentivized

We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.

Incentivized

• Positive - time to value for EA activities
• Positive - robust decision making

Incentivized

• It has a positive ROI
• Less time inverted in bugs
• More stable source code

Incentivized