PROG 2 - Claims Management System

Project Overview

This project is an ASP.NET Core MVC application designed to manage claims submitted by lecturers. It provides distinct roles for both lecturers and administrators (admins), incorporating features to streamline the claim submission and approval process. This application aims to enhance both user experience and administrative efficiency by focusing on security, responsive design, and streamlined workflows.

Implementation of POE Recommendations

1. User Authentication and Authorization:

• The application employs ASP.NET Core Identity for secure user authentication, ensuring robust login and role management.
• User roles are defined as "admin" and "lecturer," allowing for role-specific functionalities and access control.

2. Responsive Layout:

• A responsive design ensures compatibility across devices, with a dynamic navigation bar that adapts based on the user's authentication status.

3. Claims Management:

• The Claims model uses validation attributes to ensure all required data (uploader name, hours worked, hourly rate, status, etc.) is provided during submission.
• Claims are stored in a non-static, read-only manner, preserving data integrity while enabling efficient data persistence.

Features

1. User Roles:

Lecturers:

• Can submit claims through a user-friendly form.
• View their submitted claims and check the status of each submission.

Admins:

• Access a dedicated admin home page displaying all submitted claims.
• Approve or reject claims, managing and reviewing them efficiently.
• Use a streamlined navigation bar that appears only when logged in as an admin.

2. Dynamic Navigation Bar:

• The navigation bar adjusts based on the user's authentication status:
  • Displays a logo and relevant navigation links for lecturers.
  • Shows a simplified navigation bar with links to home and claims for admins.
  • Replaces the "Log in" button with a "Log out" button when a user is logged in.

3. Logging In and Out:

• A straightforward login page allows users to authenticate with their credentials.
• After logging in, users are redirected to their respective home pages (lecturer or admin).
• Users can securely log out, which terminates their session and redirects them to the home page.

4. Form Validation:

• The claim submission form includes validation, ensuring that all required fields are completed before submission, improving data integrity and user experience.

User Functionalities

Lecturer Functionalities:

• Submit claims with all necessary details (hours worked, hourly rate, etc.).
• Review the status of their submitted claims.
• Access a contact form for inquiries or assistance.

Admin Functionalities:

• View all claims submitted by lecturers on an admin dashboard.
• Approve or reject claims based on the established criteria.
• Manage the overall claims process, ensuring transparency and efficiency.

Conclusion

This project successfully implements the POE recommendations by focusing on secure user management, responsive design, and efficient claims processing. By clearly distinguishing between lecturer and admin functionalities, the application provides an intuitive workflow, enhancing user engagement and administrative oversight.