Introduction of The Construction Management System
Are you looking for a construction management system project? We are here to help you. You can contact us. This system is named as Construction Management System. This system is designed to help the customers to make construction easy. Two types of accounts are there other than the admin account.
Looking for Construction Work Management System Project Proposal. Check Our Online Store.
Admin is the one who manages all the accounts and this system. The two other types of accounts are the customer’s account and the vendor account. The customer can update about the project he wants to construct, place the orders according to the project requirements, items required, and can also make the payment for the items and the orders to the vendors.
Vendors can see the projects that are updated by the customers, can take the orders placed by the client, can send the items to the customer that are required by the customer for the project, and can make the payment made by the customer. This system is made to help the vendors to increase their sale of items and to make the project construction easy for the customer.
This system has all the features that are required by the customer who is constructing any building and also has all the functions that are needed by the vendors to increase their work and income source. The customer can also hire construction workers from the vendors as they know all kinds of employees. All other features that are provided by the system are explained further with all the details.
You can also check these posts:
- Vendor Management System
- Street Food Delivery Management System
- Banking Management System
- Online Food Ordering System
- Food Ordering System
- Car Rental System
Modules of The Construction Management System
Our system has two main modules. One is the admin, and the other is the user. The user module is again divided into two parts, either the user can be a vendor or a customer. Interfaces for both users are different.
Along with these, we have other interfaces which can user-centered as below:
Vendor:
This is one of the most important modules. This module helps the vendor to sell the items to the customers. As there are two types of user accounts, the vendor is a kind of account that is asked at the time of user registration. Then after the registration, the provider can add all the items that he sells and can also see all the projects that are updated by the customers for construction.
So, the vendor can sell his items and can increase its market and income.
Payment:
This module is present so that customers can easily pay the amount as the amount paid through this system goes to admin, and the admin can make the payments to all the vendors after deducting his profit percent. It reduces the customer’s headache. The customer can pay the amount through net banking, debit card, or credit card.
Login:
After registration, one can log in to the system either as the event manager or the customer. The option to register either as a vendor or as a customer is given when the user is registering. The further interface of this system depends upon the user’s registration type.
Order:
This module is present so that customers can easily select the items required for the construction and after selecting all the items and the number of articles can place the order to the vendor.
Items:
This module shows the customer list of all the things provided by the vendors. The customer can select items from the list and can make the payment at the same time. In the item section, there is also an option to add manpower to the project where the customer can take the employees for the project and can pay them for their work.
Project:
After the user has created an account for a customer, then one option that is given to the client is to upload the project that he wants to construct. It can be a house, any building, or a bungalow. After the customer uploads the project, the vendor can look at the project and can contact the customer if he wants to take the project and want to provide all the items that are required to complete the project.
Admin:
This module is present only for one account. That is, no one can register as an admin after one account is created. The admin account has all the privileges, to check any particular seller or customer, block any account, calculate the payment, making changes into accounts of users, etc.
Customer:
As explained in the login section, the user can be of two types and both the users will have different interfaces and after the user has registered. The user as a customer can see all the available items that he can take on rent or can buy. He can make the payment of articles and can upload its project.
Other Features:
Other various features are provided in this system that is different for customer and vendor accounts. Like paying the amount by online mode for the items bought is present in the client interface.
System Design of The Construction Management System:
Now, this system is designed in such a way that it takes fewer resources to work properly.
It has its sort of minimum requirements that we need to take care of:
- The system requires 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 correctly, and all the testing is done as per the requirements.
Er Diagram of The Construction Management System:
Entity Vendor:
As explained earlier in the construction management system, the user can be of two types and both the users will have different interfaces, and after the user has registered and login then the features provided can be used by the user. The vendor can provide services to the customer, can see the projects of the customer, can take the payments from the customer, etc.
Other attributes of entity vendor are as follows:
Name:
The user must know the name through which he or she has chosen to register itself on the system.
Number:
The phone number is taken here to keep the member updated and the confirmation of the event is also managed through this method.
Address:
Address of the user is required at the time the customer is registering itself on the system.
Shop name:
All the vendors have their shops so some name must be there to know the store, in case the customer wants to go shopping.
Items:
In this section, all the articles that are sold by the vendor and the price at which they,” can be seen.
Payment:
In this section, the vendor can see all the payments made by the customer and can calculate how much amount is remaining to be taken and from which customer it is to be taken.
Entity Customer:
All customer details need to be stored properly with essential attributes. After the admin 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 address:
As all the customers have a different address so, it is used as a primary key. The customer’s address is required in case the customer wants to pay the amount from home and then the shop owner has to send someone to take money from the customer’s home.
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 made here to keep the member updated and the confirmation of the event is also managed through this method.
Email:
Email is considered to make member aware of new offers for new events and for future references it is also relevant.
Address:
Address of the user is required at the time the customer is registering itself on the system.
Password:
The password is required to login into the system, and the password must contain a unique character, a numeric character, and an upper-case letter. Password must contain at least six characters. One must keep the password careful so that no one can get into your account and make any changes.
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 make the payment using their debit card or by net banking.
Some features of payment entity are explained further:
Name:
Name of the customer is required as the bill will be made by the vendor on the name of the customer.
Number:
The phone number is taken here to keep the member updated and the confirmation of the event is also managed through this method.
Address:
Address of the user is required at the time the customer is registering itself on the system.
Items:
On the bill, all the elements bought by the customer and the quantity in which it is purchased will be printed.
Entity Admin:
This module is present only for one account. That is, no one can register as an admin after one account is created. The admin account has all the privileges, to check about any particular account. To block any account, to calculate the salary of the employees after deducting their leaves, to update the status about any project, to track any courier, to calculate the payment, to check the payment type, etc.
Admin name:
As the account created must have some name, so the admin’s name is used to create the account.
Password:
The password is required to login into the system, and the password must contain a unique character, a numeric character, and an upper-case letter. Password must contain at least six characters. One must keep the password careful so that no one can get into your account and make any changes.
Logs:
As the admin manages all the accounts so he can see all the history of all accounts. In customer’s account record contains the items bought, date, amount, and the name of the vendor from which the items are purchased. In case, the customer made the transaction to the wrong vendor; then it helps both the customer and the supplier.
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 Project:
In this entity status of the project can be checked by both the vendor and the customer. The vendor who is providing the items and the employees for the client must get updates about the project so that he can talk to the customer confidently. Customers must get updates about the project because the customer is the one who is investing in the project and must know when the project will be completed and how much is left.
Project name:
The project name is required because the vendor can be giving services to many customers at the same time. So, to know the updates about the project he must know the name of the project.
Customer name:
It is required so that the vendor can know who is the owner of the project to which he is giving services.
Vendor name:
It is necessary so that the customer can know who the vendor from which he is taking the services is.
Phone number:
Phone number of both the customer and the vendor is required so that they can contact each other if necessary.
Amount:
It is the estimated amount that is calculated at the feasibility time. This amount can vary, and this number can be seen with other details of the project. The amount can be paid online or by cash.
Entity Order:
This entity talks about all the orders that are made by the customer to the vendor or that are completed by a vendor. The customer might want to pay the amount together for all the orders made. So, it is easy to look at all the requests made and pay the sum to the vendor.
This entity also helps the vendor as the vendor delivers the orders to many customers so he can quickly calculate the total quantity he bought and the total number 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.
Vendor name:
This entity helps the customer to know which order is made by which vendor. How much amount is to be paid, what are the other items required etc.
Items:
From this, the customer and the vendor 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 vendor in case there is any problem with the order made and the order delivered. The phone number is asked of both users at the time of the registration.
Payment:
From this entity, it can be seen that how much price is charged for 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.
Project:
The vendor must know that the order sends to the customer is for which project, what is the status of the project, when it will be completed, and how much amount is to be taken from the customer. The customer can also know all these details.
Use Case Diagram of The Construction Management System:
In this use case of the construction management system, 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 types of users one is an admin, and the other is a user type.
Users:
Two users are present here in this system. One is an 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 checks the user only when he is eligible to use the system. Attributes given to the user are:
Admin panel:
There can be only one account of admin. Admin can add the users. When a user tries to register on this system, then the request goes to admin and if the admin verifies only then the user can register with 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 system 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 The Construction Management System
The functional requirement of this is that it does what it is meant for. A functional requirement of the construction management system 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 feed into the system:
This system is doing that properly in user entity.
Buying the items required:
The customer could go but the items that are needed to construct the project.
Making Payment:
As the customer has bought different items from a vendor, then he should be able to make the payment to him.
Admin can add the users:
Admin can verify and add the user, which is they are doing with this system.
Non-Functional of The Construction Management System: –
Non-functional necessities square measure the other demand than practical needs. These square measures the needs that specify criteria which will be would not 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 regime 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 necessities of the construction management system – are often divided into two broad 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 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 .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 done distinctively in the construction management system by using the color combination such that everything needed is most frequently highlighted with focus colors. We can use simple layouts like the card and grid layout etc. 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 purpose of the interface method is to create 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, the original interface style is commonly delicate and invisible.
Keep things simple and consistent: –
Straightforward 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 correctly: –
Color combo of lite and dark is right way emphasis and done well in this system
Consider feedback messages: –
The feedback form is a perfect way taking feedback of forms and improving the system.
Simplified forms: –
The structure is made simple to fill with the clean user interface.
Conclusion of The Construction Management System
So, the outcome of all the hard work done for the Construction management system is here. It is software that helps the customer to buy the items required for project development. This system helps the customer get its project done smoothly, efficiently, and in less time and it helps the vendor to increase the work and income source.
This system is made to help both the consumer and the seller and from the above points, it is clear that the services for which it is developed, are served smoothly by this system.