The entity relationship diagram of online movie ticket booking system graphically represents database tables and relations between movie, customer, cinema, screen etc. The main entity of the online movie ticket booking system is Movie booking website, Customer, Movie, Booking, Movie Show, Cinema, Screen etc. Let’s see what are the entities of movie ER diagram.

Checkout: ER Diagram for Library Management System
Checkout: DFD for Online Movie Ticket Booking System

Online Movie Ticket Booking System ER diagram Entities and their Attributes

Each of the entities have their respective attributes. Attributes of all movie ER diagram entities are as follows:

• Movie Ticket Booking Website:– Attributes are website_name, website_url, contact_no.
• Customer:– Attributes of customer are customer_id, customer_name, customer_address,customer_contact.
• Movie:– Attributes of movie are movie_title, movie_description, Movie_stars.
• Movie Show:– Attributes are show_date, movie, show_time, cinema_name.
• Cinema:- Attributes of cinema are cinema_name, cinema_location, cinema_city.
• Screen:– Attributes of screen are screen_name, screen_no, no_of_seats.

Database Details of Online Movie Ticket Booking System

Movie database ER diagram has following features:

• Each entity contains a primary key and unique key
• For reducing data redundancy, we have normalized all the entities (Movie booking website, Customer, Movie, Booking, Movie Show, Cinema, Screen)
• For faster query execution we have implemented indexing on each table.
• Movie table stores all movie related data, Customer table stores all customer data, Movie Show table stores all different show related details and similarly other tables store respective data.
• 1:1 and 1:M relationship exists in the database.

Download Online Movie Ticket Booking System Synopsis PDF

Online Movie Ticket Booking System ER Diagram

This is an ER model of a movie ticket booking. The entities are represented in rectangular boxes and the relationships between different entities are represented by a diamond shaped box.

Here is complete movie theater database er diagram.

The post Online Movie Ticket Booking System ER Diagram appeared first on 123projectlab.com.

The main purpose of ER diagram for online library management system is to represent data objects and their relationships. The main entity of this ER diagram is library, library admin, employee, member, book, vendor, author and publisher.

Checkout: DFD for Online Library Management System

The Library Management System database working is based on the following assumptions-

• The system keeps track of all users with a single point authentication via user id and password.
• The special feature access is granted based on users’ role (such as admin, employee or member)
• The library admin has full control over the entire system. He can add new employee and member. Admin can assign access right to different users.
• Employee of the library maintain book details of the library. They can issue or receive books from library member. Each employee has unique login id and password.
• Each book has unique book id, title, price and book status (available/issued).
• Each vendor has unique id. Similarly, each publisher also has unique publisher id.
• For better database handling we have used ids in the database for any transaction. Such as at the time of book issue/receive we store book id in the database instead of book title and similarly instead of member name we store member id.
• Employee can generate various library reports such as member report, book report, vendor report etc. Such reports are very helpful in decision making.
• The entire system has several checks to avoid mismanagement. Any employee can not again issue a book which is already issued to someone. There is a check that prevents it from doing so.
• Similarly, entry of any master record such as book, member, vendor, author or publisher can not be deleted if its related record exists in any transaction table.

Library Management System Entities and their Attributes

Each of the entities have their respective attributes which are:

• Admin:-admin_id, admin_name, admin_name
• Library:- library_name, library_address, library_contact_no
• Books:-book_id, book_title, book_price, book_status
• Author:-author_code, author_name, author_qualification, author_subject
• Member:-member_id, member_name, member_address, member_contact, member_type
• Employee:-emp_id, emp_name, emp_designation
• Vendor:- vendor_code, vendor_name
• Publisher:-publisher_code, publisher_name, publisher_country

Database Detail of Online Library Management System

• Each entity in the system contains a primary key and unique key.
• We have implemented indexing on each table for faster query execution.
• There was some data redundancy. So, we normalized all entities (such as admin, employee, member, library, book, author, publisher, vendor).
• Book master table store all books data.
• Member master table store record of all library member.
• Issue receive table store all book transaction details.
• Author, publisher and vendor tables contain records of author, publisher and vendor records respectively.
• 1:M and 1:1 relationship exists in the database.

