11 docs tagged with "modeling"

When modeling an application in Txture, it is crucial to accurately reflect its deployment environments and relationships.

There are two recommended options to model logical compute clusters, such as Hypervisors or Container Engines cluster in Txture.

Database clusters are relatively straightforward to model.

The dependency report allows to visualize links between assets.

An ESB is represented by an asset of the asset-type "Technical Component", which is part of Txture's default data model for the Cloud Transformation use case.

Using Txture's default Structure model, there is a separate Asset-Type for depicting and modeling an interface between two or more applications, databases or other technical components.

While Txture offers multiple ways to import existing data or to crowd-source data, it can still be necessary to manually enter data.

How can I change the structure?

Txture’s flexible Data Model and the different modeling capabilities in its Dependency and Tree reports offer various options for representing specific architectural constructs.

The tree report is a report type specialized for hierarchical data e.g. applications and their sub components.

Using Txture's default Structure, there is a separate Asset Type for depicting and modeling clusters, such as a VMware Cluster that uses the vSphere Hypervisor.