= Use-case Model = == List of Actors / Roles == * '''Board Member''' - A member of the BEST Skopje Board who performs administrative work in the application. * [wiki:UseCase0001 UC0001 - View member profile and membership history] - A Board Member views profile, membership, function, mentor, and application data for a selected member. * [wiki:UseCase0002 UC0002 - Create activity session] - A Board Member creates an activity session and records its responsible member. * [wiki:UseCase0004 UC0004 - Check Full Member Meeting attendance] - A Board Member records attendance for a Full Member Meeting. * [wiki:UseCase0005 UC0005 - Create event edition and event functions] - A Board Member creates an event edition with locations and event function slots. * '''Main Organiser''' - A member responsible for managing one specific event edition. * [wiki:UseCase0007 UC0007 - Review applications] - A Main Organiser reviews applications for their event edition and updates their status. * '''Member''' - A BEST Skopje member who participates in activities and volunteers for event sessions. * [wiki:UseCase0003 UC0003 - RSVP or announce absence for activity session] - A Member updates RSVP data for an activity session and announces absence only for a session where their attendance is expected. * [wiki:UseCase0008 UC0008 - Volunteer for event session] - A Member volunteers for a selected event session. * '''Student''' - A UKIM student who can submit an application for selected events or participation processes. * [wiki:UseCase0006 UC0006 - Submit application] - A Student submits an application with personal data and a motivational letter. == Use-case Model Diagram == {{{ Board Member -> UC0001, UC0002, UC0004, UC0005 Main Organiser -> UC0007 Member -> UC0003, UC0008 Student -> UC0006 }}} == Realization Details on Selection of the Most Important Use Cases in the Database == The selected use cases are [wiki:UseCase0001 UC0001], [wiki:UseCase0002 UC0002], [wiki:UseCase0003 UC0003], [wiki:UseCase0004 UC0004], [wiki:UseCase0005 UC0005], [wiki:UseCase0006 UC0006], [wiki:UseCase0007 UC0007], and [wiki:UseCase0008 UC0008]. These use cases were selected because they cover the main database operations of the application: reading member data, creating activity sessions, recording participation and absence data, checking attendance, creating event editions, submitting applications, reviewing applications, and volunteering for event sessions. == AI Use == AI usage for this phase is documented here: [wiki:UseCaseModelAIUsage UseCaseModelAIUsage].