Download Library Management System Synopsis pdf Now

ER Diagram for Library Management System

This is the ER model of Library management system. The entities are represented in boxes and their attributes are represented in oval shape. The relationships between various entities are represented by diamond shape.

This diagram is drawn in Microsoft Visio software. There are many diagram designing tools. You can know best flowchart software and diagramming tools and easily draw ER diagram for Library management system online.

• Online Movie Ticket Booking System ER Diagram
• ER Diagram for Library Management System (2024)
• ER Diagram for Online Shopping System
• ER-Diagram for Hospital Management System Project
• ER Diagram for Optical Shop Management System
• ER Diagram for Gas Agency Management System
• ER Diagram for Online Book Store
• ER Diagram for Loan Automation System

The post ER Diagram for Library Management System (2024) appeared first on 123projectlab.com.

Checkout: Best Universities for Online MBA Program in USA - 2023

Entity relationship diagram for online shopping system is an ER model of online shopping website entities. It is basically a graphical representation of online shopping database tables and relation between shopping website, customer, order, product, supplier and order tracking. This ER Diagram for online shopping system also describes the data objects and their relationship.

Checkout: Audiobook Speed Calculator
Checkout: ER Diagram for Customer Relationship Management 
Checkout: ER-Diagram for Hospital Management System

Overview of Online Shopping System Database Working

Online shopping application is a widely used application in current scenario. Important feature and working of this application are as follows:

• The online shopping system is client server-based web application.
• Admin has full control over the each and every section of the website.
• The shopping site has huge number of products, which are divided under different product category.
• There are many suppliers who list their products on the shopping portal.
• Customer can visit shopping site and explore different products and order them online.
• After customer registration they can login to the shopping site and add product in the cart and place order.
• After placing the order, they can either pay online or can choose COD option.
• Customer can track their order by a unique tracking id provided by the shopping site.
• Customer can view his previous order history. Customer can also pay online via credit/debit card.
• The entire system is fully secured. Customer can login through their password and shop online.
• Admin can view all daily use reports such as product report, daily order report and payment report etc.

The is the complete working of online shopping system. Now let’s move on to the online shopping system entities and their attributes.

Run your C program s in: Online C Compiler

Entities and Attributes of Online Shopping System

Here are the entities and attributes:

• Admin:- admin_id, admin_name
• Customer:- customer_id, customer_name, customer_address, customer_contact
• Order:- order_no, order_date, order_amount
• Tracking Detail:- tracking_no, courier_name
• Shopping Website:- website_url, website_name, contact_no
• Product Category: – category_id, category_name
• Product:- prod_id, prod_name, prod_price, prod_status
• Supplier:- supplier_id, supplier_name, supplier_address

Database Description for Online Shopping System

• Indexing has been used in each table for faster query execution.
• Each table has a primary key.
• In the database 1:1 and 1:M relationship exists.
• To avoid data redundancy, we have normalized all entities (such as admin, customer, product etc)
• All customer record is stored in customer table, all supplier record is stored in supplier table.
• Similarly order table store all order details, order tracking stores each and every detail related to product delivery process.
• This tracking information can be seen by the customer to know the current status of his order.

Download Online Shopping System Synopsis pdf

ER-Diagram for Online Shopping System

This was complete ER model of online shopping system project. The boxes represent entities and oval shape represents attributes. Diamond shape represents the relationship between two entities.

This ER diagram for online shopping system is drawn on flowchart software. There are many free online flowchart software tools that you can use.

• Online Movie Ticket Booking System ER Diagram
• ER Diagram for Library Management System (2024)
• ER Diagram for Online Shopping System
• ER-Diagram for Hospital Management System Project
• ER Diagram for Optical Shop Management System
• ER Diagram for Gas Agency Management System
• ER Diagram for Online Book Store
• ER Diagram for Loan Automation System

