Title | Description |
---|---|
tab | In graphical user interfaces, a tab is a navigational element for switching between sets of documents or forms in a single window. |
tag | In the context of Intershop 7/Intershop Commerce Management, use label. |
target cluster | in data replication, the cluster that receives (updated) data from the source cluster |
task | In agile software development, tasks are used to structure the daily work. They should be doable within 6h. Tasks cover all daily work, like implementation, specification, IAD, etc. All roles are the owners of their specific tasks. |
tax engine | A tax engine is a system that calculates the tax for products and services based on the tax class and the tax jurisdiction. |
TCC | In Intershop 7, an application for the system administrator to control the Intershop Application Server instances, as well as the applications on top of them, running in the cluster. |
tenant | From Intershop's perspective, a tenant is a merchant whose e-commerce software environment is hosted on a shared platform, which is able to serve multiple independent tenants. |
test case | Test cases are derived from user stories, system use cases and IADs. They exist in the context of system components and releases and are executed automatically or manually. A large number of successfully executed test cases generally indicates a good component and/or release quality. QA engineers own the testcases. Automatic test cases rely on test frameworks. |
test execution | Test execution describes the action of running test cases. The results are documented within the test management tool "Silk Central Test Manager" (SCTM). Failed tests normally lead to a new raised defect (in the regarding Jira project). Test execution planning is done in SCTM. Using this tool Quality Assurance defines all progression tests and regression tests (including NFR testing). The analysis of the test executions serve as input for
|
test framework | Generally, test frameworks provide software testing methods that allow for automatically testing sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures, to determine whether they are fit for use. Intershop 7 and Intershop Commerce Management support the following test frameworks:
|
test group | in A/B tests, a group of customer-xs that is presented one specific discount or content asset version |
test plan | The test plan describes the timing of necessary test tasks for a dedicated release (major release, minor release, hotfix).
|
thumbnail | in graphic user interfaces, a very small picture that shows what a larger picture looks like, or what a page of a document will look like when printed |
tier | Tiers describe the physical distribution of the functionality and components on separate servers, computers, networks, or remote locations. As opposed to layers, which describe logical groupings, the term tier refers to physical distribution patterns such as two-tier, three-tier, and n-tier. |
topic | subject discussed in a discussion forum |
total | in shopping carts/requisitions and order-xs, total price of all products, including tax, shipping, etc. |
touchpoint | Generally, a touchpoint is any interface of a product or service, a brand or a company with customer-xs or other stakeholders before, during and after a business transaction. This can include web applications, phone hotlines, retail stores, printed material, etc. With respect to e-commerce systems, the storefront applications (browser-based web shop, mobile shop) constitute customer touchpoints. |
tracking framework | |
transaction management | In general, transaction management refers to features for organizing, processing and supporting all shopping-related transactions done by customer-xs in the storefront. With Intershop 7/Intershop Commerce Management, this includes, among others
|
translation management system | A translation management system is a software that manages and streamlines the common tasks involved in the translation process - from requesting a new translation to quoting, project management, translating, editing, reviewing, desktop publishing (DTP), reporting and so on. As a minimum, these systems generally include modules for
|
trunk | In a source code management system, the trunk is a branch without a parent, i.e., the main or base version of a development artifact (source code file or directory). |
type code | Type codes are unique identifiers to denote different (sub) types of a business object. |
type definition | In Enfinity Suite 6 content management, DTDs that define the data structures that form the base for content components (complex type) and content objects (simple type.) |