Project Name: Music Event System link: https://music-event-system-m4bh.onrender.com/login.jsp
| Name | Student ID | |
|---|---|---|
| Jie Zhou | 1442449 | qiwang4@student.unimelb.edu.au |
| Baorui Chen | 1320469 | baoruic@student.unimelb.edu.au |
| liuming Teng | 1292608 | liumingt@student.unimelb.edu.au |
| Linjing Bi | 1369370 | linjingb@student.unimelb.edu.au |
This is an online ticket booking platform for live music events in Australia. The application features:
- An Administrator overseeing venue management and all system users.
- Event Planners who list and manage their events. They can adjust event details and ticket prices.
- Customers who search and book tickets, either by act name or through a 6-month calendar view.
- Venues, managed by the Administrator, have various sections like mosh and VIP, with prices varying by section and artist. No payment system is integrated; simply reserving a ticket confirms a booking.
Deliverables
- Use Case Diagram: Illustrates interactions between actors and use cases, including relevant relationships. Available in the report within docs/part1.
- Use Case Descriptions: Each use case is detailed with associated actors and a high-level description, in line with Appendix E – Simplified use cases.
- Domain Model: A representation of the application's core entities and their relationships. Accompanied by a descriptive explanation.
- Report: Our detailed report, including the aforementioned elements, can be found here.
Deliverables
- Patterns Implemented:
- Domain model
- Data mapper
- Unit of work
- Lazy load
- Identity field
- Foreign key mapping
- Association table mapping
- Embedded value
- A chosen inheritance pattern
- Authentication and Authorization
- Software Architecture Design (SAD) Report:
- Contains the class diagram of our application.
- Detailed description of patterns used with contextual examples, supplemented by relevant diagrams.
- Design rationale for patterns like unit of work and lazy load.
- The full report is available here.
-
Database & Sample Data: Our deployed app includes a populated database with realistic data samples, essential for testing. Database information and data samples can be found here.
-
Usage Instructions:
- Administrator Login:
- Username: [Admin1]
- Password: [123123]
- Planner Login
- Username: [joker]
- Password: [123]
- Customer Login
- Username: [superman]
- Password: [123]
- Additional instructions on using existing data are provided. Make sure to refer to the provided data samples for a comprehensive understanding.
Deliverables
- Concurrency Implementation: *We've addressed multiple concurrency issues specific to our application domain. Details of each identified concurrency problem and its solution can be found in our SAD Report.
- Software Architecture Design (SAD) Report:
- Contains the updated class diagram with highlighted changes.
- Detailed discussion on identified concurrency issues, our chosen patterns and mechanisms, and the rationale behind our decisions.
- Details of our testing strategy and the results of the concurrency tests. The full report is available here.
- Database & Sample Data: Our application includes a populated database with realistic data samples essential for testing. Database details and sample data can be found here.
- Usage Instructions:
- Administrator Login:
- Username: [Admin1]
- Password: [123123]
- Planner Login
- Username: [joker]
- Password: [123]
- Customer Login
- Username: [superman]
- Password: [123] Follow the provided data samples to comprehend the application's data flow. Ensure you refer to the data samples for understanding.
Additional Information:
- The complete application has been deployed on Render and can be accessed here.
- All relevant documents and reports are available in the docs/part3 directory of our GitHub repository.
- Database and data sample details are documented in docs/data-sample.
Deliverables
- Performance Report:
- A detailed discourse on system performance.
- This report can be found at GitHub (docs/part4).