The post ER Diagram for Online Shopping System appeared first on 123projectlab.com.

Checkout: Best Universities for Online MBA Program in USA - 2024

Some of the main entity of this ER diagram for hospital management system are hospital, hospital admin, doctor, staff, indoor patient and outdoor patient. The ER diagram of hospital management system depicts the data objects and their relationship.

Checkout: Audiobook Speed Calculator
Checkout: Data Flow Diagram for Hospital Management System

The hospital management system database working is based on following assumptions

• The user of this system is hospital admin, doctor, cashier, hospital staff etc.
• Each user of the system has different user id and password. They can access some part of the entire system based on their role.
• Admin can appoint new doctor and hospital staff.
• Hospital staff will register new indoor patient and out door patient in the hospital.
• The doctor will visit out patient and give them medical prescription.
• Hospital staff will register indoor patient allocate room and inform specialist doctor.
• Staff will also serve patient in the guidance of doctor attended him. They will provide all medical treatment to them. These service details will be store in database for bill preparation.
• After complete recovery of patient discharge bill will be made by the staff and send to the cashier.
• The cashier will generate discharge bill. Patient will have to pay the bill.

This is the entire working of our hospital management system. We have prepared following ER diagram on these assumptions.

Hospital management system entities and their attributes

Each entity has respective attributes which are:

• Admin:- username, userid
• Doctor:- doctored, doctorname, specialization
• Staff:- staffed, firstname, lastname, designation
• In-Patient:- admissionid, admissiondate, patientname, gender
• Room:- roomid. Roomno, roomcharge
• In-PatientMedical:- admissionid, medicineid, mediciname
• In-PatientBill:- admissionid, paymentid, totalamt
• In-PatientService:- admissionid, serviced, servicename
• Cashier:- staffed, firstname, lastname, designation
• Out-Patient:- patientid, patientname, doctorname
• Out-PatientMedicalinfo:- patientid, outpatientmedid, medicinename
• Out-PatientBill:- patientid, paymentid, totalamt

Database description of hospital management system

• 1:M and 1:1 relationship exists in the database.
• For faster query execution, we have implemented indexing on each table.
• Each entity contains a primary and primary key.
• To reduce data redundancy, we have normalized all entities (such as admin, doctor, staff, in-patient, out-patient, room).
• Doctor table store all doctor’s data.
• In-patient table store all indoor patient data. Similarly, out-patient table store all out door patient data.
• In-patient medical and in-patient service table store patient medical treatment and service details. These details are useful while making patient discharge bill.
• Prescription given by doctor to the out-patient is stored in out-patient-medical-info table to maintain patient treatment history.

Download Hospital Management System Synopsis pdf

ER-Diagram for Hospital Management System

The is complete ER model of hospital management system project. The relationship between various entities are represented by diamond shape. The boxes represent entities and oval shape represents attributes.

This diagram is drawn in flowchart software. There are so many free and paid diagram designing software. Choose the best flowchart software tool and you can easily draw ER diagram for hospital management system.

• Online Movie Ticket Booking System ER Diagram
• ER Diagram for Library Management System (2024)
• ER Diagram for Online Shopping System
• ER-Diagram for Hospital Management System Project
• ER Diagram for Optical Shop Management System
• ER Diagram for Gas Agency Management System
• ER Diagram for Online Book Store
• ER Diagram for Loan Automation System
• ER Diagram for Visa Application Processing System
• ER Diagram for Customer Relationship Management (CRM)

The post ER-Diagram for Hospital Management System Project appeared first on 123projectlab.com.

ER Diagram for Optical Shop Management System Details

The following table describes the detail of optical shop entity relationship diagram

Entities and Attributes of Optical Shop Management System

Here are entities and attributes of optical shop management system:

