147: adds 5 more requirements

requirements/A/_posts/2024-10-11-access-control-via-sso.md

@@ -0,0 +1,16 @@
+---
+title: "Access Control via SSO"
+tags: usable suitable secure
+related: access control, auditability 
+permalink: /requirements/access-control-via-sso
+---
+
+<div class="quality-requirement" markdown="1">
+
+**Context/Background**: Employees in companies often have a central username/password pair or certificate used to log in via a Single Sign On (SSO) solution, such that they do not have to maintain different credentials per system. If a new system is added to the company's portfolio, it should make use of the centralized authentication system.
+
+**Source**: User authenticates using their SSO credentials on the expert system.
+
+**Metric/Acceptance Criteria**: System performs transparently the login via SSO in less than 3 seconds. The user has their correct role and rights after login.
+
+</div><br>

requirements/D/_posts/2024-10-11-display-data-based-on-context.md

@@ -0,0 +1,16 @@
+---
+title: "Display Data Based on Context"
+tags: usable suitable
+related: adaptability, functional appropriateness
+permalink: /requirements/display-data-based-on-context
+---
+
+<div class="quality-requirement" markdown="1">
+
+**Context/Background**: The same workstation of a multi-tenant system within a factory might be used by different employees of different shifts.
+
+**Source**: User logins to start their shift.
+
+**Metric/Acceptance Criteria**: The expert system displays the screens that have been opened by the user the last time before they logged off.
+
+</div><br>

requirements/P/_posts/2024-10-11-parallel-data-modification.md

@@ -0,0 +1,16 @@
+---
+title: "Parallel Data Modification"
+tags: usable efficient secure
+related: performance 
+permalink: /requirements/parallel-data-modification
+---
+
+<div class="quality-requirement" markdown="1">
+
+**Context/Background**: In some multi-tenant systems several tenants may modify the same data at the same time. A possible solution is Optimistic Locking.
+
+**Source**: User A modifies shortly after user B has read the same data record.
+
+**Metric/Acceptance Criteria**: The system display a conflict message and displays user B the data record of user A so that user B can react to the changes of user A.
+
+</div><br>

requirements/R/_posts/2024-10-11-restore-filter.md

@@ -0,0 +1,16 @@
+---
+title: "Restore Filter after Log In"
+tags: usable suitable
+related: functional appropriateness 
+permalink: /requirements/restore-filter-after-log-in
+---
+
+<div class="quality-requirement" markdown="1">
+
+**Context/Background**: In a multi-tenant web based system within a factory, each user may need to have their work environment with their settings restored after successful log in.
+
+**Source**: User logins to start their shift and accesses a website with a table with data.
+
+**Metric/Acceptance Criteria**: The website displays the table filtered by the filter as it was configured by the logged-in user before their last log off.
+
+</div><br>

requirements/U/_posts/2024-10-11-unavailable-for-max-2-minutes.md

@@ -0,0 +1,16 @@
+---
+title: "Unavailable for max 2 minutes"
+tags: reliable usable
+related:  availability, reliability
+permalink: /requirements/unavailability-max-2-minutes
+---
+
+<div class="quality-requirement" markdown="1">
+
+**Context/Background**: If an expert system becomes unavailable, the employer has to pay the employees even though they cannot work. This is especially a problem in countries with high labour costs.
+
+**Source**: User intends to perform any operation within the expert system.
+
+**Metric/Acceptance Criteria**: The user is never blocked longer than for 2 minutes at any time due to any unavailability of the system.
+
+</div><br>