|
|
|
[placeholder] |
|
|
\ No newline at end of file |
|
|
|
## LUT Structure
|
|
|
|
The LUT is implemented via a dockerized [PostgreSQL][PSQL] database, consisting of a single table, which is for convenience visualized below. As per standard database etiquette, the top row denotes the names of the columns of which the LUT is comprised. Each individual cell on the second row contains essential information that is needed in order to properly interact with the database.
|
|
|
|
|
|
|
|
|name |im1 |im2 |im3 |
|
|
|
|
|-------|-------|-------|-------|
|
|
|
|
|**string** type. This corresponds to the name of the proposed code refactoring. All names are acceptable, as long as they don't already exist in the LUT.|**int** type. The expected impact that the refactoring will have on **Energy**. The only acceptable values are -2, -1, 0, 1, 2. | **int** type. Expected impact on **Technical Debt**. Same value space as **im1** | Expected impact on **Security**. Same rules as for **im1**, **im2**. |
|
|
|
|
|
|
|
|
Below a mapping of the impact values to their actual lexicographical meanings is provided. Integers were preferred for the actual API in order to avoid trivial problems such as typos.
|
|
|
|
|
|
|
|
|value |meaning |
|
|
|
|
|-------|---------------|
|
|
|
|
|-2 |Greatly Worsen |
|
|
|
|
|-1 |Worsen |
|
|
|
|
|0 |No Impact |
|
|
|
|
|1 |Improve |
|
|
|
|
|2 |Greatly Improve |
|
|
|
|
|
|
|
|
[PSQL]: <https://www.postgresql.org/> |
|
|
\ No newline at end of file |