• Admin: Admin_id, Admin_name, Admin_address, Admin_contact
• Customer: Customer_id, Customer_name, Customer_address, Customer_contact
• Optical Shop Portal: Portal_name, Portal_url
• Eye Checkup: Customer_id, LeftCy, RightCy
• Product: Prod_id, Prod_name, Prod_price
• Shopping Cart: Temp_id, Customer_id, Product_id, Tot_amt
• Payment: Trans_id, Tot_amtReceipt: Receipt_no, Receipt_amount
• Employee: Emp_id, Emp_name, Emp_address, Emp_contact, Emp_department
• Employee Salary: Emp_id, Basic, HRA, DA

What is Optical Shop Management System

Optical Shop Management System is an online application used to manage the entire working of an online shop where eyeglasses, frames etc products are sold. Customers can buy frames and glasses online. There are several employees who manage the entire system. Admin tracks performance of each employee.

Overview of Optical Shop Management System Database Working

• This is a web based application for managing an optical shop and take it online
• There is one person with the role as admin who manages the entire application
• Admin role is to create master records such as product information and create employee record and calculate their salary
• Customer can register online and access online
• Customer can upload their eye checkup data and get suggestion for suitable glasses and frame
• Customer can select product and place order

Download Optical Shop Management System Synopsis pdf

ER diagram for Optical Shop Management System

Finally here is the optical shop management system ER diagram. This diagram is drawn in Microsoft Visio. You can use any flowchart software for making such an ERD.

Notations Used to Represent Relationship Model of Database

ER Models are the conceptual models of the database. Many variations of ER Modeling are in practice but the main difference is notation, symbols that are used to represent.

Entity: Entity is an identifiable object relevant to the system being built. Some examples of entity are:

• Customer
• Employee
• Organization
• Product
• Purchase Order

Attribute: Attribute is the characteristic of an entity. Attributes distinguish one entity instance from another. Attribute of entity Customer might include:

• Customer_id
• First_name
• Last_name
• City
• State
• Pincode
• Insurance_plan

Relationship Set: A relationship is an association among entities. Relationship Set is a collection of relationships of the same type. For example:Customer (xyz) is the owner of Account(98367). Here is the owner of a relationship set.

Conclusion

Optical shop management system is an application specially designed for managing day by day working of an optical shop. Entity relationship diagram for optical shop management system includes all major entities such as optical shop, eye test, product, bill and payment.

This optical shop management system ERD represents a graphical structure of the whole database. This diagram is very helpful to showcase your project working.

The post ER Diagram for Optical Shop Management System appeared first on 123projectlab.com.

Also Check: DFD for Gas Agency Management System

In this article we will discuss the ER diagram for the gas agency management system. An ER diagram for an online gas agency management system illustrates the logical structure of the database, by describing the entities, their attributes and identifying relationships between them.

ER Diagram for Gas Agency Management System Details

The following table describes details of gas agency management system ER diagram

Overview of Gas Agency Management System Database Working

Gas agency management system is a common application for gas agency management. Feature of this application are as follows:

• This is a web based application specially designed for managing gas agency daily workGas agency admin manages entire agency working
• New customer can apply for gas connection online
• After successfully submitted connection applications goes to the admin for approval
• Admin checkes these applications and take decision on them, either approve or reject
• After approval customer payes the registration amount
• Existing customers can book gas refill online Admin confirm cylinder booking and gives an approximate cylinder delivery date to the customer
• Existing customers can also apply for gas connection transfer from one location to another location
• This application is also verified by the admin
• Customer can give feedback of agency service

It was some common features of gas agency management system application working. Now let’s see entities and attributes of online gas agency management system

Entities and Attributes of Gas Agency Management System

Here are entities and their attributes:

• Gas Agency: Agency_code, Agency_name, Agency_address
• Customer: Customer_id, Customer_name, Customer_phone, Customer_address, Agency_name
• Gas Booking : Customer_id, Booking_no, Booking_date, Delivery_date
• Feedback: Customer_name, Feedback_date, message
• Location Transfer : Transfer_requst_no, Customer_id, To_city, To_state, To_agency_code
• Payment : Payment_id, Payment_date, Payment_amount
• Notification: Booking_status, Transfer_status

