Notification System
Examples
Description
A notification system is a component responsible for delivering messages to a user, system, or external service when a relevant event occurs within the information system. Its role is to alert the recipient to situations that require their awareness or action, allowing the system to communicate state changes, results, or exceptional conditions without direct human intervention. It can vary in complexity: from basic mechanisms that send an email when a single event occurs, to infrastructures that coordinate multiple channels and priority levels.
Mandatory capabilities
Mandatory capabilities
- Runs automatically in response to a system event or condition, without user intervention
- Communicates synthesized information, oriented toward action or toward following up on processes
- Can deliver messages through multiple and diverse channels (email, SMS, push, webhook)
- Can be configured for different audiences (end users, administrators, external systems)
- Generates messages from templates and variable data, personalizing the content according to the recipient or the event
Additional capabilities
Additional capabilities
- Recipient preferences: lets users configure which notifications they want to receive, through which channel, and how often (opt-in/opt-out)
- Grouping and periodic digest: instead of sending each notification individually, groups events and delivers them as a summary at defined intervals
- Escalation: resends or escalates the notification if the recipient does not acknowledge it within a defined time frame
- Manual sending: lets an authorized user trigger a predefined notification on demand, choosing the recipient and the parameters
Boundaries
What it is not
Information flow
Input
System event or condition that triggers the notification; recipient data and message content
→
Output
Message delivered to the recipient through the corresponding channel
Variants
- Transactional: confirmation of a user action (e.g., payment confirmation, successful registration)
- Promotional: notice about offers or new content (e.g., a new mobile plan)
- Alert: notice about a condition that requires attention (e.g., low battery, threshold exceeded)
- Scheduled: sent at regular intervals, independently of any single event (e.g., weekly summary)
- Emergency: critical, high-priority communication that interrupts the recipient (e.g., earthquake alert)
Typical dependencies
- Autonomous processes or system events that trigger the notification
- Messaging service or communication channel (SMTP, push API, SMS gateway)
- Database holding the repository of recipients and their preferences
Mapping to the Digital Board
Manual UpdateOptional
Automatic UpdateNo
Data ConceptsAlways
On-Demand OutputsNo
Automatic OutputsAlways
Autonomous ProcessesAlways
| Section | Relationship | Notes |
|---|---|---|
| Manual Update | Optional | Configuration of notification preferences by the user. |
| Automatic Update | No | — |
| Data Concepts | Always | The generated notifications and the message templates, together with the repository of recipients and their preferences. |
| On-Demand Outputs | No | — |
| Automatic Outputs | Always | The messages sent automatically in response to system events. |
| Autonomous Processes | Always | The logic that evaluates events and conditions and triggers the notifications. |
Digital Board example
Manual Update
Notification Preference Settings
Data Concepts
Notification
Message Template
On-Demand Outputs
—
Automatic Update
—
Autonomous Processes
Order Event Evaluation
Automatic Outputs
Order Confirmation
Shipping Alert