< UseCase Model | Table of content | Component Model >
Remark:
- The XL Spreadsheet helper file can be used in order to generate automatically the different tables
- A link to an external spreadsheet can be made in order to provide more complex model (SLA and Volumes for example) NonFunctionalRequirements
Requirements
Example - Usability
| Identifiant | Description | Origin | Level |
|---|---|---|---|
| PREFIX_NFR_2 | The SYSTEM shall allow the display of its WEB screens with a minimum resolution of 1024 * 768 | Assumption | ESSENTIAL |
| PREFIX_NFR_3 | The SYSTEM shall allow the display of its WEB screens with the browser ** Chrome ** Version 75.0. on Windows 10 (64 Bits). | Assumption | MANDATORY |
| PREFIX_NFR_4 | The SYSTEM shall be tested with a display of its WEB screens with the browser ** Firefox ** Version 68 on Windows 10 (64 Bits). | Assumption | ESSENTIAL |
| PREFIX_NFR_5 | The SYSTEM shall be tested with a display of its WEB screens with the browser ** Safari ** Version 12 on MacOs Mojave. | Assumption | ESSENTIAL |
| PREFIX_NFR_6 | The SYSTEM shall allow the display of its WEB screens in a “responsive” approach allowing the management of ‘Tablet’ orientations | Assumption | MANDATORY |
Technical Platform
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY |
|---|---|---|---|
| PROJECT_ACRONYM_Compo01_1 | The SYSTEM shall : EXAMPLE be delivered relying on DEVOPS continuous delivery |
Must Have | |
| PROJECT_ACRONYM_Compo01_2 | The SYSTEM shall : EXAMPLE display its screens using Microsoft Edge Version [TBD] |
Must Have | |
| PROJECT_ACRONYM_Compo01_3 | The SYSTEM shall : EXAMPLE display its screens using Firefox Version [TBD] |
Must Have | |
| PROJECT_ACRONYM_Compo02_4 | The SYSTEM shall : EXAMPLE implement GUI with a minimal resolution of **1024*768 ** |
Must Have | |
| PROJECT_ACRONYM_Compo03_5 | The SYSTEM shall : EXAMPLEshall implement GUI under a responsive design to cope with tablet orientation |
Must Have | |
| PROJECT_ACRONYM_Compo04_6 | The SYSTEM shall : The SYSTEM shall enable data segregation for the data owned by a tenant (Report of a Customer) |
Must Have | |
| PROJECT_ACRONYM_Compo05_7 | The SYSTEM shall : EXAMPLE display all labels in HMI in English (US) by default |
Must Have | |
| PROJECT_ACRONYM_Compo06_8 | The SYSTEM shall : EXAMPLE display all labels in HMI in other Right-To-Left languages thru language packages deployment, depending on the Browser configuration |
Must Have | |
| PROJECT_ACRONYM_Compo07_9 | The SYSTEM shall : EXAMPLE store and display the information logged in English (US) |
Must Have | |
| PROJECT_ACRONYM_Compo08_10 | The SYSTEM shall : EXAMPLE shall store all datetime information in UTC Zero |
Must Have | |
| PROJECT_ACRONYM_Compo09_11 | The SYSTEM shall : EXAMPLE shall display all datetime information according to the end user’s browser configuration |
Must Have | |
| PROJECT_ACRONYM_Compo10_12 | The SYSTEM shall : EXAMPLE store each date time with the following information in compliance with ISO 8601 Example : 2017-09-15T17:27:00Z |
Must Have |
Client Side Platform
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Persistence
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Volumes
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Transactional needs
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Internationalization
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Performance
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Security
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Re-use
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Reliability/Availability (failover)
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Disaster Recovery
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Exploitation
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Scalability
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
System limits
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY |
|---|---|---|---|
| No Requirements |
Backup/Restore strategy
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Archive strategy
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY |
|---|---|---|---|
| No Requirements |
Bandwidth
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
External Dependencies
| IDENTIFICATION | DESCRIPTION | ORIGIN (FUNC REQ) | CRITICITY | | —————— | ———– | —————– | ——— |
Architecture Dossier - Markdown Template - March 2018