AtlasML: Add data Flow diagram

[ufukygmr]

Feature Proposal

Spec Version 0.2.0

Context

Problem

Describe the problem that is tackled in this issue
The current project documentation lacks visual representations of the system's processes and interactions, such as a data flow diagram and a use case diagram. This absence makes it harder for new developers, stakeholders, and team members to quickly understand the system's architecture and functionality.

Motivation

Describe the motivation WHY the problem needs solving. Specify the affected users/roles.

1. Improved Understanding: Visual diagrams help developers and stakeholders easily grasp the system's behavior and flow of data.
2. Ease of Onboarding: New team members can get up to speed faster by referencing diagrams rather than deciphering code or text-based documentation.
3. Alignment: Ensures that all team members have a shared understanding of the system’s workflows and use cases.

Requirements

Describe the Functional and Non-Functional Requirements of the feature. Stick to the INVEST methodology!

1. FR: <Title>:

2. NFR: <FURPS+ Category>: <Title>:

1. FR: Create a Data Flow Diagram

• Represent data flow between components, external systems, and databases.
• Use standardized symbols and notations.

2. FR2: Create a Use Case Diagram

• Identify primary actors and their interactions with the system.
• Cover all major use cases of the current system.

3. FR3: Integrate Diagrams into Documentation

• Update the relevant sections of the documentation repository.
• Ensure diagrams are clear, well-organized, and accessible to stakeholders.