| 9 | | These techniques are important because in a real system the database is not used only for storing data, but also for producing meaningful insights such as guest statistics, financial reports, venue utilization analysis, RSVP conversion analysis, and operational summaries. |
| | 9 | The phase includes: |
| | 10 | * complex SQL reporting queries |
| | 11 | * relational algebra representations |
| | 12 | * PostgreSQL stored procedures |
| | 13 | * analytical calculations |
| | 14 | * financial analysis |
| | 15 | * venue utilization analysis |
| | 16 | * RSVP conversion analysis |
| | 17 | * performance and scalability considerations |
| 13 | | This phase is divided into the following analytical scenarios: |
| | 21 | == Technical Environment == |
| | 22 | |
| | 23 | || Component || Technology || |
| | 24 | || Database Engine || PostgreSQL 15 || |
| | 25 | || SQL Language || PostgreSQL SQL / PLpgSQL || |
| | 26 | || Database Management || pgAdmin 4 || |
| | 27 | || Application Layer || Flask REST API || |
| | 28 | || Character Encoding || UTF-8 || |
| | 29 | |
| | 30 | == Objectives == |
| | 31 | |
| | 32 | * perform advanced analytical reporting using SQL |
| | 33 | * demonstrate multi-table relational queries |
| | 34 | * implement reusable stored procedures |
| | 35 | * calculate financial and attendance metrics |
| | 36 | * represent SQL queries using relational algebra |
| | 37 | * analyze operational efficiency and guest engagement |
| | 38 | * evaluate query performance and scalability |
| | 39 | |
| | 40 | == Development History == |
| | 41 | |
| | 42 | * v0.1 – Initial analytical SQL queries |
| | 43 | * v0.2 – Added relational algebra expressions |
| | 44 | * v0.3 – Added PostgreSQL stored procedures |
| | 45 | * v0.4 – Added execution examples and validation |
| | 46 | * v0.5 – Added performance analysis and optimization discussion |
| | 47 | * v0.6 – Final wiki documentation cleanup |
| | 48 | |
| | 49 | == Scenario Summary == |
| 16 | | || [[P6BudgetAnalysis|Scenario 1: Budget vs Actual Expenditure Analysis]] || Financial analysis of wedding budgets and actual vendor costs || |
| 17 | | || [[P6VenueCapacity|Scenario 2: Venue Capacity Utilization Analysis]] || Analysis of venue occupancy and attendance metrics || |
| 18 | | || [[P6RSVPConversion|Scenario 3: Event RSVP Conversion Rate Analysis]] || RSVP response and attendance conversion analysis || |
| 19 | | || [[P6SynthesisPerformance|Synthesis and Performance Considerations]] || Integrated analytical query and optimization strategies || |
| | 52 | || Budget vs Actual Expenditure || Financial comparison between planned and actual wedding costs || |
| | 53 | || Venue Capacity Utilization || Analysis of venue occupancy and attendance efficiency || |
| | 54 | || RSVP Conversion Analysis || Analysis of invitation, RSVP, and attendance conversion rates || |
| 23 | | * Advanced SQL queries |
| 24 | | * Aggregate functions |
| 25 | | * Multi-table joins |
| 26 | | * Relational algebra expressions |
| 27 | | * PostgreSQL stored procedures |
| 28 | | * Temporary tables |
| 29 | | * Analytical reporting |
| 30 | | * Performance optimization strategies |
| | 58 | === [[P6BudgetAnalysis]] === |
| | 59 | Financial analysis using advanced SQL aggregation and stored procedures. |
| | 60 | |
| | 61 | === [[P6VenueCapacity]] === |
| | 62 | Venue utilization and attendance analysis using analytical queries. |
| | 63 | |
| | 64 | === [[P6RSVPConversion]] === |
| | 65 | RSVP response and attendance conversion analysis. |
| | 66 | |
| | 67 | === [[P6SynthesisPerformance]] === |
| | 68 | Integrated reporting, performance optimization, scalability discussion, and conclusions. |