You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository contains business requirements, functional specifications, and user stories for the Tazama financial crime monitoring platform. It covers four core modules: BIAR, CMS, TCS, and TRS.
Repository Structure
Markdown-files-SNCopy/
├── BIAR/ # Business Intelligence, Analytics & Reporting
│ ├── BRS/ # Business Requirements Specifications
│ ├── FSD/ # Functional Specification Documents
│ └── User Stories/ # Jira-linked user stories (57 files)
├── CMS/ # Case & Investigation Management System
│ ├── BRS/
│ ├── FSD/
│ └── User Stories/ # Jira-linked user stories (179 files)
├── TCS/ # Tazama Connection Studio
│ ├── FSD/
│ └── User Stories/
└── TRS/ # Transaction Rules & Simulation
├── BRS/
└── FSD/
Document Types
Type
Description
BRS (Business Requirements Specification)
Defines what a module must do — business rules, workflows, and acceptance criteria. Audience: business analysts, product owners.
FSD (Functional Specification Document)
Defines how the module works technically — data flows, API contracts, UI behaviour, and system interactions. Audience: developers, architects.
User Stories
Granular, Jira-linked requirements written from a user perspective. Each file corresponds to a Jira ticket (e.g. US-180) and details acceptance criteria for a specific feature or flow.
Modules
BIAR — Business Intelligence, Analytics & Reporting
Provides analytical dashboards, reporting, and data insights for Tazama operators. Built around Jupyter NotebookLab with a layered data warehouse architecture (Bronze → Silver → Gold).
Business Requirements (BRS)
File
Description
BRS/BI_Analytics_Reporting_BRS_v1.0.md
Core requirements for the analytics module — Jupyter-based analytics environment, data warehouse structure, supported data types (structured, semi-structured, unstructured), dashboard categories (management, operational, detection performance), and role-based access control via Keycloak.
BRS/BIAR_Implementation_Document_Clean.md
Implementation and deployment guide for the BIAR module — architecture overview, integration steps, and technical deployment guidance.
Functional Specifications (FSD)
File
Description
FSD/BIAR_Supplementary_FSD_Clean(1).md
Supplementary functional spec covering fraud detection dataflows from ingestion through to insights, including user stories for analytics features and reporting capabilities.
User Stories
57 user story files covering case queue management, work queue management, AI task integration (ATM module), reporting dashboards, and data lake ingestion pipelines (Apache Hudi, Apache Spark, TIKA text extraction).
CMS — Case & Investigation Management System (CIMS)
Manages the end-to-end lifecycle of financial crime cases — from alert triage through investigation to case closure. Split across three functional areas: Case Management, Investigation Management, and Alert Triage.
Business Requirements (BRS)
File
Description
BRS/Tazama_CIMS_Part_1_Case_Management_Clean.md
Requirements for case management — case creation workflows, case states, assignment and reassignment, suspension, resumption, and closure procedures.
Technical specification for the alert triage module — auto-triggering of triage tasks for new alerts and triage operation flows.
FSD/Tazama_CMS_Supplementary_FSD_Clean.md
Supplementary functional details — additional user stories, auto-trigger triage requirements, and extended alert management workflows.
User Stories
179 user story files covering the full case lifecycle: creating, completing, approving, assigning, unassigning, suspending, resuming, closing, reopening cases, reporting, and queue management.
TCS — Tazama Connection Studio
A standalone integration and data enrichment module that acts as the entry point for transaction data into the Tazama platform.
Functional Specifications (FSD)
File
Description
FSD/Tazama_Connection_Studio_FSD_v0.3_Clean.md
Full functional specification — REST API endpoint configuration, push- and pull-based message ingestion, data mapping utilities, schema validation, role-based access control, and multi-environment deployment support.
User Stories
User stories covering development phases, frontend development, DEMS integration, DE API integration, and DB migration activities.
TRS — Transaction Rules & Simulation
Provides the tooling for building, configuring, validating, and deploying transaction monitoring rules within Tazama.
Business Requirements (BRS)
File
Description
BRS/Simulation_BRS_v1.1_Clean.md
Requirements for the Simulation Sandbox — sandbox environment for testing rule processors against historical or synthetic datasets, enabling iterative rule refinement before production deployment.
BRS/Model_Management_BRS_v1.0_Clean.md
Requirements for Model Management — Rule Builder UI for rule authoring, Config UI for rule configuration and typology mapping, Sandbox for pre-production validation, and CI/CD pipeline integration with code review and deployment tracking.
Technical specification for rule building, configuration management, and sandbox simulation — covers implementation details for all Model Management and Simulation Sandbox capabilities.