Glossary
In this section Txture-specific terms are explained.
Term | Explanation |
---|---|
6 R's | The 6 R's is a framework that is used in Txture as the foundation for the definition of cloud migration strategies. Each "R" represents a single cloud migration strategy. |
Asset | An Asset is a single object saved in the Txture Repository. It always is a member of a single Asset-Type. Example: The Asset "CRM System" is a member of the Asset-Type "Application". |
Asset-Type | Asset-Types are classes of objects ( the assets) that have Properties and Links. All Assets have an Asset-Type and inherit their Properties and Link-Types. |
Commit | A Commit is a collection of individual changes which have been applied together. Commits can be tracked in the Time Machine. |
Cloud Knowledge Engine | The Cloud Knowledge Engine contains IaaS, PaaS, CaaS and SaaS services from the hyper scalers like GCP, AWS, Alibaba Cloud or Azure as well as legacy technologies. It includes prices, locations, certifications and provides mappings between cloud and legacy technologies. |
Target Architecture Preferences | Target Architecture Preferences (former Cloud Preferences) can be set in Txture as part of the Cloud Preferences in the Transformation Cockpit. The Target Architecture Preferences allow taking into account customer-specific requirements like preferred service model, cloud provider or deployment location for calculating Cloud Proposals. |
Cloud Proposal | Cloud Proposals are suggestions regarding infrastructure, platform, container or software replacements for an application and related assets. Cloud Proposals are calculated by the Cloud Knowledge Engine and include migration actions, all involved cloud products, as well as a cost forecast based on the most relevant cost factors of the involved cloud products. |
Cloud Readiness | In Txture the Cloud Readiness is especially important during the Cloud Readiness Assessment. It is a score between 0 and 100, where a higher score indicates better cloud suitability of the assessed application. |
Comment | A Comment is a text message attached to a Link, Asset or Property value. Comments can optionally have file attachments. |
Data Completeness | The Data Completeness is a ranking used during the Assessment. It indicates if the amount of data is already sufficient for an automated assessment of the application. High Data Completeness is required for a proper assessment. |
Dependency Graph | The Dependency Report is a powerful report that graphically displays assets and their links to one another. It can be customized in many ways through Node-Style Rules. |
Link | A Link is a connection between two Assets. |
Link Type | A Link-Type is a connection between two Asset-Types and typically has a verb-like name such as "runsOn" or "communicatesWith". All Links have a Link-Type and inherit their properties. |
Maintenance Mode | The Maintenance Mode is a special, restricted mode of operation supported by the Txture server. |
Migration Strategy | In Txture the Migration Strategies are derived from the 6 R's framework. |
Node Style Rules | A set of rules that allow customizing the appearance of assets based on their properties. For example, it allows for drawing an orange background for server assets that are currently not functional. |
Property | Properties are defined for Asset-Types. Every Asset can have a value for every Property in its Asset-Type. For example, an Asset-Type "Virtual Machine" could have a property "IP Address" that takes a different value for each Asset of this Asset-Type. Each Property has a Property-Type, such as text , number or boolean . Optionally, Properties can be many-valued, i.e. several values (of the same data type) can be set on the same Asset for a Property. Properties and their relationships to Asset-Types and Link-Types can be modified in the Structure Editor. |
Query | A Query is a list of instructions to retrieve Assets from the repository. The concept is the same as in conventional databases, albeit in a different format. |
Cloud Assessment Rules | Cloud Assessment Rules can be managed in the Transformation Cockpit. They are used to evaluate the cloud readiness of applications and to provide hints on data completeness problems. |
Repository | The Repository lists the entirety of all Assets managed by a Txture server. |
Scenario | A Scenario is a sandbox useful for exploratory "what if" modeling. |
Structure | The Structure is the entirety of all Asset-Types and Link-Types. It can be visualized and changed in the Structure Editor. |
Surveys | Surveys are a powerful tool to collect missing information from the stakeholders within your organization. Users are guided through questions about the Assets they have information about. |
Report | A Report is a visualization or list of Assets. There are several types of reports such as Aggregation Over Time, the Dependency Report or the Table Report. All reports are based on a query in order to select the displayed Assets. From Version 16 on Views will be renamed as Reports in Txture. |
Report Template | Templates are similar to reports, but they have placeholders in their query. This allows applying the same report on different Assets by substituting the placeholders for actual Assets. An example would be a deployment stack Tree Report that can be used to deliver a standard way of inspecting the deployment stack of an application. From Version 16 on Report Templates will be renamed as Report Templates in Txture. |
Target Architecture | The Target Architecture is the last section in the transformation cockpit. It provides Cloud Proposals for the Target Architecture of an application and estimates the cost incurred by a proposal. |
Transformation Cockpit | The Transformation Cockpit is Txture's main component for the Cloud Transformation. The Transformation Cockpit provides an overview of each transformation section and shows upcoming tasks and actions. It is the central cockpit from which you control and drive your Cloud Transformation. |