EAComposer is an innovative and simple-to-use enterprise architecture tool. Use it to manage your IT Landscape and Architecture Portfolio.

Delivered as a pure SaaS product: cloud hosted with a subscription based license model. This means no installs, automatic updates and no capital investment! Our prices are competitive and access is instant.

Features Highlights

Easily store your entire enterprise architecture portfolio in one convenient location.

A complete set of reporting and analysis features to obtain insight from your repository.

Included in your subscription is an advanced visual modeler, creating models and diagrams.

Full support for TOGAF and TOGAF ADM with 80+ real-life templates for you to leverage.

Develop technology strategies, roadmaps and reference architectures.

Simple and effective libraries to create & maintain IT Standards  and Reference Architectures.

Apply technology governance to ensure alignment with standards and reference architectures.

A secure, encrypted repository  with real-time sharing and collaboration.

Typical EA Tools Use Cases

Application Portfolio Management

An on-going goal for organizations includes rationalizing and simplifying the Application catalog.

Where are there gaps with business functions not being supported by applications or where do we have overlap with multiple applications supporting the same function?

Manage a 360 view for each application within your architecture and track information like # of users, level of $ investment, functional fit, lifecycle status and more.

A simple but effective way to manage your list of applications, interfaces, configurations and more.

Technology Risk Management

Manage the technology risk across the architecture portfolio is an annual activity for most organizations.

Which applications are reaching end-of-life and will require upgrading soon?

When looking at the configuration used by applications: where do we have applications relying on obscure or out-dated middleware applications?

Which business functions are supported by cloud deployed applications (or on the flipside where do we see opportnunity to leverage cloud applications)?

Technology Governance

With a more mature IT Architecture or IT planning function technology governance will be required.

Which projects are not aligned with our technology standards, architecture roadmaps & corporate goals?

Where is our architecture decision log, which decisions required us to deviate from our standards and resulted in creating technical debts? What are our current technology standards?

How can we make sure our roadmaps & strategies are realized by as planned by implementation projects?

Impact Analysis & Tracebility

Understanding how the architecture components are connected, their relationships. Ensuring different parts of the organization get benefits from an architecture repository is key to long term success. Impact analysis is usually welcomed by operational infrastructure folks & application development teams.

Which applications are consuming a specific interface?

What business functions are impacted by certain physical device or certain configuration (CMDB)?

What does the system architecture for application XYZ look like?

Capability Based Planning

Most organizations are using Capability Based Planning (CBP) in some shape of form as part of their overall planning.

With CBP you will have to relate the various business capabilities with the information that is important to your organization. Often this is technology related information like Applications used to support a certain Capability. But you can also link to non-technology related information like the Department responsible (often used for org changes).

Maintaining this information especially the relationships is where traditional modeling tools fall short and EA tools are required.

Complex Solution Design

When dealing with a complex solution design across multiple phases, which is often the case with any kind of transformation project maintaining, using Visio or similar tools simply doesn't work. Things change to quickly and making updates is too time consuming.

You end up with inaccurate information describing the solution which will result in program delays often exposed during testing.

What are all the interfaces we need to test in Phase 1?