Mudit Jain (231070021)

Prasanna Kasar(231070024)

SE LAB 2

Use Case Template: User Management

Use Case Identification

●​ Use Case ID: 1.0
●​ Use Case Name: User Registration and Profile Management

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:

Use Case Definition

●​ Actor:
1.​ New User
2.​ Existing User
3.​ System Administrator
●​ Description: Enable users to create accounts, authenticate, and manage their personal
profile information securely across the application.
●​ Preconditions:
1.​ User has access to a valid email address or mobile number
2.​ User has internet connectivity
3.​ Device meets minimum system requirements
●​ Postconditions:
1.​ User account is created and verified
2.​ User profile is completely set up
3.​ User can access all application features based on their role
●​ Priority: High
●​ Frequency of Use: Multiple times during initial setup and periodic updates

Normal Course of Events

1.​ User Signup Process 1.1 User selects signup method (email or mobile number) 1.2 System
validates contact information 1.3 System sends verification code 1.4 User enters verification
code 1.5 System creates user account
 2.​ User Login Process 2.1 User enters email/mobile and password 2.2 System validates
credentials 2.3 System authenticates user 2.4 User is redirected to dashboard
3.​ Profile Management 3.1 User navigates to profile section 3.2 User can update personal
details 3.3 User can upload/change profile picture 3.4 System validates and saves profile
information

Alternative Courses
●​ 1.0.AC.1: Social Media Signup
○​ User can signup using social media accounts (Google, Facebook)
○​ System creates account using social media profile information
●​ 1.0.AC.2: Forgot Password
○​ User requests password reset
○​ System sends password reset link
○​ User creates new password

Exceptions
●​ 1.0.EX.1: Invalid Email/Mobile Number
○​ System shows error message
○​ Prompts user to re-enter correct information
●​ 1.0.EX.2: Existing User Registration
○​ System prevents duplicate registrations
○​ Suggests login instead

Includes
●​ Identity Verification Module
●​ Profile Validation Module

Special Requirements
1.​ Password must be minimum 8 characters
2.​ Support for multiple languages in signup/profile
3.​ GDPR and data privacy compliance
4.​ Profile picture size and format restrictions

Assumptions
1.​ Users have access to personal email/mobile
2.​ Users will provide accurate information
3.​ Internet connectivity is stable

Notes and Issues

●​ TBD: Two-factor authentication implementation
●​ Open Issue: Handling international phone number formats
 ●​ Pending: Detailed data privacy consent mechanism

Use Case ID 1
Use Case Name User Registration and Profile Management
Actor(s) New User, Existing User, System Administrator
Enable users to create accounts, authenticate, and manage their
Description personal profile information
- Valid email/mobile number
- Internet connectivity
Preconditions - Device meets requirements
- Account created and verified
- Profile completed
Postconditions - Access granted to features
Priority High
Frequency of Use Multiple times during initial setup and periodic updates

Use Case Template: Family Tree Module

Use Case Identification

●​ Use Case ID: 2.0
●​ Use Case Name: Family Tree Management and Relationship Establishment

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:

Use Case Definition

●​ Actor:
1.​ Family Admin
2.​ Family Members
3.​ System Administrator
●​ Description: Enable family admins to create and manage family trees, and allow members to
view and join existing family trees with established relationships.
●​ Preconditions:
1.​ User is authenticated
2.​ User has necessary permissions
3.​ Family tree does not violate system constraints
 ●​ Postconditions:
1.​ Family tree is created or modified
2.​ Relationships are accurately represented
3.​ Members are appropriately linked
●​ Priority: High
●​ Frequency of Use: Moderate (initial setup and periodic updates)

Normal Course of Events

1.​ Family Tree Creation 1.1 Family Admin initiates family tree creation 1.2 System provides
template/wizard 1.3 Admin adds initial family members 1.4 System validates and saves family
tree
2.​ Adding Family Members 2.1 Admin searches for potential members 2.2 System validates
member eligibility 2.3 Member receives invitation 2.4 Member accepts and establishes
relationship
3.​ Modifying Relationships 3.1 Family Admin selects member to modify 3.2 System shows
current relationship options 3.3 Admin updates relationship 3.4 System validates and saves
changes
4.​ Member View 4.1 Member navigates to family tree section 4.2 System renders family tree
visualization 4.3 Member can explore relationships

