Technical Glossary
From SynerTrade
| EXPRESSION | DESCRIPTION |
|---|---|
| Back-end | All API, Business logic and DB related aspects, typically referring to scope / TT of the BE team / java |
| Card | Widget; replacement of a -> portlet, that contains various data, often in a graphical way |
| Cloud | Highly scalable, decentralized managed service infrastructure. Knows three service layers [[1]] - IAAS > such as AWS or Azure |
| Core | Refers to the pages build in old technology (“monolithic block”). Everything that is not core is built in new technology. |
| Deployment | The act of installing an application to a server / cloud infrastructure. The resulting software on the server is called Deployment Artefact. |
| Entity | Any value in a list of values belonging to an object. E.g. one specific LE, SBU, Payment Terms or UOM. |
| Ext JS | Name of the FE library used to build the pages in the new architecture; Ext JS has a client and a server side implementation |
| Front-end | All client and UI related aspects, typically referring to scope / TT of the FE team / javascript |
| Hybrid Cloud | mixture of Public Cloud and Private Cloud elements with distinct interfaces [[2]]
This is the setup we have for the Supplier Portal (PubCloud) vs. Invoice (PrivCloud) architecture |
| Infinite scrolling | Loading on demand additional records when scrolling thereby pre-loading the next batch of data; initial load is to fit page plus 2. batch |
| Kernel | The very central and connected entities and services of XLR8 without which the application cannot exist and which cannot be deactivated / not used. SDB, CDB, PDB, AO. An extended kernel definition includes WFE, DMS, SSP and search. |
| Permission | Is a system property granting one or more users (usually all of a certain role) of a system access to a specific resource. |
| Portlet | Container of information (typically in form of a list) in the -> Cockpit |
| Private Cloud | internally managed cloud, usually within an Intranet [[3]] |
| Public Cloud | externally available cloud [[4]] |
| Role | An abstract definition of an arbitrary responsibility within a digital system. Usually applicable to one or more users of the system |
| Row | A record in a table |
| Test case | A description of the tests to be conducted to validate the implementation. TCs are distinguished in functional (related to UC / US) and technical (related to browser, performance, persistence …) and are conducted manually or automatically. |
| Transaction | transaction processing is information processing that is divided into individual, indivisible operations called transactions. Each transaction must succeed or fail as a complete unit; it can never be only partially complete [[5]] |
| Workflow | The formal digital specification of business processes, providing a link between actions / tasks and actors (users). Constraints are usually defined by rules, which should be independently declared from an arbitrary workflow |
| Widget | Graphical element, often based on a standard from the FE framework Ext JS |
