Improve Source Code Documentation

**Description**:

**Issue**: Improve Source Code Documentation

**Motivation**:

Maintaining well-documented source code is essential for both current and future contributors. Clear and comprehensive documentation not only makes it easier to understand the codebase but also facilitates efficient collaboration and troubleshooting.

**Scope**:

In this issue, we aim to enhance the documentation of our source code. The scope includes the following aspects:

1. **Inline Comments**: Review and add or refine inline comments within the code. Comments should explain the purpose and logic of functions, classes, and complex sections of code.

2. **Function/Method Documentation**: Document all functions and methods, specifying their input parameters, return values, and any side effects. Ensure that comments are up-to-date.

3. **File-Level Documentation**: Provide a brief description at the beginning of each source code file, summarizing its role and context within the project.

4. **Consistency**: Maintain a consistent style and format for comments and documentation across the entire codebase.

5. **Readme Update**: Ensure that the project's README file reflects the changes made in the source code documentation, providing an overview of how to navigate and understand the codebase.

**Expectations**:

By improving source code documentation, we aim to achieve the following benefits:

- Easier onboarding for new contributors who can quickly understand the code.
- Enhanced code maintainability, as contributors can make changes with confidence.
- Streamlined issue tracking and debugging processes.
- Better transparency and understanding of project components.

**Timeline**:

This issue will be an ongoing effort. Contributors are encouraged to review and enhance documentation in their respective areas of expertise. While there is no strict deadline, we aim to steadily improve the documentation over time.

**Getting Started**:

If you're interested in contributing to this effort, please follow these steps:

1. Claim the issue by commenting on it.
2. Fork the repository and create a branch for your documentation updates.
3. Identify areas in the codebase that lack documentation or need improvement.
4. Add or refine comments, ensuring clarity and accuracy.
5. Submit a pull request with your changes.

Remember, your contributions to documentation are highly valuable and greatly appreciated.