Changes between Version 2 and Version 3 of About


Ignore:
Timestamp:
01/14/26 09:22:19 (3 days ago)
Author:
221511
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • About

    v2 v3  
     1The Faculty Resource Reservation and Usage Analytics System is a database-centered project aimed at organizing and managing shared resources within a faculty or academic institution. The database will store data related to physical and digital resources, users, reservations, availability intervals, and historical usage information.
    12
    2 {{{
    3 <p>The Faculty Resource Reservation and Usage Analytics System is a database-centered project aimed at organizing and managing shared resources within a faculty or academic institution. The database will store data related to physical and digital resources, users, reservations, availability intervals, and historical usage information.</p>
     3The project focuses on designing a well-structured relational database that ensures data integrity, supports efficient querying, and enables analytical reporting. If the project were further developed, it would include a simple application layer that demonstrates how users interact with the database to reserve resources, check availability, analyze usage trends and also propose new resources that were not shared before to be shared now.
    44
    5 <p>The project focuses on designing a well-structured relational database that ensures data integrity, supports efficient querying, and enables analytical reporting. If the project were further developed, it would include a simple application layer that demonstrates how users interact with the database to reserve resources, check availability, analyze usage trends and also propose new resources that were not shared before to be shared now.</p>
     5The system is intended to improve transparency, reduce scheduling conflicts, and support data-driven planning decisions. The main emphasis remains on database modeling, constraints, normalization, and advanced SQL queries, in alignment with the learning objectives of the Databases course.
    66
    7 <p>The system is intended to improve transparency, reduce scheduling conflicts, and support data-driven planning decisions. The main emphasis remains on database modeling, constraints, normalization, and advanced SQL queries, in alignment with the learning objectives of the Databases course.<br />
    8 &nbsp;</p>
    97
    10 <ul>
    11         <li>
    12         <p>The database and application are intended to be owned and maintained by the faculty. The primary purpose is to provide a centralized system for managing shared resources that are used for teaching, research, and administrative activities for more efficient time planning and organization.</p>
    13         </li>
    14         <li>
    15         <p>The problems solved will be the next but not limited to:</p>
     8The database and application are intended to be owned and maintained by the faculty. The primary purpose is to provide a centralized system for managing shared resources that are used for teaching, research, and administrative activities for more efficient time planning and organization.
    169
    17         <ul>
    18                 <li>
    19                 <p>Lack of&nbsp;information about resource availability</p>
    20                 </li>
    21                 <li>
    22                 <p>Conflicting or overlapping reservations</p>
    23                 </li>
    24                 <li>
    25                 <p>Limited insight into historical resource usage</p>
    26                 </li>
    27                 <li>
    28                 <p>Difficulty in planning resource allocation based on actual demand</p>
    29                 </li>
    30                 <li>
    31                 <p>Information about availability of resources students didn&#39;t even knew they could use.</p>
    32                 </li>
    33         </ul>
    34         </li>
    35         <li>
    36         <p>There will be three types of users in this system:</p>
     10The problems solved will be the next but not limited to:
    3711
    38         <ul>
    39                 <li>
    40                 <p><strong>Teaching staff</strong>&nbsp;-&nbsp;reserve resources for lectures, labs, and research</p>
    41                 </li>
    42                 <li>
    43                 <p><strong>Students</strong>&nbsp;- view availability and access permitted resources</p>
    44                 </li>
    45                 <li>
    46                 <p><strong>Faculty administrators</strong>&nbsp;-&nbsp;manage resources, approve reservations, and analyze usage data<br />
    47                 <br />
    48                 &nbsp;</p>
    49                 </li>
    50         </ul>
    51         </li>
    52         <li>
    53         <p>I am not aware of similar solutions that are actually in use for this type of system.</p>
    54         </li>
    55         <li>
    56         <p>The system is database-driven and for start a web app is going to be made to access and control it but in the future a mobile app is also a possibility if it gets wider usage.</p>
    57         </li>
    58 </ul>
     12- Lack of information about resource availability
    5913
    60 }}}
     14- Conflicting or overlapping reservations
     15
     16- Limited insight into historical resource usage
     17
     18- Difficulty in planning resource allocation based on actual demand
     19
     20- Information about availability of resources students didn't even knew they could use.
     21
     22There will be three types of users in this system:
     23
     24- Teaching staff - reserve resources for lectures, labs, and research
     25
     26- Students - view availability and access permitted resources
     27
     28- Faculty administrators - manage resources, approve reservations, and analyze usage data
     29
     30
     31I am not aware of similar solutions that are actually in use for this type of system.
     32
     33The system is database-driven and for start a web app is going to be made to access and control it but in the future a mobile app is also a possibility if it gets wider usage.
     34