-
Notifications
You must be signed in to change notification settings - Fork 0
1.2. Component enumeration
harisux edited this page Feb 15, 2023
·
6 revisions
In order to enumerate / identify the main components we could use the following convention.
- Frontend solutions: FS1, FS2, FS3, ...
- Problem domains: PD1, PD2, PD3, ...
- Backend solutions (per domain): BS1, BS2, BS3, ...
But since backend solutions would be grouped per domain (as explained in section 4), we could have subordinate ID's like the following.
├── PD1 │ ├── PD1-BS1 │ └── PD1-BS2 │ └── ... ├── PD2 │ ├── PD2-BS1 │ └── ...