Database Description of Online Gas Agency Management System

Each table has a primary keyTo avoide data redundancy all tables has been normalizedTo speed up query results indexing has been usedCustomer information is stored in customer table, gas booking details are stored in gas booking tableIn this database 1:1 and 1:M relationship exists

Download Online Gas Agency Management System Synopsis pdf

ER Diagram for Gas Agency Management System

Following diagram represents the entity relationship diagram of online gas agency management system.

This diagram has be drawn in Microsoft Visio software. There are many free flowchart software are also available online, you can access them free.

Some Tips for Effective ER Diagram

As we know ER Diagram is an important diagram. It helps application developer to understand the logical structure of database, so it should be good enough to meet its purpose. Here are some tips to draw effective ERD.

• Give meaningful name to each entity, attribute and relationship of your diagram
• Ensure that one entity may be used once in the diagram
• You can also use colours to showcase important areas of the diagram
• Identify the relationship between entities correctly
• Never connect two entities without a relationship between them

Conclusion

So it was complete details of ER Diagram for Gas Agency Management System. Gas agency is the most common application the is used to manage a gas agency daily working.

This gas agency ERD represents the logical structure of the gas agency database. In the above discussion we also identified entities and their attributes of a gas agency management system.

The post ER Diagram for Gas Agency Management System appeared first on 123projectlab.com.

The entity relationship diagram for online book store is basically an ER model of online book store website entities. ER modeling notation uses three main of constraints: entities, attributes associated with entities and relationships.

This ER Diagram is basically a graphical representation of an online book store database table and relationship between books, order, customer, bookstore website, tracking detail etc.

ER Diagram for Online Book Store Details

Following table describes the details of ER diagram for online book store.

• Name: Online Book Store ER diagram
• Abstract: ER diagram for online book store is basically a graphical representation of the book store database table and relationship between system entities such as book, customer, order, tracking etc.
• Tools: Microsoft Visio
• Designed by: 123projectlab.com

Importance of Entity Relationship Diagram

Tool for data modeling is entity relationship diagram.

To get logical database design we use data modeling. A conceptual model of data is used in an application.

This model is obtained by use of entity relationship model. ER model helps in designing relational database. A relation is a table which describes an entity set. Each column in a relation represents an attribute.

Overview of Online Book Store Database Working

Online book store is a widely used application nowadays. This application is for selling books online. Important feature of this application are as follows:

• Online book store is a client server based application
• Admin manages entire book store website
• Admin add all master records such as book detail, publisher, author etc
• Customer can browse all books details available on store or he can search any specific book
• After book selection customer adds book in the cart and proceed for checkout and payment
• After successfully placing the order, customer gets a confirmation email with a tracking number
• This order parcel is scanned on each hub that comes in its route
• The current location of the parcel is updated after scan on each hub
• Customer can track current location of his order by this tracking number
• Once the order is delivered to the customer it update as completed

Entities and Attributes of Online Book Store

Following are the entities and related attributes:

• Admin: Admin_id, Admin_role, Admin_name
• Bookstore Website: Website_name, Website_url, Contact_no
• Customer: Costomer_id, Customer_name, Customer_address, Customer_contact
• Book: Book_id, Book_title, Book_price, Book_status
• Author: Author_id, Author_name, Author_subject, Author_qualification
• Publisher: Publisher_id, Publisher_name, Publisher_country
• Order: Order_no, Order_date, Order_amount
• Tracking Detail: Tracking_id, Courier_name

Download Online Book Store Synopsis pdf

ER Diagram for Online Book Store

This is the ER diagram for the online book store system. You can showcase logical database design of your project with this diagram.

If your project requirements are little different then you can edit this template.

Conclusion

Entity Relationship Diagram is an important tool for conceptual data modeling. With this diagram we get logical database design.

