LAKE BOAT MANAGEMENT SYSTEM

 

INTRODUCTION OF LAKE BOAT ELECTROFISHING MANAGEMENT

Are you looking for Lake boat electrofishing management for your final year project? We are here to help you. You can contact us

Whenever we think about the lake or any water flow we always want to walk over that or swim in it. but fortunately or unfortunately we cannot do that every time due to any reason.

But if we get a chance to go through a boat in the lake we cannot deny that opportunity. W don’t get everywhere this system . but wherever we get this we would love to enjoy those moments.

So here we have the system which can book the boats prior to the ride. One can book the boat through the home with this system. In this system, the users will register in this and vendors or we can say the boat owners will register with whole information of the boats and condition with a staff of them.

Now the user will request for a token of that and give the attributes of no . of people. according to that cost will be calculated and the life-saving tools will be allotted and at the time of ride they can come and take the trip and enjoy the moment.

In this way the system becomes paperless and one can enjoy the trip of the water on demand and confirm.

MODULES OF LAKE BOAT ELECTROFISHING MANAGEMENT

The system is made of the combination of modules which work with collaboration with each other and make it beneficial to accomplish the main aim of the system.

TOKEN GENERATION:

This is the interface every user will see here we have the option to select the time of the ride, no . of people along the journey they are going according to that the cost will be calculated and is given to be paid to the boat owner.

As they do so they can go for the ride. They will get a confirmation where they will be getting all the details of the ride which they will be going like boat number, life tools, staff who will assist them and few more.

they will show this token to get the ride.

BOAT STAFF ASSIGNMENT.

Every boat has many staffs who work on them and maintain the boat, they help in the proper ride of the users. they are responsible for the life tools and providing to the customer and they check the tokens and confirms before giving the ride to the person.

they assigned by the boat owner and they are responsible for them.

LIFE TOOLS CHECK:

Before every ride, the life tools are mandatory to check twice as to clear any kind of danger if exist. This is done by the staff and cleared by the users. Now they can safely go to the ride.

REGISTRATION:

Users information have to be compelled to be registered within the system thus on establish every of them unambiguously and do the-the required group action as simple potential .like on the name of the bill are issued.

on the far side, this plenty of things require measure there wherever we will reference him. Without registration, there are few options and pages one user can see which are landing on the home page and taking the features read but he won’t be allowed to use those.

For use, he will have to register. One person needs to put his all the details properly and precisely as it will be helpful in identifying them and believing that he is the real person who has booked for the same. It also includes driver license for them who is driving and parameter too.

LOGIN:

After registration one will log within the system because the operator of the system either on the behalf of user. when this he has the opposite helpful interfaces accessible for any actions.

Here either bride or groom both have to log in with their unique identity and passwords. After this, they will be directed to the main user interface from where they have further options.

FORGOT PASSWORD:

This is quite often that people tend to forget the password they keep for the login. So this could be very tedious and hectic to recover the password manually in case if one needs to login in the emergency.

So to overcome this problem we have this module named ass forgot the password and using this module user can recover their password in seconds. So here we need to only put our registered email Id and hit the enter.

then one confirmation email will go to the email where we have the option to reset the password. In seconds one can use this module and get rid of forgetting password problem.

ADMIN:

Admin has the official powers to control the flow of the data from one part of the system to the other. He has the power to manipulate the access of the users to the data.

The main purpose of this account is to make the user data relevant and then giving the inputs to the other interface module and make it work optimistically and get the timetable according to the wish we want to create for a particular type of inputs.

Hence all the data will be reflected with clean and well data in the interfaces.

SYSTEM REQUIREMENTS OF LAKE BOAT ELECTROFISHING MANAGEMENT

Now, this method is intended in such the way that it takes fewer resources to figure out work properly. it’s its own type of minimum needs that we’d like to required care of :

The system wants a minimum of two GB of ram to run all the options sleek and unforeseen.

It wants a minimum 1.3 gigahertz processor to run sleek as else which will produce issues.

The system must be operated by some approved person as wrong hands will build it happy-go-lucky.

Rest is all up to the user’s usage can take care of hardware

For security opposing anti-virus is suggested.

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.

SYSTEM DESIGN OF LAKE BOAT ELECTROFISHING MANAGEMENT

ENTITY BOAT OWNER:

PRIMARY KEYBOARD OWNER:_ID:

This is system generated and unique, which can be referenced in any other entity.

BOAT OWNER NAME:

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

QUALIFICATION:

qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

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.

EMAIL:

email is taken to make member aware of new offers new events and for future reference, it is also relevant.

TYPE:

the type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

ADDRESS:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

LAKE NAME:

The name of the lake where he has ownership of the ships.

ENTITY TOKEN:

PRIMARY KEY TOKEN_ID:

This is system generated and unique, which can be referenced in any other entity.

FOREIGN KEY USER_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities.