Alternative Courses
●​ 2.0.AC.1: Member-Initiated Joining
○​ Member requests to join family tree
○​ Family Admin receives and approves request
●​ 2.0.AC.2: Imported Family Tree
○​ Admin can import family tree from external sources
○​ System validates and converts data

Exceptions
●​ 2.0.EX.1: Duplicate Member Addition
○​ System prevents adding same member multiple times
○​ Provides clear error message
●​ 2.0.EX.2: Circular Relationship Detection
○​ System prevents illogical family relationships
○​ Alerts admin about potential errors

Includes
●​ User Verification Module
●​ Relationship Validation Module

Special Requirements
1.​ Graphical family tree visualization
2.​ Privacy controls for relationship visibility
 3.​ Support for complex family structures
4.​ Audit trail for relationship modifications

Assumptions
1.​ Family members are willing to participate
2.​ Relationships can be accurately represented
3.​ Users understand family tree concept

Notes and Issues

●​ TBD: Advanced genealogy research integration
●​ Open Issue: Handling deceased family members
●​ Pending: Cross-family connection mechanism

Use Case ID 2
Use Case Name Family Tree Management and Relationship Establishment
Actor(s) Family Admin, Family Members, System Administrator
Create and manage family trees, establish relationships between
Description members
- User authenticated
- Necessary permissions
Preconditions - Valid family structure
- Family tree created/modified
- Relationships established
Postconditions - Members linked
Priority High
Frequency of Use Moderate (initial setup and updates)

Use Case Template: Messaging Module

Use Case Identification

●​ Use Case ID: 3.0
●​ Use Case Name: Real-time Messaging and Communication

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:
Use Case Definition
●​ Actor:
1.​ Individual Users
2.​ Group Members
3.​ System Administrator
●​ Description: Enable users to engage in real-time private and group messaging with
multimedia support, facilitating seamless communication within the application.
●​ Preconditions:
1.​ User is authenticated
2.​ User has active internet connection
3.​ User has necessary device capabilities
●​ Postconditions:
1.​ Messages are sent and received successfully
2.​ Multimedia content is shared and stored
3.​ Chat history is maintained
●​ Priority: High
●​ Frequency of Use: Very High (Daily Active Communication)

Normal Course of Events

1.​ Private Messaging 1.1 User selects another user to chat with 1.2 System opens private chat
window 1.3 User composes and sends message 1.4 System delivers message in real-time
1.5 Recipient receives and can respond
2.​ Group Messaging 2.1 User creates or joins group chat 2.2 System validates group
membership 2.3 User sends group message 2.4 System broadcasts message to all group
members
3.​ Multimedia Sharing 3.1 User selects multimedia sharing option 3.2 User chooses file
(image/video/audio) 3.3 System validates file type and size 3.4 File is uploaded and shared in
chat 3.5 Recipients can view/download shared content
4.​ Message Management 4.1 User can view chat history 4.2 User can delete individual
messages 4.3 User can block/report inappropriate content

Alternative Courses
●​ 3.0.AC.1: Voice/Video Calling
○​ User initiates voice or video call
○​ System establishes peer-to-peer connection
●​ 3.0.AC.2: Message Translation
○​ System offers real-time message translation
○​ Users can communicate across language barriers

Exceptions
●​ 3.0.EX.1: Message Delivery Failure
○​ System attempts multiple message deliveries
○​ Notifies sender of delivery issues
●​ 3.0.EX.2: File Upload Restrictions
○​ System blocks files exceeding size limits
 ○​ Provides clear error messages about restrictions

Includes
●​ User Authentication Module
●​ File Upload Validation Module
●​ Real-time Communication Service

