Table 16.
Architecture Impact on each Process using MoSCoW.
| Impact | Process ID | M | S | C | W |
|---|---|---|---|---|---|
| Employment/Human Resources | A.2, A.3, A.4, A.5, A.6, A.8, A.9, A.10, A.20 | Ѵ | |||
| Additional job desc | A.7, A.11, A.12, D.1, D.2, D.4, D.5, D.6, D.7, D.8, D.9 | Ѵ | |||
| Catalog, proposal draft, or installation manual | A.13, A.18 | Ѵ | |||
| Notifications through certain media | A.14 | Ѵ | |||
| T-Apps application changes, problem status notifications | A.15, A.16 | Ѵ | |||
| Changes to CRM and billing applications | A.17, A.19, B.1, B.2, B.3, B.6, C.4 | Ѵ | |||
| Special reports on customer problems (smart city) | A.21 | Ѵ | |||
| Billing application changes and defining the lifecycle | A.22 | Ѵ | |||
| T-Apps application changes | B.4, B.5, | Ѵ | |||
| Provision of supporting IoT infrastructure or changing the current network configuration | C.1, C.2 | Ѵ | |||
| Network capability | C.3 | Ѵ | |||
| Changes to the T-Apps application, adding pages for smart city customer users | D.3 | Ѵ | |||
| CRM application changes, specifically the CRN® interface | D.10, D.12 | Ѵ | |||
| CRM application changes, specifically the GPR® interface | D.11, D.13 | Ѵ | |||
| VRN® application changes | D.14 | Ѵ | |||
| E-mail is sent by humans or machines | D.15 | Ѵ |