INTRODUCTION OF TEA STALL MANAGEMENT SYSTEM

Are you looking for Tea stall management system for your final year project? We are here to help you. You can contact us

This system is named as Tea Stall Management System. This system helps the tea stall owners to take orders and to deliver them easily. This system helps the customers to place orders easily and to make payments.

This system has all the features like making changes in orders, knowing the status of an order, making payment in online mode if the customer wants.

This system also has the option to add different industries into the system so that the employees working in any company can make the order and as some companies have rules to pay for their employee’s order so, the payment can be taken from the company on the monthly basis.

Only those customers who are verified by the industry can make the orders from company’s name. This system has the option to make changes into the menu and customers can choose the order from available items.

This system also has the option to manage staff which is working for the tea stall. Staff’s attendance can be saved on this system and their monthly salary can also be calculated on this system.

This system has one admin account which verifies the registering customer. All other features of this system are explained further with details.

MODULES OF TEA STALL MANAGEMENT SYSTEM

Our system has only two main interfaces. One is for the admin and the other one is for the user, the here user can be a customer, an industry or a tea seller. Along with these, we have other interfaces which can be discussed as below:

Admin:

This module can only have one account and this account has all the privileges which a user account might not have. First of all, admin account is created and then if the admin verifies a registering user then his account will be created.

Tea Stall:

This module consists of tea seller. The option to register as a seller or a customer is given at the registration time. This module contains the options to add items in the menu, managing staff, adding customers and taking payment etc.

Customer:

This module is different from tea seller module and a user registered as a customer cannot register as a seller. This module contains the options to make orders from tea sellers, adding items into order, managing account, making payment to tea seller and adding the industry in which he works etc.

Different Industries:

The customer can be an industry also as some companies give its employees to make some orders from tea sellers and the company itself pays for the employees. So, the company might make the payment on the monthly basis. Then the tea seller can add the company to his account as a permanent customer.

Items:

This module contains all the items that the seller is selling. Tea seller can make changes into the list of items he sells. As an order contains many items, all the items can be seen in the history of the order is old.

Staff:

It is the module which shows the employees working for a particular tea seller. Their details can be seen by the tea seller and their salary can be calculated easily as the system has the option to do it by adding the salary and leaves of each employee.

Order:

This module is available in both the interfaces, one of the customers and the other of the seller. The customer can see the items he has ordered in order, can check the status of the order made and can also see the old orders made by him as it saves the order history.

In the tea seller’s module, he can see the order made by the customer and can update the status of the order and he can also the orders made by the customer in the past.

Other Features:

There are other various features that are provided in this system like adding and deleting staff, deleting order history and adding payment remaining to pay.

SYSTEM DESIGN OF TEA STALL MANAGEMENT SYSTEM:

Now this prison management system is designed in such a way that it takes fewer resources to work properly. It has its own sort of minimum requirements that we need to take care of :

The system needs a minimum of 2 GB of ram to run all the features smooth and sudden.

It needs a minimum 1.3 GHz processor to run smooth as less than that may create problems.

The system needs to be operated by some authorized person as wrong hands can make it irresponsible.

Rest is all up to the user’s usage will care for hardware

For security Antivirus is recommended.

The system is made properly and all the testing is done as per the requirements. So, the rest of the things depend on the user and no one can harm the data or the software if the proper care is done. All the attributes are working perfectly and if any error is found then it can be removed easily.

ER DIAGRAM OF TEA STALL MANAGEMENT SYSTEM:

ER DIAGRAM OF TEA STALL MANAGEMENT SYSTEM

Entity Tea stall:

Every User detail needs to be stored in a proper manner with very needed attributed. As all the other tasks can be performed only if the user is authenticated. Some of the features of the user are as follows:

Primary key User id:

The user id is system generated and unique, which can be referenced in any other entity.This mostly for recognizing it in the unique way anywhere in the program.

Username:

Username is taken from the user and fed into this it is properly validated so that no mistake happens.

Number:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.
Employees:

Tea seller can add all the employees working under him and can do their monthly salary calculations.

Payments:

In this section, the seller can see all the remaining payments he has to take from customers or from companies and can also see the payments they have to make to employees and others.

Address:

Address of the user is required at the time the user is registering itself on the system. The address can be the shop address or the home address.

Entity Customer:

The customer is the entity which requires it to order the items he wants from a tea seller if he wants to make payment to the seller. If any customer has any query then there is also an option to put your query and it will be answered by your service provider.

Some of the features of the customer entity are explained below :

Industry name:

The customer might be working in an industry so, the option to add the industry name is given. It also helps the tea seller to know that how many industries are taking the services.

Address:

The address is required because if the customer is not working in any industry and is taking services then the bill of the orders can be taken from the given address if required. So, the address of the customer is required.

Salary:

It is required because the seller has to make the payments to the employees who are working and he can know the salaries that others are giving to the employees.

Phone number:

It is required because the customer can make the order and when the employee has to deliver the order to the given address then he can call the customer to know the exact location.

Entity payment:

This module is present in both the interfaces but the options that are provided are different. In the customer’s interface, there is an option to pay the bill using their debit card or by net banking.

Customers can also see their payment status after paying their bill. In the Tea seller’s module, there is an option to take the bill. Some features of payment entity are explained further :

Number:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

Address:

The address is required because if the customer is not working in any industry and is taking services then the bill of the orders can be taken from the given address if required. So, the address of the customer is required.

Entity Staff:

In this entity, the employees who are working can be seen. A job that they do can be seen, their salary can be seen. Other attributes of this entity are as follows:

Name:

The user must know the names of employees which he or she has chosen either to work.

Phone number:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

