How prajwal-v-naik/movie_ticket_booking works
Main Components
• User Interface (UI) Pages:
• LoginPage.java – The entry point for user login.
• SignUpPage.java – Registration page for new users.
• MovieSelectionPage.java – Allows users to browse and select movies.
• PaymentPage.java – Handles payment interactions and transactions.
• Core Logic and Utilities:
• Main.java – Likely the central driver or initialization class.
• AuthUtil.java – Contains authentication/authorization related functionality.
• Data Layer:
• CSV Files (movies.csv, users.csv, booked_seats.csv, receipt.csv) – Serve as the persistent storage for different entities such as user data, movie listings, bookings, and receipts.
Diagramming the Relationships and Interactions
• UI components as the primary interaction points. They should be grouped visually to indicate the “front-end” or user-facing side.
• Flow from LoginPage → (via AuthUtil) → SignUpPage (if registration is needed) → MovieSelectionPage → PaymentPage.
• Main.java as the component that initiates the application and may coordinate the interaction between multiple UI components.
Highlighting Architectural Patterns
• The “View” is represented by the different Page classes (LoginPage, SignUpPage, etc.).
• The “Model” is the CSV-based data store.
• The “Controller” role is implicitly played by Main.java and AuthUtil.java coordinating application flow.
• Stress the importance of clear data flow and dependencies—especially how data movement happens between the UI and the CSV storage.