Art of abbreviation

Fig 1 TinyURL idea applied to specification


Often you need to convert sentences into abbreviations so you can move further by using them rather than typing over and over same sentences. They took less space in your and your reader’s brain allowing concentrating on specification purpose and not on reading it.


My rules:
- abbreviation is bolded
- abbreviation used to describe another abbreviation is bolded too
- abbreviation built from letters explained by bolding and underlining those letters used for abbreviating

Linked Lists
Define available LL transformations (like changing ‘one to many’, ‘locked by reference’) and analyze existing UI. Some features discussed here are not implemented yet.
LL – Linked List
Cat – category, SLOS participating in LL as category
Subcat – subcategory, SLOS participating in LL as subcategory
LLL – Linked in LL (Cat can be LLL with Subcat) this means there is a record in [linked_list_value] with llv_id linking them
ALL – Application linked LL means llv_id is referenced in one or many application tables (like in [il_cip])
Link – link a Subcat with Cat – new record in [linked_list_value] created
Unlink – unlink a Subcat from Cat – record in [linked_list_value] deleted
Move – relate Subcat to different Cat – one record in [linked_list_value] deleted and one record in [linked_list_value] created
OM – one Subcat allowed to be in many Cats
OO – one Subcat can be in one Cat only
LR – locked by reference – once AL established can not Move
NLR – not locked by reference – Move allowed
To the point

  • April 24th, 2009