Special Requirements
1.​ End-to-end encryption for messages
2.​ Support for various file formats
3.​ Low-bandwidth message delivery
4.​ Cross-platform message synchronization
5.​ Accessibility features for messaging

Assumptions
1.​ Users have basic digital communication skills
2.​ Network connectivity is relatively stable
3.​ Users understand multimedia sharing etiquette

Notes and Issues

●​ TBD: Advanced message search capabilities
●​ Open Issue: Implementing message read receipts
●​ Pending: Group chat administration features

Use Case ID 3
Use Case Name Real-time Messaging and Communication
Actor(s) Individual Users, Group Members, System Administrator
Enable real-time private and group messaging with
Description multimedia support
- User authenticated
- Active internet connection
Preconditions - Device capabilities
- Messages delivered
- Multimedia content shared
Postconditions - Chat history maintained
Priority High
Frequency of
Use Very High (Daily Active Communication)

Use Case Template: Community Feed Module

Use Case Identification
●​ Use Case ID: 4.0
●​ Use Case Name: Community Content Sharing and Engagement

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:

Use Case Definition

●​ Actor:
1.​ Registered Users
2.​ Content Creators
3.​ Community Moderators
4.​ System Administrator
●​ Description: Enable users to create, share, and interact with various types of content
including text, images, and videos, while providing engagement mechanisms like comments,
likes, and sharing.
●​ Preconditions:
1.​ User is authenticated
2.​ User has content creation permissions
3.​ User has active internet connection
●​ Postconditions:
1.​ Content is published and visible to appropriate audience
2.​ User engagement metrics are recorded
3.​ Content moderation rules are applied
●​ Priority: High
●​ Frequency of Use: Very High (Multiple Times Daily)

Normal Course of Events

1.​ Content Creation 1.1 User selects content type (text/image/video) 1.2 User composes content
1.3 User adds tags and location (optional) 1.4 System validates content 1.5 Content is
published to community feed
2.​ Content Engagement 2.1 User views content in feed 2.2 User can like/react to content 2.3
User can comment on content 2.4 User can share content 2.5 System updates engagement
metrics
3.​ Localized Updates 3.1 System aggregates local/community news 3.2 Filters updates based
on user preferences 3.3 Displays relevant localized content
4.​ Content Discovery 4.1 User can explore trending content 4.2 System recommends content
based on interests 4.3 User can follow specific content creators

Alternative Courses
 ●​ 4.0.AC.1: Anonymous Posting
○​ Option for users to post with limited personal information
○​ System maintains content traceability
●​ 4.0.AC.2: Sponsored/Promoted Content
○​ Verified organizations can create sponsored posts
○​ Clear labeling of promotional content

Exceptions
●​ 4.0.EX.1: Content Violation
○​ System detects inappropriate content
○​ Automatic content removal or user notification
○​ Potential account suspension for repeated violations
●​ 4.0.EX.2: Content Sharing Restrictions
○​ System prevents sharing in certain contexts
○​ Provides clear explanation of sharing limitations

Includes
●​ Content Moderation Module
●​ User Verification Module
●​ Recommendation Engine

Special Requirements
1.​ Content filtering and age restrictions
2.​ Support for multiple media formats
3.​ Performance optimization for content loading
4.​ Accessibility for content consumption
5.​ Privacy controls for content visibility

Assumptions
1.​ Users will create meaningful content
2.​ Users understand community guidelines
3.​ Diverse user interests and backgrounds

Notes and Issues

●​ TBD: Advanced content recommendation algorithms
●​ Open Issue: Balancing content moderation and free expression
●​ Pending: Implementing content monetization features
Use Case ID 4
Use Case Name Community Content Sharing and Engagement
Registered Users, Content Creators, Community
Actor(s) Moderators
Create, share, and interact with various types of
Description content
- User authenticated
- Content creation permissions
Preconditions - Active connection
- Content published
- Engagement metrics recorded
Postconditions - Moderation applied
Priority High
Frequency of
Use Very High (Multiple Times Daily)

Use Case Template: Event Management Module

Use Case Identification

