This is aSystem analysis and project management class assignment. Masters level. This project has 3 phases. Phase 1 and 2 has been completed. I only need phase 3. I will upload the project sheet, 1...

Interface Design

Database Design
1. Users Table
Attributes:
· user_id (Primary Key)
· username (Unique)
· email (Unique)
· password
· preferences (JSON or text format to store user-specific preferences)
· availability (JSON or text format to store availability details)
· created_at (Timestamp)
· updated_at (Timestamp)
Constraints:
· username and email are unique.
· email must be in valid email format.
· password is encrypted for security.
2. Activities Table
Attributes:
· activity_id (Primary Key)
· activity_name
· activity_type (e.g., outdoor, indoor, recreational, etc.)
· description
· duration (time in hours or minutes)
· location (optional)
· tags (JSON for storing activity categories or preferences)
· created_at (Timestamp)
· updated_at (Timestamp)
Constraints:
· activity_name must be unique.
· duration should be a positive integer.
· created_at and updated_at are automatically generated.
3. User_Activities Table
Attributes:
· user_activity_id (Primary Key)
· user_id (Foreign Key referencing Users)
· activity_id (Foreign Key referencing Activities)
· status (e.g., planned, completed, canceled)
· scheduled_date (Timestamp)
· feedback (optional text for user feedback on activities)
· created_at (Timestamp)
· updated_at (Timestamp)
Foreign Keys:
· user_id references Users(user_id)
· activity_id references Activities(activity_id)
Constraints:
· The combination of user_id and activity_id must be unique to prevent duplicate entries for the same user-activity pair.
4. Emails Table
Attributes:
· email_id (Primary Key)
· user_id (Foreign Key referencing Users)
· subject
· body
· received_date (Timestamp)
· status (e.g., read, unread)
· priority (High, Medium, Low)
· created_at (Timestamp)
· updated_at (Timestamp)
Foreign Keys:
· user_id references Users(user_id)
Constraints:
· subject and body are required fields.
· received_date must be a valid timestamp.
5. Reports Table
Attributes:
· report_id (Primary Key)
· user_id (Foreign Key referencing Users)
· title
· content (Text or JSON for storing structured report content)
· created_at (Timestamp)
· updated_at (Timestamp)
Foreign Keys:
· user_id references Users(user_id)
Constraints:
· title should be unique for each user.
· content is a required field.
6. Feedback Table
Attributes:
· feedback_id (Primary Key)
· user_activity_id (Foreign Key referencing User_Activities)
· rating (Numeric scale, e.g., 1-5)
· comments (optional text for additional feedback)
· created_at (Timestamp)
Foreign Keys:
· user_activity_id references User_Activities(user_activity_id)
Constraints:
· rating must be an integer between 1 and 5.
· comments are optional but can be stored as text.
7. Task Prioritization Table
Attributes:
· task_id (Primary Key)
· user_id (Foreign Key referencing Users)
· task_name
· priority (High, Medium, Low)
· due_date (Timestamp)
· status (e.g., pending, completed)
· created_at (Timestamp)
· updated_at (Timestamp)
Foreign Keys:
· user_id references Users(user_id)
Constraints:
· task_name must be unique for each user.
· due_date must be a valid timestamp.
8. Activity Recommendations Table
Attributes:
· recommendation_id (Primary Key)
· user_id (Foreign Key referencing Users)
· activity_id (Foreign Key referencing Activities)
· score (numeric score for the recommendation)
· reason (optional text explaining why this activity is recommended)
· created_at (Timestamp)
Foreign Keys:
· user_id references Users(user_id)
· activity_id references Activities(activity_id)
Constraints:
· score must be between 1 and 10.
· reason is optional but can be provided as text.
Class Diagram
Software Design
Method Name: Task Prioritization with Feedback()
Class Name: TaskManage
ID: Task Prioritization #1
Clients (Consumers): Project Manage
Associated Use Case(s): Task Scheduling, Task Management
Description of Responsibilities: Calculates urgency of tasks and prioritizes them based on user-defined weights for ensuring critical tasks that are addressed.
Arguments Received: List of Tasks, Cu
ent Time, Priority Weights
Type of Value Returned: Sorted List of Tasks
Pre-Condition(s): User provides a list of tasks, cu
ent time, and priority weights.
Post-Condition(s): A list of tasks...