Requirements - eaakashmaurya/CS308_Fall20-Team5_SlotBookingProject GitHub Wiki

Version	Date	Author(s)	Description
v1.0	09/11/20	Zaidan Bhat (B18040)
		Aakash Maurya (B18042)
		Chandan Prakash (B18050)
		Kalyani Kumari (B18063)
		Mohit Kumar (B18072)

1. Introduction
   1.1. Need and Purpose
   1.2. Intended Audience
   1.3. References
   

2. Description
   2.1. Features and Function
   

   • Features
   • Functions
   2.2. Users
   

3. Specific Requirements
   3.1. External Interfaces
   3.2. Performance Requirements
   3.3. Design Constraints
   3.4. Additional Comments
   

4. Appendix A

This project aims to create an online platform for online booking and management of equipment for C4DFED. Convenience and ease of use is the integral part of this platform. This is a PHP based website and uses SQL database to store and retrieve data.

With the wide-spread availability of PCs, laptops and smartphones, lab equipments users can book thier slots online. When it comes to give an yearly report, the lab management finds it typical to retrieve all informations of lab equipment uses. Hence, there is a need for an inexpensive, easy-to-use slot booking tool.

SlotBooking tool fills this need. It allows the lab management to have the availability of equipments instantly updated on its website. Users and cocncerned faculties can see the availability and book equipments. It is also integrated with a payment gateway which generates bills and also show previous uses (history).

This document is intended for software managers and designers, and for sales and marketing people. The managers of the labs may also read the document.

[1] Recommended Security Protocols for Online Banking Transactions, Recommendation R.73, Organisation for Secrecy in Securities, 2110.
[2] Billing Interface for Class 3 Digital PABX, Standard G.893, Association of PABX Vendors, 1897.
[3] “Capability Maturity Model”, Wikipedia, the free encyclopedia,l accessed on 25/10/2011, http://en.wikipedia.org/wiki/Capability_Maturity_Model
[4] Pankaj Jalote, An Integrated Approach to Software Engineering, 3rd ed., Springer, 2005

SlotBooking can be used by several users at the same time. Users access it via a browser. It is intended for novice users and hence has extensive online help and validation of data.The Lab administration use it as a tool to maintain their register for equipment uses and accpet/reject a booking by users.

The user module handles
1. request to book slots
2. checkout their previous bookings
3. maintain proper to book equipments sequencially

The admin module handes
1. approve/reject request
2. mainatin equipment history
3. see particular user's history
4. help in yearly auditing

1. Managers
2. Equipment users

SlotBooking requires an entry-level PC for labs with up to 100 equipmemts. Users can use any thing which support browsing.

The SlotBooking server can run on any recent version of Linux, such as Ubuntu, Debian, Fedora Core, Redhat Enterprise, etc. It requires: 1. Apache 4.5 or later 2. Tomcat 5.6 or later 3. PHP 5.6 The SlotBooking user-interface works with any of the following graphical browsers on any hardware and OS: 1. Firefox 5.0 2. Internet Explorer 7.2 3. Chrome 2.0 4. Safari 3.6 5. Opera 2.3 Higher versions of these browsers are likely to work but cannot be guaranteed.

This product is useful only in a capitalist, democratic society.

1. Can log in and see pending requests of users.

2. For every equipment, he/she can approve or reject a request
   2.1. If approved for the preferred slot, booking status = OK.
   2.2. If rejected for the preferred slot, a message with the next available time has to be sent to that user by the admin (manual kind of thing).
   

3. Admin needs a yearly report in which it is shown usage of equipment is shown, the name of users, revenue generated, etc are shown. This yearly report will be manually made but the admin should have the option to mail all the users that please provide us your achievements (publications) that you acquired working with the equipment.

4. Admin wants the utility to see bookings details on a yearly basis or monthly basis.

5. Admin can see the usage of a particular user.

6. Admin can see the usage of particular equipment.

7. Admin can generate a billing invoice for a user purchase.

8. Admin can generate revenue of equipment for a particular period of time.

9. (Optional) Admin and user can chat in remarks

10. (Optional) Asks for publication details i.e. if they achieved something significant by the time they are returning their item or any time later, they can add it with the details of the equipment issue.

1. Can book equipment for a period of time.
2. users can log in to his account.
3. Users can make an account. Info about him - Name, Institute, Supervisor or Faculty, Company/ Incharge, Master Student, Funding source, etc.
4. Users can see their previous bookings.
5. Users can book equipment, telling its usage, time period, etc.
6. Users can see the costs of every equipment.
7. Users can book multiple types of equipment at a time.
8. User is usually a Master student, working under a faculty. Frequently uses the equipment.
9. Users can see the amount (order statistics) for the usage of equipment.
10. Users can ask for bill invoices.
11. Users do experiments and sometimes (their experiments are published). They can share publication details with the admin.
12. No need to share the results of every experiment.

On an entry-level PC acting as server, with 100 equipments, the maximum response time for any online request must be less than 2 secs.

• Every equipment has some usage cost.
• Cost is mentioned in the website.
• Charges depend on time of use.

### Booking booking _id, user_id, equi_id, date of the booking, time starts, time end, cost, rate, amount,

This document describes a software product purely for project submissions. It is only related to our project.