●​ Use Case ID: 5.0
●​ Use Case Name: Event Creation, Management, and Participation

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:

Use Case Definition

●​ Actor:
1.​ Family Admin
2.​ Regular Users
3.​ Event Organizers
4.​ System Administrator
●​ Description: Enable family admins to create events and allow users to discover, RSVP, and
participate in various community and family-related events.
●​ Preconditions:
1.​ User is authenticated
2.​ User has appropriate permissions
3.​ Event creation follows community guidelines
●​ Postconditions:
 1.​ Event is created and published
2.​ Users can view and interact with events
3.​ Event participation is tracked
4.​ RSVP status is managed
●​ Priority: High
●​ Frequency of Use: Moderate (Depends on community activity)

Normal Course of Events

1.​ Event Creation (Family Admin) 1.1 Admin navigates to event creation section 1.2 Admin fills
event details (title, date, time, location) 1.3 Admin sets event visibility
(public/private/family-only) 1.4 System validates event information 1.5 Event is published to
relevant users
2.​ Event Search and Discovery 2.1 User accesses event search functionality 2.2 User can filter
events by: - Date - Location - Category - Interests 2.3 System displays matching events 2.4
User can view event details
3.​ RSVP Process 3.1 User selects an event 3.2 User chooses RSVP status (Going/Maybe/Not
Going) 3.3 System updates event participation count 3.4 Event organizer receives RSVP
notifications
4.​ Event Management 4.1 Family Admin can modify event details 4.2 Admin can send event
reminders 4.3 Admin can track participant information 4.4 System maintains event history

Alternative Courses
●​ 5.0.AC.1: Virtual Event Creation
○​ Option to create online/virtual events
○​ Integration with video conferencing platforms
●​ 5.0.AC.2: Recurring Event Setup
○​ Admin can create events that repeat periodically
○​ System manages recurring event logistics

Exceptions
●​ 5.0.EX.1: Event Capacity Reached
○​ System prevents additional RSVPs
○​ Offers waitlist functionality
●​ 5.0.EX.2: Event Cancellation
○​ Admin can cancel events
○​ Automatic notifications to participants
○​ Refund process for paid events

Includes
●​ User Notification Module
●​ Payment Processing Module (for paid events)
●​ Location Services Module

Special Requirements
 1.​ Calendar integration
2.​ Multi-language support for event details
3.​ Accessibility for event information
4.​ Mobile-friendly event management
5.​ Privacy controls for event visibility

Assumptions
1.​ Users are interested in community events
2.​ Family admins will create meaningful events
3.​ Users have basic digital event management skills

Notes and Issues

●​ TBD: Advanced event recommendation system
●​ Open Issue: Handling complex event pricing models
●​ Pending: Social sharing of events

Use Case ID 5
Event Creation, Management, and
Use Case Name Participation
Family Admin, Regular Users, Event
Actor(s) Organizers
Create, discover, and participate in
Description community events
- User authenticated
- Appropriate permissions
Preconditions - Valid event guidelines
- Event published
- RSVP enabled
Postconditions - Participation tracked
Priority High
Frequency of Use Moderate
Use Case Template: Community Directory Module

Use Case Identification

●​ Use Case ID: 6.0
●​ Use Case Name: Member Search and Connection Management

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:

Use Case Definition

●​ Actor:
1.​ Registered Users
2.​ Community Members
3.​ System Administrator
●​ Description: Enable users to search and connect with community members based on various
criteria, facilitating networking and relationship building.
●​ Preconditions:
1.​ User is authenticated
2.​ User has completed profile
3.​ Privacy settings allow directory searches
●​ Postconditions:
1.​ Search results are displayed
2.​ Connection requests can be sent/managed
3.​ Mutual connections are identified
4.​ User privacy is maintained
●​ Priority: High
●​ Frequency of Use: Moderate to High

Normal Course of Events

