Changes between Version 1 and Version 2 of P4


Ignore:
Timestamp:
01/03/26 21:58:45 (2 weeks ago)
Author:
193284
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • P4

    v1 v2  
    1 = Phase P4
     1Phase P4 – First Application Prototype
    22
    3 == Content
    4 To be defined.
     3Description
     4This phase presents a working prototype application that demonstrates
     5how selected application scenarios from Phase P3 can be implemented
     6using a real database and backend logic.
     7
     8Technology
     9- Programming language: Python
     10- Framework: Flask
     11- Database: SQLite
     12- Execution environment: Local development (Windows)
     13
     14Implemented Scenarios
     15The prototype implements a representative subset of the application
     16scenarios defined in Phase P3:
     17
     181. Listing weddings for a user
     192. Viewing events for a selected wedding
     203. Viewing guests for a wedding
     214. Attendance overview for an event
     225. RSVP overview for an event
     236. Venue availability check with conflict detection
     24
     25Venue Availability Logic
     26The application implements business logic to detect overlapping
     27venue bookings for a selected date and time interval.
     28
     29If a conflict exists, the system returns:
     30- available: false
     31- list of conflicting bookings
     32
     33If no conflict exists, the system returns:
     34- available: true
     35
     36Screenshots
     37Below are screenshots demonstrating:
     38- Wedding listing
     39- Attendance overview
     40- RSVP overview
     41- Venue availability with conflict
     42- Venue availability without conflict
     43
     44This prototype demonstrates the feasibility of implementing
     45the database usage scenarios and validates the database design.