Ip Synopsis1
Ip Synopsis1
A Project Synopsis
Submitted To
Submitted By:
Page No.
1.Introduction
1.1 Purpose
1.2 Scope
1.4 References
2. Overall Description
2.9 ER Diagram
“MOTEL MANAGEMENT SYSTEM”
Description of Project:
Team Members: 03
Team Members Name, 1.Avdheshwar Singh Sisodiya
2.Shubham Karanjiya
3.Vibhor Jain
Supervisor Mr. Ashutosh Rajguru
Front End Tool Python IDLE/Anaconda(Spyder)
Back End Tool MYSQL/CSV
1. Introduction:-
Purpose:-
The main purpose of the Motel management system is to show the details
of the entire customer, Room (whether they are allotted to the customer or not),
Services offered by the management. It manages all information about Room
number, Customer name, Amount, Check IN date and time, Check Out Date and
time, ID PROOF, Address, Mobile number, etc. By this information Admin and
User will know the details about the customer and the room which he/she has
allotted. The purpose of the project is to build application program to reduce the
manual work for managing the details and services.
Scope:-
It may help collecting perfect management in details. In very short time, the
collection will be obvious, simple and sensible. It will help a person to know the
management of passed year perfectly and vividly. It also helps in current all works relative
to Motel management system. And it will reduce manual work. Manual work can be miss
or misplaced but in this all data will store in Databases and can only be access by “ID” and
“PASSWORD” only.
References:-
Book References:-
Web References:-
www.google.com
www.wikipedia.com
Technologies to be used:-
While adding motel services, the Admin or User has to enter its “ID,
NAME, AMOUNT, CHECK IN(DATETIME),CHECKOUT(DATETIME),
ROOMNO, CUSTOMERID PROOF, and CUSTOMER ADDRESS”. If
ROOMNO is already exists, then this system does add the items and show error.
And in this system Admin can perform all the action but the User can only ADD
and VIEW data cannot delete and update data.
Product Perspective:-
Any visitor can see the website and if he got any query than he can submit it on site by
the help of enquiry form. No login required for submitting query. Also, motel manager
can upload details (Daily available room) on site.
Software Interface:-
Hardware Interface:-
Client Side:-
RAM - 4 GB
Server Side:-
RAM - 1GB
Database - MySQL
Product Functions:-
The Admin can Add, Delete, Update, View Data and the User can only View and
Add Data but before for the first time they to register themselves and then for the next time
they have to login.
1. Admin module
2. User module
1. Admin module:-
The administrator will get all the enquiries which has been submitted by the visitors on
website. Also, admin can reply those queries with the solution. Also, the admin can view
that data uploaded by the manager.
2. User module:-
User Characteristics:- This project has mainly two users that are Admin and User.
1. Admin:-
The Admin can upload all details on application and can perform any action.
2. User:-
The User can view data uploaded by the Admin and Add Data.
Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. So when a system
is analyzed to gather its functionalities use cases are prepared and actors are identified.
Now when the initial task is complete use case diagrams are modeled to present the
outside view. The purposes of use case diagrams can be as follows:-
Motel
ADMIN USER
REGISTRATION REGISTRATION
LOGIN LOGIN
Database design is the process of producing a detailed data model of a database. This
logical data model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a Data Definition Language,
which can then be used to create a database. A fully attributed data model contains
detailed attributes for each entity.
The term database design can be used to describe many different parts of the
design of an overall database system. Principally, and most correctly, it can be thought of
as the logical design of the base data structures used to store the data.
ER Diagram:-
The entity is a person, object, place or event for which data is collected. The
relationship is the interaction between the entities. The cardinality defines the relationship
between the entities in terms of numbers. The relationship is the interaction between the
entities
Room_No
Room_Type Alloted
Motel
Room_Charges Services
Id_proof
Cust_Emailid Room_No
Cust_Address Check_in
Check_out
Cust_No
Room_No Cust_Name
Customer
Id_proof Cust_ph_no
Cust_Emailid Cust_Address