Salary:

Salary can be paid online using this system after deducting the leaves that an employee has taken in a month.

Address:

Address of the user is required at the time the user is registering itself on the system. From the address of the employee, it can be verified that the person is good or bad.

Job Profile:

From this section, it can be known that what kind of task is performed by the employee at the job.

Entity Admin:

Admin is only a single user which can verify the user who is trying to register on this prison management system. If the admin verifies the user then only the user can see the details and can make changes according to the given privileges.

No other user can register as admin as there is only one account for admin.

Username:

Username is taken from the user and fed into this it is properly validated so that no mistake happens.

Password:

The password is required to login into the system and the password must contain a special character, a numeric character and an uppercase letter.

Logs:

As the admin manages all the accounts so he can see all the history of all accounts. In customer’s account log contains the items bought, date, amount and the name of the seller from which the items are bought.

In case, the customer made the transaction to the wrong seller, then it helps the both the customer and the seller.

Verification:

If the admin verifies a registering user only when a user can get itself registered on the system.

Admin-id:

Admin can keep anything as id because there is only one admin account and it does not matter what the id is.

Entity Order:

This entity tells about all the orders that are made by the customer to the seller or that are completed by a seller. The customer might want to pay the amount together for all the orders made. So, it is easy to look at all the orders made and pay the amount to the seller.

This entity also helps the seller as the seller delivers the orders to many customers so he can easily calculate the total quantity he bought and the total quantity he sold.

Customer name:

This entity is required to know that which order is sent to which customer and how much payment is to be taken from that customer.

Seller name:

This entity helps the customer to know which order is made to which seller. how much amount is to be paid, what are the other items required etc?

Items:

From this, the customer and the seller can know which items are delivered and which are remaining and can also know how much quantity is delivered.

Phone number:

This entity helps both the customer and the seller in case there is any problem in the order made and the order delivered. The phone number is asked from the both users at the time of the registration.

Payment:

From this entity, it can be seen that how much price is charged for each and every item and how much amount is to be made. Payment can be made by the customer using net banking, debit card and credit card.

USE CASE DIAGRAM OF TEA STALL MANAGEMENT SYSTEM:

USE CASE DIAGRAM OF TEA STALL MANAGEMENT SYSTEM

In this use case as you can see we have our system as box and the users who use our system are of the kind of outside the box but related to the system. There are two kinds of user one is admin and the other is user type.

Users:

There are two users that are present here in this system. One is admin but the other is a user. After the admin verifies the user only when he is eligible to use the system and after that, it has all the privileges.Attributes given to the user are:

Adding user:

Admin can add a new user and can save it. The details of the user can be seen only by the valid users.

Adding staff:

In this attribute or column, the user can add the details about the staff members.

Adding customers:

This entity is about the details of the customers who are using the service from the company and all other details of them.

Admin panel :

There can be only one account of admin. When a user tries to register on prison management system then the request goes to admin. Other privileges that admin has been explained below :

He can Login through his id and password. The password is made very secure so that no person can guess and make it difficult for hackers to crack.

He has access to the profile of his own and he can search detail of other Users and can see the detail of him.

He can add a user to that account and give access to for handling the prison on their own.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF TEA STALL MANAGEMENT SYSTEM

Functional requirements of tea stall management system:

The functional requirement of this is that it does what it is meant for. A functional requirement describes what a software system should do, while non-functional requirements place constraints on how the system will do so. Functional requirements specify a function that a system or system component must be able to perform. It can be documented in various ways. The most common ones are written descriptions in documents and use cases.Few of its functional requirements are as given below:-

User data should be fed into the system:

This system is doing that properly in user entity. After fetching the data of the customer, the bill can be made and sent to the customer.

Admin can add the users:

Admin can verify and add the user, which is they are doing with this system. He can also delete the users if required.

Non-Functional of tea stall management system:-

Non-functional necessities square measure the other demand than practical necessities. This square measure the necessities that specify criteria which will be wouldn’t to choose the operation of a system, instead of specific behaviours.

Non-functional necessities – are often divided into 2 main categories:

Execution qualities, like security and usefulness, that square measure evident at the runtime.

Evolution qualities, like liabilities, maintainability, flexibility and quantifiable, that square measure embodied within the static structure of the code.

Non-functional of teal stall management system necessities place restrictions on the merchandise being developed, the event method, and specify external constraints that the merchandise should meet.

Our project qualifies all the criteria of functional and non-functional accordingly and the system is up to mark performance vice. Unlike ancient style wherever the goal is to form the thing or application physically enticing, the goal of interface style is to form the user’s interaction expertise as straightforward and intuitive as attainable – what’s typically known as user-centred style.

Where smart graphic/industrial style is daring and eye-catching, smart interface style is commonly delicate and invisible.

Keep things simple and consistent:-

Simple and Harmonic way making UI is very intuitive and needs to follow.

Make good use of typography:-

The typography is taken care very strictly as the need of the system.

Use colour and contrast properly:-

Color combo of lite and dark is a good way emphasise and done well in this system

Consider feedback messages:-

The feedback form is a very good way taking feedback of forms and improving the system.

CONCLUSION OF TEA STALL MANAGEMENT SYSTEM

Finally in tea stall management system, all the hard work is done for tea stall management system is here. It is a software which helps the tea sellers to increase their customers, to increase their work and to increase their income source.

This system helps the customers to make orders and make payments of their orders easily. The User Interface of it is very friendly and can be easily used by anyone. This system has different user interfaces for the different user types.

It also decreases the amount of time taken to write details manually and other modules. At the end, it can be said that it is serving all its purposes very smoothly and efficiently for which it is made.