1.​ Member Search 1.1 User accesses community directory 1.2 User selects search criteria: -
Name - Username - Family name - Interests - Background 1.3 System processes search
query 1.4 Displays matching user profiles
2.​ Mutual Connection Discovery 2.1 System identifies mutual connections 2.2 Displays
connection pathways 2.3 Suggests potential connections based on: - Shared interests -
Common friends - Family connections
3.​ Profile Exploration 3.1 User can view limited profile details 3.2 System respects privacy
settings 3.3 Option to request more connection details
4.​ Connection Management 4.1 User can send connection requests 4.2 Recipients can
accept/reject requests 4.3 System tracks connection status 4.4 Users can manage their
connections list
Alternative Courses
●​ 6.0.AC.1: Advanced Filtering
○​ Detailed search with multiple criteria
○​ Geographical location-based search
○​ Professional background filtering
●​ 6.0.AC.2: Anonymous Browse
○​ Limited profile viewing without direct contact
○​ Protects user privacy

Exceptions
●​ 6.0.EX.1: No Search Results
○​ System provides suggestion for broader search
○​ Offers recommended connections
●​ 6.0.EX.2: Privacy Restriction
○​ Blocks search for users with strict privacy settings
○​ Provides clear messaging about access limitations

Includes
●​ User Profile Module
●​ Privacy Management Module
●​ Connection Request Handling Module

Special Requirements
1.​ GDPR and data privacy compliance
2.​ Granular privacy control settings
3.​ Search performance optimization
4.​ Multilingual search support
5.​ Accessibility in search functionality

Assumptions
1.​ Users want to expand their network
2.​ Users are comfortable sharing limited profile information
3.​ Community values mutual connections

Notes and Issues

●​ TBD: Advanced connection recommendation algorithm
●​ Open Issue: Handling cross-family connections
●​ Pending: Professional networking integration
Use Case ID 6
Use Case Name Member Search and Connection Management
Actor(s) Registered Users, Community Members
Search and connect with community members based on
Description various criteria
- User authenticated
- Completed profile
Preconditions - Privacy settings configured
- Search results displayed
- Connections managed
Postconditions - Privacy maintained
Priority High
Frequency of Use Moderate to High

Use Case Template: Donation and Charity Module

Use Case Identification

●​ Use Case ID: 7.0
●​ Use Case Name: Fundraising and Donation Management

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:

Use Case Definition

●​ Actor:
1.​ Fundraising Organizers
2.​ Donors
3.​ Community Administrators
4.​ System Administrator
●​ Description: Enable users to create, discover, and contribute to fundraising campaigns while
providing transparent donation tracking and management.
●​ Preconditions:
1.​ User is authenticated
2.​ User has valid payment method
3.​ Fundraising campaign meets platform guidelines
 ●​ Postconditions:
1.​ Fundraising campaign is created/published
2.​ Donations are processed securely
3.​ Donation history is maintained
4.​ Transparency in fund utilization
●​ Priority: High
●​ Frequency of Use: Moderate

Normal Course of Events

1.​ Fundraising Campaign Creation 1.1 Organizer initiates campaign creation 1.2 Provides
campaign details: - Campaign title - Fundraising goal - Cause description - Timeline - Fund
utilization plan 1.3 System validates campaign information 1.4 Campaign is published for
community review
2.​ Donation Process 2.1 User discovers fundraising campaign 2.2 User selects donation amount
2.3 Chooses payment method 2.4 System processes payment securely 2.5 Donation is
recorded and acknowledged
3.​ Campaign Tracking 3.1 Organizers can track donation progress 3.2 System provides
real-time fundraising statistics 3.3 Donors can view campaign updates 3.4 Transparency
reports are generated
4.​ Donation History 4.1 Users can view their donation history 4.2 System provides detailed
donation receipts 4.3 Option to download/print donation records

Alternative Courses
●​ 7.0.AC.1: Recurring Donations
○​ Option to set up automatic periodic donations
○​ Flexible recurring donation schedules
●​ 7.0.AC.2: Corporate Matching
○​ Integration with corporate donation matching programs
○​ Automatic tracking of matched contributions

