# Glossary (nomenclature)

# Codebase development over time

Designer configuring the solution meta models

[![TsDesignerStat.png](https://wiki.tsnocode.com/images/3/30/TsDesignerStat.png)](https://wiki.tsnocode.com/index.php?title=File:TsDesignerStat.png)

  
Engine handling the solution meta models

[![TsEngineStat.png](https://wiki.tsnocode.com/images/c/ce/TsEngineStat.png)](https://wiki.tsnocode.com/index.php?title=File:TsEngineStat.png)

  
Tempus Serva core databases

[![TsDatabaseStat.png](https://wiki.tsnocode.com/images/5/55/TsDatabaseStat.png)](https://wiki.tsnocode.com/index.php?title=File:TsDatabaseStat.png)

  
Client side scripting

[![TsScriptStat.png](https://wiki.tsnocode.com/images/e/e0/TsScriptStat.png)](https://wiki.tsnocode.com/index.php?title=File:TsScriptStat.png)

  
Linux administration tools

[![TsAmazonStat.png](https://wiki.tsnocode.com/images/b/b3/TsAmazonStat.png)](https://wiki.tsnocode.com/index.php?title=File:TsAmazonStat.png)

# Objects

- Dashboard: Front-end page 
    - Widget: UI element in a dashboard
- Section: Collection of entities
- Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)
- Record: Main data holding thing (This is an object in OOP) 
    - Revision: How many times a record has been changed
- Status: Configurable state a record is in 
    - Level: Assignable number to a status
    - Action: Configurable behavior depending on status
- Field: A single data point of a record 
    - Block: Collection of fields for the purpose of access management
    - Validation: A check on whether or not a field has received correct data
    - Dependency: A field's existence can be made dependent on other things
- User group: Determines who has access to which data and features
- Codeunit: Java code for specialized functionality
- Template: Tool for automatically creating documents and interfaces by feeding values into a predefined layout.
- Interface:

# Parts

- Front-end: The system that the normal user sees
- Back-end: Where the front-end is configured
- Database: It's a database

# Platform metrics

## <span class="mw-headline" id="bkmrk-performance-indicato-1">Performance indicators</span>

Tested on a standard AWS small server

Setup

- Topology: Seperate frontend / database server
- Hardware: 4 Core CPU, 2 Gb RAM
- Software: Windows, MySQL, Tomcat
- Usecases: login, list, item, update, export

Results

- Frontend server: Average 80% CPU
- Database server: N/A
- Page throughput: 63 requests/second
- Size throughput: 421 kB/second

Results are equivilant to 500+ concurrent users

## <span class="mw-headline" id="bkmrk-high-volume-toleranc-1">High volume tolerance</span>

Setup

- 100.000 records, 5 columns each
- 20 mB export CSV file size

Results

- &lt;2 second reponse
- &lt;300 mB heap size spike
- &lt;1% garbage collection

## <span class="mw-headline" id="bkmrk-codebase-metrics-1">Codebase metrics</span>

Project metrics for source version 2489

- Java codebase: 536.529 lines
- Other sources: 161.647 lines
- Designer pages: 507
- Engine classes: 838
- Dependent libs: 90

[Codebase development over time](https://docs.tsnocode.com/books/glossary-nomenclature/page/codebase-development-over-time "SvnStatistics")