How joha546/unity-donors works
Main Components Identification
a) Presentation Layer (Frontend)
• MVC Views (located in /Views directory)
• Static content (CSS, JavaScript, Templates)
• Client-side components
b) Application Layer (Backend)
• Controllers (handling business logic)
• Models (data representations)
• Helper Classes
c) Data Layer
• Entity Framework context
• Database tables and relationships
• Data access components
d) External Services
• Email/SMS notification system
• Stripe payment integration
[Client Layer]
• ↑↓
[Web Layer]
• ↑↓
[Business Layer]
• ↑↓
[Data Access Layer]
• ↑↓
[Database]
Component Details
Client Layer:
• Main views: Home, Dashboard, Registration, Finder
• User types: Donors, Seekers, Blood Banks, Hospitals
• Frontend technologies: Bootstrap, jQuery, Custom JS
Web Layer:
• Controllers (AccountsController, BloodBankController, etc.)
• Route configuration
• Authentication/Authorization
Business Layer:
• Model View (MV) classes
• Business logic components
• Helper classes
Data Access Layer:
• Entity Framework context
• Database tables (User, Donor, BloodBank, Request, etc.)
• Data access patterns
Key Relationships to Highlight
• User authentication flow
• Blood donation request process
• Donor-Seeker matching system
• Campaign management
• Stock management for blood banks
Additional Elements
Specific components:
• Security layer showing authentication
• API endpoints for external communications
• Cache layer if implemented
• Email/SMS notification service
• Payment processing service
Specific Implementation Notes
• The MVC architecture pattern
• Entity Framework integration
• Role-based access control
• Blood matching algorithm
• Real-time notification system
Technical Details
Database Schema:
• Tables: Users, Donors, BloodBanks, Requests
• Important relationships between entities
• Critical fields for blood donation matching
API Layer:
• REST endpoints
• Controller actions
• Service interfaces