An interactive Excel tool to collect, prioritise and trace requirements (by Use Case) is available at empirica. Among others, it can also be used for surveys among staff and to calculate the result.
Any use of the list below must reference empirica GmbH.
Non-functional¶
Non-functional requirements capture properties of a system. These requirements address ‘hidden areas’ of the system that are important to the users even though they might not realise it.
This category is referenced with the capital “NF” or “2”.
R2.2. Auditability (AUD)¶
Specifies the following requirements associated with the degree to which the SMARTSPACES service must support independent auditing of its transactions and finances. Background: A service might also be used to directly be used for billing or other financial transactions. In such a case certain standards have to be met.
R2.2.1 Billing-Validity The service shall ensure that generated output can be used for billing services. R2.2.2 Billing-Creation The service shall generate bills that shall also be used for tax purposes (e.g. VAT). R2.2.3 Billing-FollowUp The service shall follow the status of a bill and whether it has been paid (correctly). R2.2.4 Audit-Report The service shall store all records for at least a year.
R2.3. Configurability (CNF)¶
Specifies the following requirements associated with the degree to which the SMARTSPACES service must exist in multiple simultaneous configurations or variants.
R2.3.1 Internalisation - System The service shall allow for multi language programming. R2.3.2 Internalisation - User The service shall allow for changing the language to the preferred by the user. R2.3.3 Personalisation - User User shall be able to set preferences (e.g. language) which are stored with the user account and / or as cookies.
R2.4. Extensibility (EXT)¶
Specifies the following requirements associated with the degree to which the SMARTSPACES service can be modified to meet changing requirements or goals. Background: Eventually the original set-up will or has to be extended in the future.
R2.4.1 Resource The service shall allow for adding further resource types to the system. R2.4.2 Data Source The service shall allow for adding further data sources to the system. R2.4.3 Building The service shall allow for adding further buildings to the system. R2.4.4 Floor The service shall allow for adding further floors to the system. R2.4.5 Room The service shall allow for adding further rooms to the system. R2.4.6 Zone The service shall allow for adding further zones to the system. R2.4.7 Users-Admin The service shall allow for adding further admin-users to the system. R2.4.8 Users-Staff The service shall allow for adding further staff-users to the system. R2.4.9 Preferences The service shall allow for adding further preference settings to the system.
R2.5. Scalability (SCAL)¶
Specifies the following requirements associated with the degree to which the SMARTSPACES service can be scaled up. Background: Eventually the original service will be scaled up to other sites or environments.
R2.5.1 Functional The service shall be able to allow for new functionality in one or more parts of the service. R2.5.2 Reproduction The service shall be able to be reproduced in a similar setting in form of a new instance (e.g. another municipality). R2.5.3 Extension See R2.4 Extensibility. R2.5.4 Completeness The service shall, by design, be able to cover all public buildings in the municipality of the pilot.
R2.6. Interoperability (IOP)¶
Specifies the following requirements associated with the ease with which the SMARTSPACES service can be integrated with other system (e.g., browsers, legacy applications, and required databases). Background: Web-portals are usually displayed in environments of third parties (e.g. browsers). Depending on the functionality and restrictions of the service and / or the third-party programme the service might not be fully compatible.
R2.6.1 Browser - Chrome10 & above The service shall support the listed browser. R2.6.2 Browser - FireFox4 & above The service shall support the listed browser. R2.6.3 Browser - IE6 The service shall support the listed browser. R2.6.4 Browser - IE7 &above The service shall support the listed browser. R2.6.5 Browser - Opera10 & above The service shall support the listed browser. R2.6.6 Browser - Safari4 & above The service shall support the listed browser. R2.6.7 App - Android The service shall support the listed mobile app platform. R2.6.8 App - iOS The service shall support the listed mobile app platform. R2.6.9 App - Win7 The service shall support the listed mobile app platform.
R2.7. Performance (PER)¶
Specifies the following requirements concerning the minimum number of objects that the SMARTSPACES service can support; time that is permitted for The service to execute specific tasks or to respond. Background: Users could be hindered to use the service due to limitations of the service. Reliable figures need to be identified in order to allow proper service for all users.
R2.7.1 Capacity-Users The service shall support a sufficient number of simultaneous users accessing the service. R2.7.2 Capacity-Data (any) The service shall support a sufficient number of data entries of any kind without loss of data and without restrictions to any user type. R2.7.3 Latency The service’s entry masks and functionalities shall lead to the expected result (e.g. registration, settings for certain graph) without obstructing and hindering the use of the service. R2.7.4 Response Time The service shall be usable without delay (e.g. loading of website) obstructing and hindering the use of the service.
R2.8. Reliability (REL)¶
This subsection specifies the following requirements associated with the reliability (e.g. mean time between failures, number of failures per unit time) of the system.
R2.8.1 Failure - 1 year The mean time between failures (MTBF) shall exceed 12 months. R2.8.2 Failure - 1 quarter The mean time between failures (MTBF) shall exceed 3 months. R2.8.3 Failure - 1 month The mean time between failures (MTBF) shall exceed 1 month. R2.8.4 Failure - 1 week The mean time between failures (MTBF) shall exceed 1 week.