In this article we learnt all about entity relationship diagram of online book store system, overview of online book store database, importance of ER diagram, entities and attributes of online book store.

You can practice of making ER diagram from more examples.

The post ER Diagram for Online Book Store appeared first on 123projectlab.com.

An ER model is a detailed, logical representation of data for an organization. The ER model is expressed in terms of entities, relationships and attributes or properties.

Checkout: DFD for Loan Automation System 

An entity can be an object, person, place, concept or event about which the organization wants to maintain data. Entity is represented by a rectangle. An attribute is a characteristic or property of an entity. It is represented by an oval shape. Relationships are important to hold the various components of an ER model. A relationship is an association between the instance of one or more entity types.

ER Diagram for Loan Automation System details

The following table shows all the details about ER Diagram for loan automation system:

Importance of Entity Relationship Diagram

During the software development life cycle we have to define system scope and overview of general requirements. ER Diagram is suitable for this phase because this can be translated into a variety of technical architecture for data.

Most organizations use ER modeling for conceptual data modeling. Entity relationship diagrams provide the analyst with a concise notation for examining data within the context of software application.

Entities and Attributes of Loan Automation System

• Admin: Admin_id, Admin_name, Admin_email
• Employee: Emp_id, Emp_name, Emp_address, Emp_contact_no
• Customer: Costomer_id, Costomer_name, Customer_address, Customer_ac_no
• Branch: Branch_id, Branch_name, Branch_address
• Department: Depart_id, Depart_name
• Loan: Loan_type,Loan_amount, Interest_rate
• Loan System: No_of_branch, Name_of_branch
• EMI: loan_id, EMI_amt

Overview of Loan Automation System Database Working

Loan automation system helps to automat loan approval and EMI repayment process. This application is commonly used by loan providing organizations for easy record handling. Some of the main features of this application are as follows:

• Loan automation system works on client server approach
• This application is specifically for loan providing organizations. This is not a general application
• Admin manages the entire loan system. He manages all master records
• Loan system has multiple branches. Each branch has multiple departments
• Admin appointments employees in different branches
• These employee register customer who comes for loan in the branch
• This application also maintain record of loan repayment
• Each loan has a unique loan account number
• Whenever customer pays his loan EMI, it is recorded in customer loan account
• Admin can view all reports such as customer list, loan outstanding report, loan repayment report etc
• Customer can view all paid EMI details

Download Loan Automation System Synopsis pdf

ER Diagram for Loan Automation System

This is an ER Diagram for a loan automation system. This diagram is very helpful in understanding the concept of your project.

You can edit this diagram if requirements of your project are different. This diagram is made using Microsoft Visio. There are many free flowchart software available online.

The post ER Diagram for Loan Automation System appeared first on 123projectlab.com.

Checkout: DFD for Visa Application Processing System 

ER Diagram for Visa Application Processing System Detail

The following table shows the overall description of ER Diagram for Visa Application Processing System

What is Visa Application Processing System

Visa application processing system is a web based application to process a large number of visa application that comes for approval. Manual processing takes a long time and lots of human resource. Use of this application makes the process easy and fast.

Visa applicants access the visa website, register themselves and submit visa applications. This application is verified by the executive and the applicant is asked for an interview. After successful verification and interview visa is approved

Overview of Visa Application Processing System database working

• This is a web based application
• User can apply for visa online
• To send visa application, first of all user has to register himself on the visa website
• After registration there is an option to apply for a visa. User click on the option and fill all required details and submit application
• The Visa website has different executive employees. These executives verify user application
• If users application is verified then an interview date is given to the applicant
• User has to be available for an interview on a given date and time. If the executive is satisfied with applicant’s answers the visa is issued.
• User can also renew if there visa validity date is expired or about to expire

Entities and Attributes of Visa Application Processing System

