Requirements Assessment‌ Clause Samples

Requirements Assessment‌. In Section 8.2 we discussed how we verified the functionality of all the “must have” requirements (Requirements 1 to 3). Therefore we conclude that our design satisfies these requirements. The design of the monitoring system is mostly platform-agnostic, although it should be easily extendable, satisfying Requirement 4. Because the components in the design are decoupled and communicate only through their interfaces through the orchestrator, the design also satisfies Requirement 5. Although the monitoring system does not use an SLA specification written in our DSL as a direct input, the monitoring specification we generate is based directly on Table 8.1: Example of test data used for scenario testing. This data was used to test the first agreement of the export scenario, also shown in Listing 8.2. Each row represents one of the test cases, with createdOn and plannedOn as inputs, and diff and timePassed as calculated variables. createdOn plannedOn diff timePassed Result 2023-10-01 12:00:002023-10-01 12:00:00Now - 12 hours 2023-10-01 20:00:00 2023-10-02 12:00:00 8 hours 24 hours 12 hours true false true Now - 36 hours 36 hours false Listing 8.2: First agreement of Listing 8.1, which checks whether an order is planned within one day. It uses two interface variables: plannedOn and createdOn. Its expression checks whether it is either not planned and less than a day has passed, or it is planned and the difference between createdOn and plannedOn is less than one day. Table 8.2: Test data used in unit testing to verify the equivalence expression solver of the analyser component. The table shows both inputs and the result, with remarks in parentheses where needed. Left Operand Right Operand Result false true false true true true 12 12 true 12 12 (different variable) true 7.5 2.5 false 7.5 7.5 true