System Architecture

The PostMyAd project in the adtech domain aims to build a global advertising community with a focus on accessibility, detailed billboard information, precise audience targeting, flexible ad scheduling, guideline compliance, transparent pricing, revenue-sharing opportunities, availability management, and a user-friendly interface.

Admin Panel Design System

The PostMyAd platform grants Super Admins extensive control over permissions for Clusterhead, Sub-admin, Advertiser, Business Owner, and Normal User roles. Additionally, Super Admins can dynamically adjust access permissions based on socket events, ensuring real-time management capabilities. The dedicated user app and web app for Super Admins facilitate comprehensive control and management, including the optimized download of scheduled ad content two hours before playtime to enhance internet usage efficiency. Each user role is equipped with specific functionalities, access rights, and responsibilities aligned with their role in the advertising ecosystem. The user-friendly interface enhances efficient management and interaction across diverse user roles, ensuring a seamless experience for all participants.

The Admin Panel of PostMyAd encompasses robust features for effective platform management. It offers detailed insights into user data, categorizing users based on distinct roles. Admins can oversee all available billboards, manage orders with advanced filters, and gain analytics insights. Device management allows control over Android boxes, and Voucher & Coupon Management facilitates the creation and tracking of discounts. Finance Management provides a financial overview, while Analytics delivers advanced insights into platform metrics. Together, these features ensure efficient and comprehensive administration.

1. Scoping:

A) Functional

<aside> 💡 Functional requirements describe the specific functionalities or features that a system or application must have . It's described in two parts module level thinking and feature level thinking

</aside>

1. Module Level Thinking:

<aside> 💡 Module Level Thinking involves organizing the functional requirements into broader modules or sections.

</aside>

Module Level Thinking.png

Overview :

The project adopts a module-level approach, focusing on Supply and Demand aspects. The Supply module encompasses a user-facing web platform and mobile apps, emphasizing user registration, billboard management, advertising campaigns, flexible scheduling, instant refunds, demographic insights, and transparent pricing. It also includes features like burner ad support, camera image viewing, guideline enforcement, and a wallet system.

On the other hand, the Demand module addresses multi-user management, authentication with two-factor authentication, CRUD operations, socket connection management, and account creation, ensuring a comprehensive and balanced system.

2. Feature Level Thinking:

<aside> 💡 Feature Level Thinking involves drilling down into the specific features or functionalities within each module.

</aside>