• User: User_id, User_name, User_address, User_contact
• Visa Application: Appl_id, Visa_country, User_pasport_no, Visa_duration, Visa_type
• Visa Web Portal: Web_address, No_of_registered_user
• Admin: User_id, Admin_name, Contact_no
• Executive: Exe_id, Exe_name, Exe_address, Exe_contact_no
• Visa Renewal Application: Appl_ref_no, Renewal_date_from, Renewal_date_to

Database Description of Visa Application Processing System

• In this ER model mainly two relationship exists: 1:1 and 1:M
• Each database table has a primary key
• To reduce data redundancy all database tables has been normalized
• To get faster result of queries indexing has been used
• All users details are stored in user table, all visa application details is stored in visa application table
• Similarly visa renewal details is stored in visa renewal table

Symbols of used in ER Diagram

Mainly three symbols are used in ER Diagram: Rectangle, oval and diamond.

Rectangle represents an entity. Oval shape represents an associated attribute and a diamond shape represents relation between two entities.

Download Visa Application Processing System Synopsis pdf

ER Diagram for Visa Application Processing System

This is the ER Diagram for Visa Application Processing System. Rectangle represents entities and oval shape represents associated attributes. The diagram shape between entities represents their relationship.

This ER model will help you to showcase your project work. It is easy to understand the working of the system by viewing this diagram. You can edit this diagram if your project requirements are little different. There are many free flowchart software available online.

The post ER Diagram for Visa Application Processing System appeared first on 123projectlab.com.

The entity relationship diagram for customer relationship management (CRM) graphically represents database tables and their relationship.

Checkout: DFD for Customer Relationship Management (CRM)

ER Modeling Notation

The basic entity relationship modeling notation uses three main constraints: data entities, relationships and their associated attributes.

An entity is an object, person or event in user environment about which the organisation want to maintain data. Every entity has its own identity.

A relationship is an association between the instance of one or more entity types.

An attribute is a characteristic or property of an entity. In ER diagram we represents attribute by placing its name in ellipse with line connected to the associated entity.

Overview of Customer Relationship Management (CRM) Database Working

Customer Relationship Management (CRM) is the most common application used by any customer service based organization. As the name indicates this application helps to maintain better relationship with customer by providing them better service. Some of the important feature of this application are as follows:

• The system works in DBMS approach.
• This CRM system can be implemented in any service based organization such as automobile workshop
• Admin of the organisation can add master records such as service and price for each service.
• Each employee has its user id and password through which he can access the system
• Whenever customer comes to the organisation for service for first time, the employee takes his details and register him on the system and open new job Card
• If customer is already registered then employee seach his record and open new job Card
• This job Card is assigned to the respective worker of the organisation
• The worker keeps updating this job Card as the service progress
• Once the entire service is complete admin makes job Card status closed and the detail of service is passed to the billing section for final billing
• Admin can view all required reports such as: customer list, open or closed job Card report and employee report

Entities and Attributes of Customer Relationship Management (CRM)

Customer Relationship Management has following main entities:

• Admin: admin_id, admin_name, admin_role
• CRM Portal: website_url, website_name, contact_no
• Customer: customer_id, customer_type, customer_name, customer_address, customer_contact
• Employee: employee_id, employee_name, employee_address
• Job Card: jobcard_id, jobcard_date, assign_to, jobcard_status
• Service: service_no, service_name, service_amt

Database Description of Customer Relationship Management (CRM)

• In CRM database 1:1 and 1:M relationship exists
• To improve search time, indexing has been used in all tables
• All customer detail is stored in customer table, job Card detail is stored in job Card table
• Similarly employee and service related detail is stored in employee and service table respectively
• All table are normalised to avoid data redundancy and each table has a primary key

Download Customer Relationship Management Synopsis pdf

ER Diagram for Customer Relationship Management (CRM)

Following diagram is the ER Diagram for customer relationship management (CRM).

This diagram is very useful in showing progress of your project work. Rectangle represents entities, oval shape represents attributes of entities and diamond shape represents relationship between two entities.

The post ER Diagram for Customer Relationship Management (CRM) appeared first on 123projectlab.com.