Skip to content

Functional Requirements

This section details the functional requirements for the Conference Expo Portal v2.0, broken down by major feature areas. Each requirement area is documented in its own file for clarity and maintainability.

API and Integration

  • API Design
    • RESTful API endpoints
    • Authentication and authorization
    • Error handling and validation
    • Rate limiting and security
    • Nimlogix API integration
    • Webhook management

User Management

  • User Authentication

    • Email/password authentication
    • Session management
    • Password reset and recovery
    • Security and session handling

  • User Management

    • User roles and permissions
    • Account creation and invitations
    • User profiles
    • Access control
    • User preferences

Event Management

  • Event Management
    • Event creation and configuration
    • Organiser management
    • Sponsor management and invitations
    • Event settings and preferences
    • Event status and lifecycle
    • Sponsor progress dashboards

Stand and Artwork

  • Stand Configuration

    • Stand package management
    • Stand customisation
    • Configuration approval workflow
    • Pricing and calculations

  • Artwork Management

    • Artwork upload and validation
    • Artwork review process
    • Proof approval workflow
    • Version control
    • Nimlogix integration

Payments

  • Payment Processing

    • Stripe Checkout integration
    • VAT calculation
    • Balance payments
    • Payment tracking and receipts

  • Additional Fees

    • Admin fee management
    • Fee tracking and reporting
    • Balance calculations

Communication

  • Communication and Notifications
    • Messaging system
    • Message routing
    • In-app notifications
    • Email notifications
    • WebSocket real-time updates
    • User notification preferences

System Administration

  • System Administration

    • Default settings management
    • VAT rule configuration
    • Deadline configuration
    • Event-specific overrides
    • Admin-only access

  • FAQ Management

    • Central FAQ library
    • Event-specific FAQ overrides
    • Category management
    • FAQ inheritance

Each requirement file follows a consistent structure:

  • User Stories
  • Functional Requirements
  • Key Entities
  • Edge Cases

For detailed technical specifications, see the Architecture document.