How fullstack-verse/yms works
Main Actors
• Admin: This actor interacts with several management features like adding categories, packages, posts, handling booking history, reports, and user profiles.
• Employer/User: There are separate login credentials mentioned (e.g., for an “employer” or registered user), representing the typical user who might book classes or events.
• Guest: Unauthenticated site visitors who can browse items such as class details or contact information.
Major Use Cases
• User Authentication:
• Login
• Registration (new user signup)
• Logout
• Change Password
• Booking Management:
• View Booking Details
• New Bookings (for new registration/bookings)
• Partial Payment Bookings
• Full Payment Bookings
• Booking History (for users and admins)
• Content Management (Admin Use Cases):
• /Edit Post (blog or class/post updates)
• Category/Package (to update offerings)
• Manage Posts
• Reports & Administration:
• Report on Booking
• Report on Registration
• Profile Management (for users/admin)
• Navigation & General Interaction:
• Browse classes, posts, and package details
• Access pages like “about”, “contact”, etc.
System Boundary
• Encapsulate all the use cases within a boundary (often called “Gym/Yoga Management System”).
• Which use cases are internal to the system.
Relationships
• Admin actor to the management and report use cases (like adding content, managing bookings, profile changes).
• Link the Employer/User actor to authentication, booking management, and general navigation use cases.
• That Guest users can access certain non-restricted pages and then be prompted to register or login.
• Use include or extend relationships where needed. For instance, “Login” could be an included action for “Change Password” or “Profile Management” if a user isn’t authenticated. Similarly, booking details might include verification of user accounts.