Skip to main content

Modeling an Application in Txture

When modeling an application in Txture, it is crucial to accurately reflect its deployment environments and relationships. Follow these guidelines for a correct and effective application model.

Agenda​

  1. Key Concepts
  2. Property Management
  3. Assessment and Target Architecture
  4. Best Practices
  5. Example

Key Concepts​

  1. Application
    Represents a single installation of an application corresponding to a specific deployment environment, such as Testing, Production, or Staging. Each environment is modeled as a separate application asset. Each application (deployment environment) has a unique deployment stack, encompassing its infrastructure, dependencies, and configurations.

  1. Business Application
    Serves as a grouping asset for multiple deployment environments of the same application. It aggregates shared properties and facilitates a consolidated view.

Property Management​

  • Business Application
    Populate properties that are consistent across all deployment environments.

  • Application (Deployment Environment)
    Maintain properties specific to the individual deployment environment.

Assessments and Target Architecture​

The Assessment and computation of Target Architecture recommendations are performed at the level of the individual application (deployment environment), ensuring environment-specific results.

Best Practices​

  1. Environment Granularity
    Always model each deployment environment as a separate application asset for clarity and precision.

  2. Parent-Child Relationship
    Link all deployment environments (applications) to their corresponding business application for a structured hierarchy.

  3. Consistent Naming
    Use environment identifiers in application names (e.g., AppName - Production, AppName - Testing) to avoid ambiguity.

Example​

The below example shows the Business Application "Inventory Control" that consists of two deployment environments, a production and a testing environment.
Each deployment environment is represented by a dedicated Application asset. Each Application has its own deployment stack with Database, Technical Component and Virtual Server assets. The use of an asset such as a database from multiple environments is possible, but not shown in this example.