From 20c0a09bad3b6ca956e3dad42c8a8c19f7d4a8b7 Mon Sep 17 00:00:00 2001
From: Gerard Lamusse <gerardlamo@gmail.com>
Date: Tue, 22 Aug 2023 10:30:47 +0200
Subject: [PATCH] Create notificationservice.md

---
 docs/Current/notificationservice.md | 86 +++++++++++++++++++++++++++++
 1 file changed, 86 insertions(+)
 create mode 100644 docs/Current/notificationservice.md

diff --git a/docs/Current/notificationservice.md b/docs/Current/notificationservice.md
new file mode 100644
index 0000000..bd11e2e
--- /dev/null
+++ b/docs/Current/notificationservice.md
@@ -0,0 +1,86 @@
+ # Notification Service
+
+**Status**: [**Assess**|Trial|Adopt|Hold]
+
+## Description
+A service offering an interface to send short messages, with optionally one action(link), that should be sent* to either a single user or a group of users.
+
+The service should support multiple delivery channels as well as the ability for an end user to view all their notifications some place, ideally in the BCC Topbar
+
+### Context
+BCC Forbundet wants to notify users of specific groups that a new article was published
+
+BCC Event wants to notify a user when they are registered or unregistered from an event or activity
+
+### Background
+Instead of each service implementing their own notification service, we would like to consolidate the effort a nd make a simple to use service
+
+## Alternatives
+
+novu.co
+
+### Summary
+
+| #      | Title                                   | Security         | Delivery     | Sustainability | Usability    |  
+| ------ | --------------------------------------- | ------------     | ----------   | ----------     | ------------ |  
+| 1      |                                         | ✅              |              |                |              |           
+| 2      |                                         | ❌              |              |                |              | 
+| 3      |                                         | ❌              |              |                |              |     
+
+
+**RISK/BENEFIT CHECKLIST**
+
+**Security**    
+1. [] Governance: e.g. federated access control? 
+2. [] Legal: e.g GDPR compliance?
+3. [] Reputation: Security track record?
+4. [] Simplicity: easy evaluate security?
+
+**Delivery** 
+5. [] Velocity: will we develop products faster?
+6. [] Unique: does the solution provide new features/value?
+7. [] Reliability: is the solution scalable and robust?
+
+**Sustainability**
+5. [] Know-how: is it main stream, well-documented solution?
+6. [] Redundance: are we already using competing solutions?
+7. [] Cost: what are the long term running costs?
+
+
+
+### Alt 1: [Title]
+[Description]
+
+**Risks**  
+
+**Benefits**  
+
+
+### Alt 2: [Title]
+[Description]
+
+**Risks**  
+
+**Benefits**  
+
+
+
+### Alt 3: [Title]
+[Description]
+
+**Risks**  
+
+**Benefits**  
+
+
+## Assessment
+[TODO: Preliminary assessment based on assessment criteria]
+
+
+## Trial
+[TODO: Document experience after trialing]
+
+
+## Decision
+[TODO: Document final decision and update tech radar]
+