Introduction of Border Control Management
Are you looking for a Border control management project? We are here to help you. You can contact us. This system is named Border Control Management. This system is made to keep records about the people who are crossing the borders of a country and are going to other countries.
This system helps the border control officers as the people who are going through the border to another country, might have some luggage and that luggage also need to be checked and the passport of the customer also needs to be verified. For some countries passport might not be required, so people going to those countries must have all the other documents required.
This system has one admin account and only admin can add officers who are on duty. The duty officers have duty shifts and this system has all the options that help the officers in their shifts. People crossing through the border who does not have valid documents will be considered terrorists and punishment will be given.
If the people crossing the border get caught with any drugs, then also, they will be given punishment. This system also has the option to add and delete officers as their duty gets keep changing. Admin and the officers can check which officer has a duty on which border and the duty shift. Officers can also apply for leaves using this system.
All other options of this system are explained further in more detail.
You can also check these posts:
- Complaint Management System
- School Finder System
- Prison Management System
- Online Shopping Project in PHP
- Crime Management System
- Banking Management System
- Garbage Management System
- Online Shopping System
- Bus Management System Project
Modules of Border Control Management
Our system has two main interfaces one for Admin panel and other is for User which is jailor.
Along with these, we have other interfaces which can be discussed as below:
Registration:
Officers on duty need to be registered in the border control management system so as to use the system and add the criminals’ details, and complaints, update closed cases, etc. If the user is not registered in the border control management system, he/she cannot do any task. After an officer applies for registration on this system then the admin verifies the registering officer and if the admin verifies the registering officer only then an officer can get registered on this system.
Login:
After registration, one can log in to the system as the operator of the system on the behalf of the user. After this, he has the other user interfaces available for further actions.
Checking Luggage:
Another module that is present in this system is checking the luggage of people. As thousands of people across the borders daily so, it is very important to check the luggage of all. This system can scan the luggage and can tell the officer if any doubtful object is found in any luggage. After that, the owner of luggage can be taken under custody and can be checked again and if anything is found then can be punished.
Punishment:
The second option that is given in this is one of the most important that is adding prisoners. As soon as the court declares that the victim is found guilty and tells his or her punishment and in which prison the victim must be kept, the prisoner will be sent to the same prison as told by the court and all the details of the criminal like name, address, age, criminal number, crime and the punishment all can be updated in the prison management system.
Then later these details can be used further and there is no option to delete the prisoners’ data so once the prisoner is added to the database, no one can delete the data of the criminal and it will be helpful as papers can get lost or can be theft but, in this case, information cannot be lost and there is no use of theft this data as no changes can be made in the database.
Adding Complaints:
The third important feature that is provided by this system is adding complaints. If in any case, the person files a complaint then the complaint can be registered on this system, and then further actions can be taken. Any kind of complaint like missing luggage, doubt on some person, etc. can be registered on this system.
Once a complaint is added then it cannot be deleted because it might be required later.
Payment:
This module is present so that officers can easily pay the amount as the amount paid through this system goes to admin and then admin can make the payments to all the officers according to their work. In some cases, people are also fined and this payment can also be paid using this system.
System Design of Border Control Management:
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 smoothly and suddenly.
- It needs a minimum 1.3 GHz processor to rum 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.
Er Diagram of Border Control Management:
Entity User:
All User’s details need to be stored in a proper manner with very needed attributes. All the other tasks can be performed only if the user is authenticated. After the user has registered and is verified by the admin then the user can perform all the tasks on it.
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 a 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 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.
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.
Entity Admin:
Admin is only a single user who 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.
Entity People:
People who are crossing the border must be saved on this system for safety purposes. A person’s name, age, sex, country he belongs to, person’s id, and address is the entities that are required to be filled on this system.
It has following attributes:
Primary key person id:
As we all know that all the person’s id is always unique so is used here as a primary key. It is easy to find a person using the person’s id as names might be the same for many people.
Address:
As the prisoner is a criminal so for the record there must be a person’s address so that if the person is found wrong then it can be verified from his address.
Name:
Name of the person is important as it is easy to found a person in case it is required.
Crime:
The user must know which prisoner is there and for which crime. So, the user can check it in the database whenever he wants and about whoever he wants.
Punishment:
As the user must know about the crime, he or she must also know about the punishment period and the type of punishment of the prisoner. So, an entity punishment is provided to know about the punishment of the prisoners.
Entity Luggage:
Another module that is present on this system is luggage as everyone crossing the border has luggage so, this system helps in scanning the luggage of people and if anything is found in any luggage the officer can check the owner of the luggage. This system saves the time that gets wasted in checking the luggage of people.
Other attributes of entity guard are as follows:
Name:
The user must know the names of the people as in case if something is found in any luggage then the owner of the luggage can be caught.
Address:
If any person who is crossing the border gets hurt and might found as a fake person then he or she can be verified from the person’s address.
Use Case Diagram of Border Control Management:
In this use case, as you can see, we have our system as a 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 users 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. This user has all the privileges but it cannot register itself on this system as the admin needs to verify the registering 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.
Admin panel:
There can be only one account of admin. Admin can add the users. When a user tries to register on the prison management system then the request goes to admin and if the admin verifies only then the user can register itself on it.
Other privileges that admin has been explained below:
- He can log in 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 a profile of his own and he can search for detail of other Users and can see the detail him.
- This admin is responsible for creating and uploading the Menu card to every User in the Interface.
- He can add a user to that account and give access to handling the prison on their own.
- He can manipulate the data of any user. In this, we are showing here the interaction of the users with our system through our use case diagram.
Functional and Non-Functional Requirements of Border Control Management
The functional requirement of border control management 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 of border control management 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 the user entity.
- The user can add the prisoners: Users are able to add prisoners, which is what they are doing with this system.
- Able to add and delete complaints: The user can add the complaints and their details and if required he or she can also delete the details of the complaint.
Non-Functional Requirements of Border Control Management: –
Non-functional necessities square measure the other demand than practical necessities. These square measures the necessities that specify criteria which will be wont to choose the operation of a system, instead of specific behaviors. Non-functional necessities square measure within the style of “system shall be “, associate degree overall property of the system as a full or of a specific facet and not a particular operation.
The system’s overall properties remarkably mark the distinction between whether or not the event project has succeeded or unsuccessful.
Non-functional of border control management 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 border control management 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.
Here we need to take care of few more things before heading towards the system. The most important feature of the application world is the application’s ease of usage. The application will easy to use if made while keeping in mind that the user need not think twice about searching any feature.
Everything should be made distinctive by using the color combination such that everything needed most frequently highlighted with focus colors. We can use simple layouts like the card and grid layout etc. By varying color and other UI combinations, many good intuitive interfaces can be made. Which ultimately makes the interface easy to use for a long time.
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-centered 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 followed.
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 good way emphasis 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.
Simplified forms: –
The form is made simple to fill with the clean user interface.
Border Control Management Project
Conclusion of Border Control Management
So, the outcome of all the hard work done for the border control management system is here. It is software that helps the user to work with the border control people easily. This software reduces the amount of manual data entry and gives greater efficiency. Anyone who is found doubtful can be caught easily using this system.
The User Interface of it is very friendly and can be easily used by anyone. It also decreases the amount of time taken to write complaint details and other modules. In the end, we can say that this software is performing all the tasks accurately and is doing the work for which it is made.