Exceptions
●​ 7.0.EX.1: Payment Processing Failure
○​ System provides clear error messages
○​ Offers alternative payment methods
○​ Ensures no duplicate charges
●​ 7.0.EX.2: Campaign Goal Reached
○​ Automatic campaign status update
○​ Options for excess fund allocation

Includes
●​ Payment Processing Module
●​ User Verification Module
●​ Reporting and Analytics Module
Special Requirements
1.​ PCI DSS compliance for payment processing
2.​ Secure encryption of financial transactions
3.​ Multiple payment method support
4.​ Detailed reporting capabilities
5.​ Accessibility in donation interface

Assumptions
1.​ Users are motivated to support causes
2.​ Community values transparent fundraising
3.​ Users have basic digital payment skills

Notes and Issues

●​ TBD: Blockchain-based donation tracking
●​ Open Issue: International donation support
●​ Pending: Tax deduction receipt generation

Use Case ID 7
Use Case Name Fundraising and Donation Management
Fundraising Organizers, Donors, Community
Actor(s) Administrators
Create, discover, and contribute to fundraising
Description campaigns
- User authenticated
- Valid payment method
Preconditions - Campaign guidelines met
- Campaign published
- Donations processed
Postconditions - History maintained
Priority High
Frequency of Use Moderate
Use Case Template: Notification Module

Use Case Identification

●​ Use Case ID: 8.0
●​ Use Case Name: User Notification and Alert Management

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:

Use Case Definition

●​ Actor:
1.​ Registered Users
2.​ System Administrators
3.​ Community Administrators
4.​ Notification Service
●​ Description: Enable comprehensive notification management with user-controlled
permissions, supporting multiple notification channels and personalized alert preferences.
●​ Preconditions:
1.​ User is authenticated
2.​ User has configured device for notifications
3.​ Notification services are operational
●​ Postconditions:
1.​ Notifications are delivered through preferred channels
2.​ User notification preferences are respected
3.​ Critical information is communicated
4.​ Notification history is maintained
●​ Priority: High
●​ Frequency of Use: Very High (Continuous Background Process)

Normal Course of Events

1.​ Notification Preferences Setup 1.1 User accesses notification settings 1.2 User selects
preferred notification channels: - Push Notifications - Email - SMS - In-App Notifications 1.3
User configures notification types 1.4 System saves user preferences
2.​ Notification Delivery 2.1 System generates notification event 2.2 Checks user's notification
preferences 2.3 Delivers notification through selected channels 2.4 Logs notification delivery
status
3.​ Notification Types 3.1 User Engagement Notifications - Messages - Connection Requests -
Event Invitations 3.2 Community Updates - New Posts - Fundraising Campaigns - Community
News 3.3 Personal Alerts - Profile Changes - Account Security - Donation Confirmations
 4.​ Notification Management 4.1 User can view notification history 4.2 Option to mark
notifications as read/unread 4.3 Ability to clear notification history 4.4 System maintains
recent notification log

Alternative Courses
●​ 8.0.AC.1: Intelligent Notification Prioritization
○​ System learns user interaction patterns
○​ Prioritizes most relevant notifications
○​ Reduces notification fatigue
●​ 8.0.AC.2: Notification Scheduling
○​ Users can set quiet hours
○​ Batch notification delivery
○​ Time-zone aware notifications

Exceptions
●​ 8.0.EX.1: Notification Delivery Failure
○​ System attempts multiple delivery methods
○​ Provides fallback notification mechanisms
○​ Logs delivery attempts
●​ 8.0.EX.2: Excessive Notifications
○​ System implements notification throttling
○​ Prevents notification spam
○​ Offers user-level control

Includes
●​ User Preference Management Module
●​ Communication Channel Integration
●​ Notification Logging Service

Special Requirements
1.​ Cross-platform notification support
2.​ Low battery consumption
3.​ Granular notification permissions
4.​ Accessibility in notification design
5.​ Multi-language notification support

Assumptions
1.​ Users want to stay informed
2.​ Notification preferences vary by individual
3.​ Users have multiple communication devices

Notes and Issues

 ●​ TBD: Machine learning-based notification optimization
