Faculty Deliverable System Use Case Diagram
Are you struggling with managing your faculty deliverables? If yes, then you’re not alone. Faculty deliverable management can be a daunting task, but with the help of the online Faculty Deliverable System in PHP and MySQL, it can be much easier. A use case diagram is an essential tool that helps developers and researchers visualize the system’s functions and features. In this blog post, we will discuss the benefits of using the online Faculty Deliverable System and how the use case diagram plays a vital role in its development. Whether you’re a faculty member, administrator, or researcher, this system can make your life easier by streamlining the faculty deliverable management process. So, let’s dive in and explore the world of Faculty Deliverable System and use case diagrams.
About the Project
The capstone project, “Faculty Deliverables Monitoring System with SMS Notification” is a web-based project that will enable faculty to upload their deliverables such as grades, syllabuses, and learning materials. Faculty members and department heads will be able to interact more easily with one another, as well as keep track of the requirements and files submitted by the faculty members. The said project has also a notification feature via SMS that will remind the faculty about the deadline of requirements.
The online Faculty Deliverable System in PHP and MySQL is a powerful tool that can benefit educational institutions in a number of ways. One of the main benefits of this system is that it streamlines the faculty deliverable process, making it easier for faculty members to submit and track their deliverables. This reduces the workload of administrative staff and allows them to focus on other important tasks.
Another benefit of this system is that it provides a centralized location for faculty members to access important information, such as course schedules, student information, and administrative policies. This makes it easier for faculty members to stay informed and up-to-date, which can ultimately improve the quality of education provided to students.
Furthermore, this system can improve communication between faculty members and administrative staff, as it provides a platform for them to exchange information and collaborate on various tasks. This can result in more efficient and effective decision-making processes, leading to better outcomes for the institution as a whole.
What is Use Case Diagram?
A use case diagram is a graphical representation of the interactions between the system and the actors (users, external systems, etc.) in a particular process or scenario. It is an important tool in software development as it helps to define the system’s functionality from the user’s perspective, and can be used as a basis for further analysis and design.
In the case of the online Faculty Deliverable System in PHP and MySQL, the use case diagram can help to identify the different actors involved in the system, such as faculty members, administrators, and students. It can also help to define the various tasks and activities that they perform within the system, such as creating and submitting assignments, grading papers, and generating reports.
The use case diagram is an essential tool in the research and software development of the online Faculty Deliverable System in PHP and MySQL as it helps to ensure that the system is designed to meet the needs and requirements of all stakeholders involved. It can also be used to validate the system’s functionality and to identify any potential issues or areas for improvement.
Use Case Diagram
The image shown above is the use case diagram of the system Faculty Deliverable System. The system has two user sides, the Admin/Secretary and the Faculty. The admin/secretary can access the entire core modules of the system while the Faculty can access the Dashboard, Approved Files, Messages, Notification, Downloadable File and Submitted File Modules of the system.
Use Cases
The following are the discussions that describe how a user uses a system to accomplish a particular goal.
Use Case: Dashboard
Actor(s): Admin/Secretary and Faculty
Description:
This feature is used to manage the information displayed in the dashboard of the Faculty Deliverable System.
Successful Completion:
- The Faculty can view the information displayed in the dashboard using this feature.
- The admin/secretary can search, add, update and remove information to be displayed in the dashboard.
Alternative: The faculty can only view the dashboard; the admin/secretary can access and manage all dashboard information.
Precondition: The admin/secretary and the faculty will login first to access the dashboard.
Post Condition: updated dashboard information.
Use Case: Faculty Info
Actor(s): Admin/Secretary
Description:
This feature is used to manage the information of the faculty members of the system.
Successful Completion:
- Admin/Secretary can search, add, update and remove a faculty’s information using this feature.
Alternative: Admin/secretary can register new faculty; admin can update information of old faculty members.
Precondition: The admin/secretary will need to login first to access the Faculty Info Module.
Post Condition: registered faculty and updated faculty information
Use Case: File category
Actor(s): Admin/Secretary
Description:
This feature is used to manage the information of the file categories found in the system.
Successful Completion:
- Admin/secretary can search, add, update and remove a file category information using this feature.
Alternative: Admin/secretary can add or update file category using the feature.
Precondition: The admin/secretary will need to login first to access the File Category Module.
Post Condition: updated file category information
Use Case: Approved Files
Actor(s): Admin/ Secretary and Faculty
Description:
This feature is used to view and manage the Approved Files in the system.
Successful Completion:
- The faculty can only view the approved files using this feature.
- Admin can view, review, reject and approve files.
Alternative: The faculty can only view the approved files; the admin/secretary can access and manage all approved files.
Precondition: The admin/secretary and the faculty will login first to access the Approved Files Module.
Post Condition: updated Approved Files
Use Case: Messages
Actor(s): Admin/ Secretary and Faculty
Description:
This feature is used to view and manage the Messages in the system.
Successful Completion:
- The faculty can only create and view messages in the system using this feature.
- Admin/secretary can search, add, update and remove a message information using this feature.
Alternative: The faculty can only create and view messages; the admin/secretary can access and manage all messages.
Precondition: The admin/secretary and the faculty will login first to access the Messages Module.
Post Condition: updated Messages
Use Case: Notifications
Actor(s): Admin/ Secretary and Faculty
Description:
This feature is used to view and manage the Notifications in the system.
Successful Completion:
- The faculty can only view notifications.
- Admin/secretary can search, add, update and remove a notification using this feature.
Alternative: The faculty can only view notification; the admin/secretary can access and manage all notifications.
Precondition: The admin/secretary and the faculty will login first to access the Notification Module.
Post Condition: updated Notifications
Use Case: Downloadable Files
Actor(s): Admin/ Secretary and Faculty
Description:
This feature is used to view and manage the Downloadable Files in the system.
Successful Completion:
- The faculty can only download files.
- Admin/secretary can admin can upload and manage the downloadable files using this feature.
Alternative: The faculty can only download files; the admin/secretary can access and manage all downloadable files.
Precondition: The admin/secretary and the faculty will login first to access the Downloadable File Module.
Post Condition: updated downloadable file information
Use Case: Submitted Files
Actor(s): Admin/ Secretary and Faculty
Description:
This feature is used to view and manage the Submitted Files in the system.
Successful Completion:
- The faculty can only submit files.
- Admin/secretary admin can access and manage the submitted files using this feature.
Alternative: The faculty can only submit files; the admin/secretary can access and manage all submitted files.
Precondition: The admin/secretary and the faculty will login first to access the Submitted File Module.
Post Condition: updated submitted file information
Use Case: Reports
Actor(s): Admin
Description:
This feature is used to view and print the reports in the system.
Successful Completion:
- Admin can view, print and export the report of the system.
Alternative: None
Precondition:
- Admin will need to login to access the reports.
Post Condition: hard and soft copy of the report of the system.
Summary
The blog post discusses the use case diagram for the online Faculty Deliverable System developed in PHP and MySQL. It explains the purpose of the use case diagram in the software development process and how it helps in identifying the system requirements and functionalities. The post also explains the various actors, use cases, and relationships depicted in the use case diagram, including features such as faculty login, deliverable upload, evaluation, and feedback. Additionally, it highlights the importance of the Faculty Deliverable System in streamlining the process of delivering and evaluating faculty assignments, leading to increased efficiency and productivity. Overall, the blog post provides a comprehensive overview of the use case diagram for the Faculty Deliverable System, highlighting its benefits and significance in the development of the software.
Readers are also interested in:
Faculty Deliverable System Conceptual Framework
Faculty Deliverables System ER Diagram
You may visit our Facebook page for more information, inquiries, and comments. Please subscribe also to our YouTube Channel to receive free capstone projects resources and computer programming tutorials.
Hire our team to do the project.
