Post Module | Delete Post

# Creating Post Process

## User Story

As a user, I need the ability to delete posts from the platform's collection. When I identify a post that requires removal, I want to initiate the deletion process. If the post I intend to delete is not found, the system should display a message indicating that the post is not available for deletion.

## Task

1. Implement Data Access Object (DAO) Layer.
2. Implement Service Layer.
3. Create JUnit Test Cases.
4. Ensure that the test cases are passing.
5. Write clear and concise comments in the code to explain complex logic.

## DAO

- `deletePost()`: Allows the removal of a post from the platform's collection.

## Service

- `deletePostService()`: Manages the post deletion process using the Service Layer.

## JUnit Tests

- `testValidDeletePost()`: Tests the successful deletion of a post.
- `testInvalidDeletePost()`: Tests the scenario when the requested post isn't found for deletion.

## Estimation

Estimated time for completion: 3 hours

## Flowchart

```mermaid
graph TD
Start --> UserInitiatesPostDeletion
UserInitiatesPostDeletion --> SearchPostToDelete
SearchPostToDelete -->|Post Found| ConfirmDeletion
SearchPostToDelete -->|Post Not Found| NotifyPostNotFound
ConfirmDeletion -->|User Confirms| DeletePost
DeletePost -->|Success| NotifyDeletionSuccess
DeletePost -->|Failure| NotifyDeletionFailure
NotifyPostNotFound --> EndNotFound
NotifyDeletionSuccess --> EndSuccess
NotifyDeletionFailure --> EndFailure

No source paths are named; start by locating the post DAO and service entry points and existing JUnit conventions. Implement the listed deletePost and deletePostService behavior, including the not-found message, then run testValidDeletePost and testInvalidDeletePost. Done means both tests pass.

Written by the indexing model from the issue text.