●​ Open Issue: Balancing user engagement and notification frequency
●​ Pending: Advanced notification customization options

Use Case ID 8
Use Case Name User Notification and Alert Management
Registered Users, System Administrators, Notification
Actor(s) Service
Description Manage user notifications across multiple channels
- User authenticated
- Device configured
Preconditions - Services operational
- Notifications delivered
- Preferences respected
Postconditions - History maintained
Priority High
Frequency of Use Very High (Continuous)

Use Case Template: Roles and Permissions Module

Use Case Identification

●​ Use Case ID: 9.0
●​ Use Case Name: User Role and Access Management

Use Case History

●​ Created By: Mudit Jain, Prasanna Kasar
●​ Date Created: 28/01/25
●​ Last Updated By:
●​ Date Last Updated:

Use Case Definition

●​ Actor:
1.​ Community Administrator
2.​ Family Administrator
3.​ Regular Users
4.​ System Administrator
●​ Description: Implement a comprehensive role-based access control system to manage user
permissions across different levels of the community platform.
●​ Preconditions:
1.​ User is authenticated
 2.​ User has been assigned a specific role
3.​ Role-based access control system is operational
●​ Postconditions:
1.​ User can access only permitted features
2.​ Hierarchical access control is maintained
3.​ Permissions are dynamically manageable
4.​ Audit trail of permission changes
●​ Priority: Critical
●​ Frequency of Use: Moderate (During system administration)

Normal Course of Events

1.​ Role Hierarchy Management 1.1 System defines role hierarchy: - Community Administrator
(Master Control) - Family Administrator - Regular User 1.2 Each role has predefined
permission sets 1.3 Permissions can be granularly configured
2.​ Community Administrator Capabilities 2.1 Manage entire platform 2.2 Control: - Family
management - Member account management - Content moderation - Event oversight -
Fundraising campaigns 2.3 Ability to create/modify/delete any platform content
3.​ Family Administrator Capabilities 3.1 Manage specific family ecosystem 3.2 Control: - Family
tree modifications - Member addition/removal - Family event creation - Internal
communication 3.3 Limited to their specific family group
4.​ Regular User Capabilities 4.1 Standard platform interactions 4.2 Permissions include: -
Messaging - Event participation - Content creation - Donation - Profile management
5.​ Permission Audit and Tracking 5.1 System logs all permission changes 5.2 Generates
comprehensive audit reports 5.3 Allows rollback of permission modifications

Alternative Courses
●​ 9.0.AC.1: Dynamic Role Assignment
○​ Ability to create custom roles
○​ Flexibility in permission configuration
○​ Temporary role elevation
●​ 9.0.AC.2: Delegation of Permissions
○​ Family admins can delegate specific permissions
○​ Granular control over temporary access

Exceptions
●​ 9.0.EX.1: Unauthorized Access Attempt
○​ Immediate system alert
○​ Access immediately blocked
○​ Comprehensive logging of attempt
●​ 9.0.EX.2: Role Conflict
○​ System prevents conflicting role assignments
○​ Provides clear resolution path

Includes
●​ User Authentication Module
 ●​ Access Control Management
●​ Audit Logging Service

Special Requirements
1.​ Zero-trust security model
2.​ Compliance with data protection regulations
3.​ Real-time permission synchronization
4.​ Scalable permission architecture
5.​ Cryptographically secure permission management

Assumptions
1.​ Clear organizational hierarchy
2.​ Responsible use of administrative privileges
3.​ Continuous evolution of role definitions

Notes and Issues

●​ TBD: Machine learning-enhanced permission recommendations
●​ Open Issue: Handling cross-family administrative scenarios
●​ Pending: Implementation of role-based pricing model

Use Case ID 9
Use Case Name User Role and Access Management
Community Administrator, Family Administrator,
Actor(s) Regular Users
Description Manage role-based access control across platform
- User authenticated
- Role assigned
Preconditions - Access control operational
- Permissions enforced
- Access controlled
Postconditions - Audit trail maintained
Priority Critical
Frequency of Use Moderate