FOREIGN KEY BOAT_OWNER_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities.

START TIME:

At the time when they will be allowed to board the boat.

END TIME:

Till what time the time when they will be allowed to board the boat.

NO. OF PERSONS:

No . of persons they can go along registered according to them.

COST:

The cost of heading the boat is calculated and liable to pay b user.

FOREIGN KEY LIFE TOOLS_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities.

ENTITY BOAT:

PRIMARY KEY BOAT_ID:

This is system generated and unique, which can be referenced in any other entity.

NAME:

Name of the boat.

BOAT NO.:

A unique number is given to the boat by the owner.

SIZE:

The size or we can say the capacity of the boat.

COST PER TRIP:

The cost of per trip for a single user is given through this interface.

ADDRESS:

The address where the boat will be parked is given in this

ENTITY LIFE TOOLS:

PRIMARY KEY LIFE TOOLS_ID:

This is system generated and unique, which can be referenced in any other entity.

NAME:

Name of the tool is given here.

TYPE:

The type of the tool like where it will be wearable.

COLOR:

Choosy about the colour, colours are mentioned for life tools

ADDRESS:

where these tools are put.

ENTITY STAFF:

PRIMARY KEYSTAFF_ID:

This is system generated and unique, which can be referenced in any other entity.

STAFF NAME:

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

QUALIFICATION:

qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

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.

EMAIL:

email is taken to make member aware of new offers new events and for future reference, it is also relevant.

TYPE:

the type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

ADDRESS:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

FOREIGN KEY BOAT_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities.

ENTITYUSER:-

User data have to be saved in this entity and all fields are required for this purpose which taken from the user .proper validation is checked and the attributes are as follows:

PRIMARY KEYUSER_ID:

This is system generated and unique, which can be referenced in any other entity.

USERNAME:

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

QUALIFICATION:

qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

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.

EMAIL:

email is taken to make member aware of new offers new events and for future reference, it is also relevant.

TYPE:

the type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

ADDRESS:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

ENTITY ADMIN:

PRIMARY KEY ADMIN:

This is the main supervisor of all task happening in the system for long. It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities. It has all the power to make changes in the filed of other tables. It grants the privileges to other users of the system that what kind of operations they can perform.

LOGS:

The logs are saved here to analyze the system accordingly. The changes occur. For necessary changes.

PASSWORD:

A Strong password is recommended for this account as no one wants to get hacked and lose the sophisticated data.

DESCRIPTION:

Any important info. Regarding this account is attributed in this.

USE CASE DIAGRAM OF LAKE BOAT ELECTROFISHING MANAGEMENT

In this system we mainly have three actors first is a user who will book the ride on the boat through the system and after giving the details generate the token and get the details of it to ride on the boat at the particular time.

boat owner assigns the staff on the boat and boat maintenance. The user will head to the boat at the time and get the life tools by staff and enjoys the ride.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF LAKE BOAT ELECTROFISHING MANAGEMENT

FUNCTIONAL REQUIREMENTS OF LAKE BOAT ELECTROFISHING MANAGEMENT SYSTEM:-

The functional requirements lake boat electrofishing management are those requirements which are necessary to the eye of the user and the client. Here we try to make the module possible to accomplish the need of the desired function. few of its functional requirements are as follows-

NON-FUNCTIONAL REQUIREMENTS OF LAKE BOAT ELECTROFISHING MANAGEMENT SYSTEM:-

These requirements needs unit among the style of “system shall be “, associate an overall property of the system as a full or of a particular aspect and not a particular operation.

The system’s overall properties remarkably mark the excellence between whether or not the event project has succeeded or unsuccessful.

NON-FUNCTIONAL OF LAKE BOAT ELECTROFISHING MANAGEMENT SYSTEM NEEDS –

unit of measurement usually divided into 2 main categories:

Execution qualities, like security and quality, that unit evident at the run time.

Evolution qualities, like liabilities, maintainability, flexibility and quantitative, that unit embodied among the static structure of the code.

Non-functional of lake boat electrofishing management system needs place restrictions on the merchandise being developed, the event technique, and specify external constraints that the merchandise has to be compelled to meet

Our project qualifies all the factors of helpful and non-helpful consequently and the system is up to mark performance device.Here we’d prefer to need the care of few lots of things before heading towards the system.

the many sensible intuitive interfaces are usually created. that ultimately build interface easy to use for a lengthy time. in distinction to ancient vogue wherever the goal is to create the difficulty or application physically enticing, the goal of interface vogue is to create the user’s interaction expertise as simple and intuitive as doable – what’s typically mentioned as user-centred vogue.

where smart graphic/industrial vogue is daring and eye-catching, smart interface vogue is sometimes delicate and invisible.

KEEP THINGS SIMPLE AND CONSISTENT:-

Simple and Harmonic means that making u i is extraordinarily intuitive and needs to followed