The document summarizes a software architecture assignment from September. It includes two high priority drivers: Alarm Handling and Pricing. For Alarm Handling, scheduling and reducing computation overhead tactics are suggested. For Pricing, using a central pricing component and intermediary are recommended tactics. The document also includes context diagrams, component diagrams, deployment diagrams, and scenarios to describe the architecture.

1. Software Architecture:
September Assignment
Ingmar Dasseville - s0198801

2. ADD

3. ADD1
● Driver: Alarm Handling (P1)
– High Priority
– High impact on the system
● Tactics:
– Scheduling: Ideal to make optimal use of
the system according to the time
constraints
– Reduce Computation Overhead: too little
control
– Concurrency: improve throughput

4. ADD1: Alarm Handling

5. ADD1: Alarm Handling

6. ADD2
● Driver: Pricing (M1)
– High Priority
– Higher impact than Av1 (database is
already existent, pricing isn't)
● Tactics:
– Semantic Coherence: create central point
for pricing as localize the changes
– Use an Intermediary: a component
connecting the bill sender and the data,
so ripple effects are avoided
– Adherence to Protocol: the changes are
too large for one protocol to cover

7. ADD2: Pricing

8. Final Architecture
● Context
● Component
● Deployment

9. Context Diagram

10. Top Level Component Diagram

11. Lower Level: Trame Database

12. Deployment Diagram

13. Scenarios

14. New Measurement Trame

15. Anomaly Detection

16. Alarm Handling

17. Cloud based Fraud Detection
● No non-functional requirements
● Special case of Anomaly Detection

18. June vs September
● Consistency: earlier start with appendix for
self-check
● Context Diagram: components shown
● Decomposition: consistency
● Deployment: motivated
● Scenarios: consistency
● ADD: only non-functional drivers, but
focus on high-impact drivers