MeetBuss Report

MEET - BUSS
Book Your Business Meetings

A PROJECT REPORT ON
“Meet-Buss”
Submitted by
Urvi Shah (150240116036)
Guided by
Prof. Sanjay Makwana

In fulfillment for the award of the degree
of
BACHELOR OF ENGINEERING
IN
DEPARTMENT OF INFORMATION TECHNOLOGY
Hasmukh Goswami College of Engineering, Ahmedabad.
Gujarat Technological University, Ahmedabad
April, 2019
HASMUKH GOSWAMI COLLEGE OF ENGINEERING,
Department of Information Technology
2019
CERTIFICATE
Date:
This is to certify that the Project entitled “Meet-Buss’’ has been carried out
by Urvi Shah (150240116036) under my guidance in fulfillment of the degree
of Bachelor of Engineering in Information Technology Engineering (8th
Semester) of Gujarat Technological University, Ahmedabad during the
academic year 2019.
Internal Guide: Head of Dept.:
Prof. Sanjay Makwana Prof. Hitesh Patel
Asst. Professor, IT Dept. Head, IT Dept.
HGCE, Vahelal HGCE, Vahelal
Sign of External Examiner:

GUJARAT TECHNOLOGICAL UNIVERSITY
CERTIFICATE FOR COMPLETION OF ALL ACTIVITIES AT ONLINE PROJECT PORTAL
B.E. SEMESTER VIII, ACADEMIC YEAR 2018-2019
Date of certificate generation : 25 March 2019 (10:54:58)
This is to certify that, Shah Urviben Rajeshkumar ( Enrolment Number -

150240116036 ) working on project entitled with Meet-Buss from Information
Technology department of HASMUKH GOSWAMI COLLEGE OF
ENGINEERING, VAHELAL had submitted following details at online project
portal.
Periodic Progress Reports (PPR) Completed
Business Model Canvas (Image) Completed
Business Model Canvas (Report) Completed
Patent Drafting Exercise (PDE) Completed
Final Plagiarism Report Completed
Final Project Report Completed
Name of Student : Shah Urviben Rajeshkumar Name of Guide : Mr. Sanjay Kirtibhai Makwana
Signature of Student : _____________ *Signature of Guide : ________________
Disclaimer :
This is a computer generated copy and does not indicate that your data has been evaluated. This is the receipt that GTU
has received a copy of the data that you have uploaded and submitted as your project work.
*Guide has to sign the certificate, Only if all above activities has been Completed.
COMPANY PROFILE
Company Name : Teksun Microsys Pvt. Ltd.
Address : 415, Palladium Business Hub, Opposite : 4D Square Mall, Nr. VGEC
Collage Visat-Gandhinagar Highway, Motera, Harikurpa Society,
Chandkheda, Ahmedabad, Gujarat 380005
Contact No : +91 - 079 2329 9559
Email Id : info@teksun.in
Teksun is a global Electronic R&D Services company providing services such as PCB Design,
Hardware Development, Firmware Development, Technology Research, Product Engineering
Services, New Product Development, Product Re-Engineering, Product Sustenance, and
Manufacturing to a number of industry verticals such as Consumer Electronics, Automotive,
Healthcare, Industrial ,Automation, Home Automation, IOT, Security & Surveillance, Aerospace
& Defense, Cloud and Mobility.
Our services include design and development consultancy services at every stage of the product
design, right from the product concept to production. Teksun team is well equipped to deliver the
reliable and quality product solutions at the shortest possible development time. We offer design
services in the area of Embedded Hardware, Firmware Design and Turn-Key Product Design and
Solutions.
Teksun is an Original Equipment Design firm providing world-class design and development
services to its clients. Our services include design and development consultancy services at every
stage of the product design, right from the product concept to production. Teksun team is well
equipped to deliver the reliable and quality product solutions at the shortest possible development
time. We offer design services in the area of Embedded Hardware, Firmware Design and Turn-
Key Product Design and Solutions.
PLAGIARISM SCAN REPORT
Words 990 Date March 26,2019
Characters 6277 Exclude Url
13% 87% 6 41
Plagiarized
Plagiarism Unique Unique Sentences
Sentences
Content Checked For Plagiarism

A) What is Android ? Android is Linux-based Operating System for mobile devices such as smartphones and tablet
computers. Android is open source, it was developed first by Andy Rubin and then handover to open handset
Alliance, led by Google, and other companies. (B) Why Android as a Front End? Android applications are written in
the Java programming language. The compiled Java code along with any data and resource files required by the
application is bundled by the app tool into an Android package, an archive file marked by an. Apk suffix. This file is
the vehicle for distributing the application and installing it on mobile devices; it's the file users download to their
devices. All the code in a single. Apk fileis considered to be one application. (C) Why uses Android? Android
application can be freely downloaded and they are also available on web. Bellows is the list of software is given
which we need to develop an Android Application Java JDK(java development kit)5 or later version • Android
SDK(software development kit) • Java Runtime Environment (JRE) 6 • Eclipse or Android studio • Eclipse IDE for Java
Developers (optional) Android Runtime This is the third part or section of the android architecture and it is available
on the second layer from the bottom of the architecture. This section provides a key component called Dalvik
Virtual Machine which is a kind of Java Virtual Machine specially designed and optimized for Android. Linux core
functions are used by the dalvik virtual machine-like memory management and multi-threading, which is intrinsic in
the Java language. The Dalvik VM enables every Android application to run in its own process, with its own instance
of the Dalvik virtual machine. Core libraries are also provided by this section which enable Android application
developers to write Android applications using standard Java programming language. Application Framework Many
high-level services are provided by this layer. Application developers are allowed to make use of these services in
their applications. • Activity Manager − Controls all aspects of the application. Design Approach All Software design
methods share the same goal - to transform a set of data processing requirements into a computer program. The
major objectives of the software design process are to document in sufficient detail the software design based on
the software requirements and traceability to specifications. The output is complete, consistent, correct, testable
and understandable information that can be used as input for code generation. The Functional Specifications and
the system specifications are used as inputs for this process. The process ends when all the objectives of the
software requirement document are met. System Design System Design is an important phase in which quality is
fostered in software development design is the process that actually transforms the requirements in to a finished
software product (or) system. Design is the process of translating the requirement prepared during system study
into design. The system design phase employs a variety of tools such as class diagram and so on. System design is
primarily a synthesis function. In designing a new system, one must have a clear picture of what is required and
what must be done in order to achieve the requirement. Web pages are designed in such a way that it should be
easily understandable for a layman. Output Design The output is the most important direct source of information to
the user. Intelligent output Design will improve the systems relationship with the user and also helps in decision
making, once the output requirement is determined, the system designer can decide, what to include in the system
and how to structure it, so that the required output can be produced. Hence the output requirements are to be
determined before going to actual system design. Output design is based on the following factors. • Layout for the
presentation of outputs. • A simple and neat format is preferred rather than complex form of output. Input Design
Input Design is a part of overall system design which requires very care attention. If an error occurs in the input
data then the result of that error may lead to unwanted problems. Errors committed by users can be controlled by a
proper input design. Normally the data will be keyed into the system through the standard input device like
keyboard. In such case, a validation program should be there to check the validity of the data. Database Design
Database design is the most critical part of the design phase. An elegantly designed, well-defined database can play
as a strong foundation for the whole system. Database design transforms the information domain model created
during the analysis into the data structures that will be required to implement the software system. Conceptual
Level Conceptual level describes the major data objects and relationship between them. This level uses symbols
from a modeling method called Entity Relationship Analysis. Entity Relationship Analysis uses three major
abstractions to describe data. They are as follows, • Entities: Distinct objects of the system an entity is a conceptual
representation of an object. • Attributes: Properties of the entities. • Relationship: Meaningful interaction between
entities. Relationship between entities makes up the database structure. • Three types of relationship exist among
entities. They are, • One-to-One: Association between two entities. • One-to-Many: Association between one entity
with two or more entities. • Many-to-One: Association between two or more entities in both directions. Detailed
design The database used here is designed using Fire Base. It has very advanced security features which are very
essential while storing the data. 9.1 Limitations: • This application can not work on android devices having less
android versions from KitKat 4.1. • This application cannot work without internet connection. • Sometimes
implementation on large field and data is challenging. • For use this application Android phone is required. It cannot
work on IOS and Microsoft devices. • At present situation refund generation of advanced payment is difficult and
complicated.
Sources Similarity
Android: Java, C or C++? - Stack OverflowCompare text

i wrote some simple apps in android using java. but later i found this: … how is it related to this: … are all three
languages possible? sorry for the dumb question. 10%
https://stackoverflow.com/questions/8901488/android-java-c-or-c
Текст: Application FundamentalsCompare text
this file is the vehicle for distributing the application and installing it on mobile devices ; it's the file users
download to their devices . 10%
https://lingualeo.com/ru/jungle/application-fundamentals-14117
Android ArchitectureCompare text

this section provides a key component called dalvik virtual machine which is a kind of java virtual machine
specially designed andthe android runtime also provides a set of core libraries which enable android application 15%
developers to write android applications using standard java...
http://www.tutorialspoint.com/android/android_architecture
Android Application Penetration Testing - Part 1- Android Pentesting...Compare text

application developers are allowed to make use of these services in their applications.these comprise both the
native applications provided with the particular android implementation (for example web browser and email 5%
applications) and the third-party applications installed by the user after...
https://gbhackers.com/android-application-penetration-testing-1/
DECLARATION OF ORIGINALITY
We hereby certify that we are the sole authors of this report and that neither any part
of this report nor the whole of the report has been submitted for a degree to any other
University or Institution.
We certify that, to the best of our knowledge, the current report does not infringe upon
anyone’s copyright nor violate any proprietary rights and that any ideas, techniques,
quotations or any other material from the work of other people included in our report,
published or otherwise, are fully acknowledged in accordance with the standard referencing
practices.
We declare that this is a true copy of report, including any final revisions, as approved
by review committee. We have checked write up of the present report using anti-plagiarism
database and it is in allowable limit. Even though later on in case of any complaint pertaining
of plagiarism, we are sole responsible for the same and we understand that as per UGC
norms, University can even revoke Bachelor of Engineering degree conferred to the student
submitting this report.
Date:
Place: Ahmedabad
Student name Urvi Shah

Enrollment no. 150240116036
II
ACKNOWLEDGEMENT
I wish to express my heartfelt appreciation to all those who have contributed to this
project, both explicitly and implicitly, without the cooperation of whom, it would not have been
possible to complete this project.
This final year project has been carried out at the Department of Information
Technology Engineering, Gujarat Technological University. I would like to express my
sincere thanks to my external guide Mr. Prakash Bamaniya (Teksun Pvt. Ltd) whose
guidance and encouragement is invaluable. It has been an honor and memorable experience
working with him.
I would also like to thank my internal guide Prof. Sanjay Makwana, Assistant
Professor of IT Department and Prof. Hitesh Patel, Head Of Department and the faculty
members of HGCE who had helped me directly or indirectly in my project work.
We are thankful to Dr. J. K. Ratnadhariya, Principal Of Hasmukh Goswami

College of Engineering, Vahelal for his consistent encouragement, valuable suggestions and
moral support.
We would like to thank all our friends for all the thoughtful and mind stimulating
discussions we had, which prompted us to think beyond the obvious.
We cannot end without thanking our lovely family, on whose encouragement, support,
and love, we have relied throughout my studies. We would like to thank to all those who has
directly or indirectly supported us in carrying out this report work successfully.
I thank my parents for standing behind me all the time and I thank my friends for their
advice, guidance and help. I thank God for all his blessings.
Urvi Shah (150240116036)
III
Project ID : 34347
LIST OF FIGURES
FIGURE NO FIGURE NAME PAGE NO.
Fig. 1.1 Android Architecture 05
Fig. 2.1 Iterative Model 08
Fig. 2.2 Time duration chart 10
Fig. 4.1 Employee Use Case 24
Fig. 4.2 Use case of Hotel Manager 25
Fig. 4.3 Use Case of Admin 26
Fig. 4.4 E-R Diagram 27
Fig. 4.5 Sequence Diagram of Admin 28
Fig. 4.6 Sequence Diagram of Hotel Manager 29
Fig. 4.7 Sequence Diagram of Employee 30
Fig. 4.8 Flow Chart of Admin 31
Fig. 4.9 Flow Chart of Employee 32
Fig. 4.10 Flow Chart of Hotel Manager 33
Fig. 4.11 Data Dictionary 34
Fig. 4.12 Booking Data Dictionary 35
Fig. 4.13 Employee Data Dictionary 35
Fig. 4.14 Payment Data Dictionary 35
Fig. 4.15 Hotel Data Dictionary 36
Fig. 4.16 Feedback Data Dictionary 36
Fig. 4.17 Help Data Dictionary 36
Fig. 4.18 DFD level-0 37
Fig. 4.19 DFD level-1 Admin 38
Fig. 4.20 DFD level-1 Employee 40
Fig. 4.21 DFD level-1 Hotel Manager 42
Fig. 5.1 Activity Diagram of Admin 50
Fig. 5.2 Activity Diagram of Employee 51
Fig. 5.3 Activity Diagram of Manager 52
Fig. 5.4 Registration Page 53
Fig. 5.5 Login Page 54
Fig. 5.6 Forget Password Page 55
IV
Project ID : 34347

Fig. 7.1 White Box Testing 61
Fig. 7.2 Black Box Testing 62
Fig 8.1 Admin Authentication Page 65
Fig 8.2 Admin Data Manage Page 66
Fig 8.3 Admin Data Page 67
Fig 8.4 Admin Side Payment Details Page 68
Fig 8.5 Dashboard Page 69
Fig 8.6 List of Room Page 70
Fig 8.7 Filter Page 71
Fig 8.8 Places ( Room ) Details Page 72
Fig 8.9 Registration Page 73
Fig 8.10 Login Page 74
Fig 8.11 Forget Password Page - I 75
Fig 8.12 Forget Password Page - II 76
Fig 8.13 Booking Page 77
Fig 8.14 Payment Page - I 78
Fig 8.15 Payment Page - II 79
Fig 8.16 Confirmation Mail Page 80
Fig 8.17 Booking History Page 81
Fig 8.18 Facilities Page 82
Fig 8.19 Account Settings Page 83
Fig 8.20 Help Page 84
Fig 8.21 FAQ Page 85
Fig 8.22 Feedback Page 86
Fig 8.23 Contact Us Page 87
Fig 8.24 Terms & Condition 88
Fig 11.1 PMMS Status 91
Fig 11.2 PPR Status 92
Fig 11.3 PSAR Status 92
Fig 11.4 Design Engineering Sheet Status 93
V
Project ID : 34347

Fig 11.5 AEIOU Sheet 93
Fig 11.6 Empathy Sheet 94
Fig 11.7 Ideation Canvas Sheet 95
Fig 11.8 Product Development Sheet 95
Fig 11.9 Business Model Canvas Status 96
Fig 11.10 Business Model Canvas Sheet 96
Fig 11.11 Patent Drafting Exercise 97
VI
Project ID : 34347
LIST OF TABLES
TABLE NO. TABLE TITLE PAGE NO.
Table 2.1 Roles and responsibility 11
Table 2.2 Effort Estimation 15
Table 2.3 Questions 16
Table 2.4 Language Selection 17
Table 7.1 Admin Activities 64
Table 7.2 User Activities 64
VII
Project ID : 34347
LIST OF SYMBOLS AND ABBREVIATIONS

SYMBOLS
Symbol Name Notation
Use Case Diagram:
System Boundary
Use Case
Actor
Uses
Data Flow Diagram:
Entity
Data Process
Data Flow
Data Store
VIII
Project ID : 34347
Entity Relationship Diagram:
Entity
Attribute
Relationship
Flow Chart:
Process
Input
Decision
Terminator
Flow
IX
Project ID : 34347
ABBREVIATIONS
Abbreviated Form Expanded Form
SRS Software Requirement Software
S/W Software
H/W Hardware
DBMS Database Management System
GUI Graphical User Interface
OOP Object Oriented Programming
UI User Interface
UML Unified Modeling Language
Admin Administration
X
TABLE OF CONTENTS
Title
Certificate Page I
Plagiarism Report
Declaration of Originality II
Acknowledgement III
List of Figures IV
List of Tables VII
Notation & Abbreviations VIII
Abstract XI
Chapter : 1 Introduction
1.1 Project Summary 01
1.2 Purpose 02
1.3 Scope 03
1.4 Technology & Literature Review 04
Chapter : 2 Project Planning & Scheduling
2.1 Project Model 08
2.2 Project Planning & Scheduling 10
2.2 Risk Management 11
2.2.1 Risk Identification 12
2.2.2 Risk Analysis 12
2.2.3 Risk Planning 13
2.4 Estimation 14
2.4.1 Effort Estimation 14
2.4.2 Risk Analysis 18
Chapter : 3 System Requirement Study
3.1 User Characteristics 19
3.2 Hardware and Software Requirement 20
3.3 Constraints 20
Chapter : 4 System Analysis
4.1 Study of Current System 21
4.2 Problem & Weakness of Current System 21
4.3 Requirements of New System 21
4.4 Feasibility Study 22
4.5 Requirement Validation 23
4.6 Function of System 24
4.6.1 Use Case Diagrams 24
4.7 Data Modeling 27
4.7.1. E-R Diagram 27
4.7.2. Sequence Diagram 28
4.7.3. Flow Chart 31
4.7.4 Data Dictionary 33
4.8 Functional & Behavioral Modeling 37
4.8.1 Context Diagram 37
4.8.2 Data Flow Diagram (0 and 1 level) 38
4.8.3 Process Specification & Decision Table 38
4.9 Main Modules of New System 44
4.10 Selection of Hardware & Software Justification 44
Chapter : 5 System Design
5.1 Database Design 45
5.1.1 Tables and Relationships 45
5.2 System Procedural Design 48
5.2.1 Designing Pseudo code 48
5.2.2 Flow Chart or activity design 50
5.3 Input/output and Interface design 53
Chapter : 6 Implementation Planning and Details
6.1 Implementation Environment 56
6.1.1 Single Vs. Multi-User 56
6.1.2 GUI Vs. Non-GUI 56
6.2 Program/Module Specification 56
6.3 Security Features 56
6.4 Coding Standards 57
6.5 Sample Code 57
Chapter : 7 Testing
7.1 Testing Plan 60
7.2 Testing Strategies 60
7.3 Testing Methods 64
7.4 Test Cases 64
Chapter : 8 Screen Shots and User Manual
8.0 Screen Shots and User Manual 65
Chapter : 9 Limitations and Future Enhancement
9.1 Limitations 89
9.2 Future Enhancement 89
Chapter : 10 Conclusion 90
Chapter : 11 Appendix
PMMS Status 91
Periodic Progress Reports (PPR) 92
Patent search and Analysis Report (PSAR) 92
Design Engineering- Canvas Activity 93
Business Model Canvas (BMC) 95
Patent Drafting Exercise (PDE) 97
References 98
MEET-BUSS
Submitted By:
Urvi Shah (150240116036)
Supervised By:
Prof. Sanjay Makwana
Assistant Professor,
Department of Information Technology,
Hasmukh Goswami College of Engineering, Vahelal.
Abstract
Finding the place for meeting which is as per the requirements is quite difficult on local websites.
It is also a time-consuming process to find out a perfect place. So, this idea is about meeting
booking. By which company manager can find out a particular place. Basically, in this application
any company can book the conference hall for meeting purpose. Here it will provide multiple
choice for meeting of the hotel rooms or any conference hall which is registered by their owner.
There are mainly three types of registration/login i.e. company registration, conference hall/hotel
manager registration and guest registration. The places for meeting are registered by their
owners. If any company want to book any hall/room then he/she can register and find the places
as per their requirements. The places are filtered by their price and facilities. Hotel manager can
manage all the new updates which are newly available and attract users. So this application is
beneficial to hotels too.
XI
Project ID : 34347 Introduction
Introduction
1.1 PROJECT SUMMARY
1.1.1 WHAT IS MEETING ROOM BOOKING SYSTEM?
1.2 PURPOSE
1.3 SCOPE
1.4 TECHNOLOGY AND LITERATURE REVIEW
HGCE(IT)
CHAPTER 1
Introduction
Now a days everyone is going online for each work. Each people always used to
find a short way to complete their work. So basically, in this application any company can
book the conference hall for meeting purpose. It is tough to find out relevant options for
booking conference hall. Normally if we want to book any place we have to search it and
find out relevant place if we do not satisfy then again search for it. Here we are providing
multiple choice for meeting of the hotel rooms or any conference hall which is registered
by their owner. So by using this application easily anyone can find out a perfect choice as
per requirements. Also it is very good opportunity for hotels and conference room owners
to advertise their facilities.
1.1 Project Summary

The major purpose of this document will be to describe in brief about the Meet-
Buss. All the processes which are included in hotels and company will be described in this
document. The main characteristic of the system regarding its input and output process and
all the facilities which will be included in the operation and is described in this document.
The basic idea of how the work is going in this project will described in this document.
Admin is responsible for all the management of data. Hotel and Company do
registration itself. Only registered persons can access the booking part of the application
and only authorized members can generate report and got notification. Guest user can see
options about available rooms but can not access booking of that room without register.
There are three types of users for current system:
1. Admin
– Admin can manage user
– Admin can Generate Reports
– Admin can Manage Records
1
HGCE(IT)
2. Employee
– Employee can Check list of rooms
– Employee can Select place
– Employee can Manage booking
– Employee can Manage payment
3. Hotel manager
– Hotel manager can Manage profile
– Also can Manage booking
– Hotel manager can Manage offers
– Also can Manage payment
4. Guest User
– Guest user can check rooms
– Select room
– Register to application
– Login to application
1.1.1 What is Meeting Room Booking System?

A meeting room booking system can give venue owners a more effective and more
profitable way of managing their spaces. Even managing a single space can be difficult if
it is in high demand, and if a venue owner relies on analog methods, it is only a matter of
time before the space is double booked or a client uses the space without paying. Modern
management software, paired with A/V technology integrated into the space, ensures that
this doesn’t occur, and helps venue management reliably oversee any number of spaces.
1.2 PURPOSE
The purpose of this system is to reduce the complexity and finding out the proper
place for meeting which is as per requirement and nearly available. Easily book the room
and get facilities.
2
HGCE(IT)
• Goals:
– Reduce complex work like finding places as per requirements
– Provide many options to book
– Helpful to employees who have busy schedule
– Beneficial to Room owners to join online and get customers
– To increase the digital work and online booking
• Objective:-
– This application will reduce complex work like finding places as per
requirements.
– If this project is implemented successfully then each company must join to this
– Integrate with any existing online application.
– One can make dynamically changes.
– Employees and managers can generate notification.
– In future new technology can be applied.
– It can be used for all the companies and hotels so they can take advantage of it
– Main objective of the this is to reduce struggle and save everyone’s valuable
time.
– User interface would be user friendly so operator can easily operate system.
1.3 SCOPE
This application provide a real time application that means it will respond as per
your requirements. So by sing this you can get the place which ever you want. Meeting
rooms booking system can give venue of owner’s place a more effectively and more
profitable way of managing their spaces. Even managing a single space can be difficult if
it is in high demand. By this you can also get if the place is available or not and also get
the ratings of that particular room.
For now it is only for Ahmedabad so in future if this project will get successful then
we can develop it on the large base (i.e. Gujarat ).
3
HGCE(IT)
1.4 TECHNOLOGY AND LITERATURE REVIEW

(A) What is Android ?
Android is Linux-based Operating System for mobile devices such as
smartphones and tablet computers. Android is open source, it was developed first by Andy
Rubin and then handover to open handset Alliance, led by Google, and other companies.
(B) Why Android as a Front End?
Android applications are written in the Java programming language. The compiled
Java code along with any data and resource files required by the application is bundled by
the app tool into an Android package, an archive file marked by an. Apk suffix. This file
is the vehicle for distributing the application and installing it on mobile devices; it's the file
users download to their devices. All the code in a single. Apk fileis considered to be one
application.
(C) Why uses Android?
Android application can be freely downloaded and they are also available on web.
Bellows is the list of software is given which we need to develop an Android Application
Java JDK(java development kit)5 or later version
• Android SDK(software development kit)
• Java Runtime Environment (JRE) 6
• Eclipse or Android studio
• Eclipse IDE for Java Developers (optional)
4
HGCE(IT)
Android Architecture:-
Android operating system is a collection of software components. These software
components are divided into five categories and four main layers are given below in the
architecture diagram.
Fig 1.1 Android Architecture

Linux Kernel
At the bottom of the layers is Linux - Linux 3.6 with approximately 115 patches.
Kernel provides a level of abstraction between the hardware od device and all the required
hardware are contained by it.
Libraries
On top of Linux kernel there is a collection of libraries including open-source Web
browser engine WebKit, well known library libc, SQLite database etc.
Android Libraries
This category encompasses those Java-based libraries that are specific to Android
development. Examples of libraries in this category include the application framework
libraries in addition to those that facilitate user interface building, graphics drawing and
5
HGCE(IT)
database access. A summary of some key core Android libraries available to the Android
developer is as follows –
• android.app − Provides access to the application model and is the cornerstone of
all Android applications.
• android.content − Facilitates content access, publishing and messaging between
applications and application components.
• android.os − Provides applications with access to standard operating system
services including messages, system services and inter-process communication.
• android.text − Used to render and manipulate text on a device display.
• android.view − The fundamental building blocks of application user interfaces.
• android.widget − A rich collection of pre-built user interface components such as
buttons, labels, list views, layout managers, radio buttons etc.
Android Runtime
This is the third part or section of the android architecture and it is available on the
second layer from the bottom of the architecture. This section provides a key component
called Dalvik Virtual Machine which is a kind of Java Virtual Machine specially designed
and optimized for Android.
Linux core functions are used by the dalvik virtual machine-like memory
management and multi-threading, which is intrinsic in the Java language. The Dalvik VM
enables every Android application to run in its own process, with its own instance of the
Dalvik virtual machine.
Core libraries are also provided by this section which enable Android application
developers to write Android applications using standard Java programming language.
Application Framework
Many high-level services are provided by this layer. Application developers are
allowed to make use of these services in their applications.
• Activity Manager − Controls all aspects of the application lifecycle and
activity stack.
• Content Providers − Allows applications to publish and share data with other
applications.
6
HGCE(IT)
• Resource Manager − Provides access to non-code embedded resources such

as strings, color settings and user interface layouts.
• Notifications Manager − Allows applications to display alerts and
notifications to the user.
• View System − An extensible set of views used to create application user
interfaces.
Application Components:-
These android Application components are very essential building blocks of an
Android application. These components are loosely coupled by the application manifest
file AndroidManifest.xml it defines how the different components of the application will
interact.
Activities
An activity represents a single screen with a user interface, in-short Activity
performs actions on the screen. For example, an email application might have one activity
that shows a list of new emails, another activity to compose an email, and another activity
for reading emails.
Services
A service is a component that runs in the background to perform long running
operations. For example, a service might play music in the background while the user is in
a different application, or it might fetch data over the network without blocking user
interaction with an activity.
Broadcast Receivers
Broadcast Receivers simply respond to broadcast messages from other applications
or from the system.
Content Providers
A content provider component supplies data from one application to others on
request. Such requests are handled by the methods of the ContentResolver class. The data
may be stored in the file system, the database or somewhere else entirely.
7
HGCE(IT)
Project ID : 34347 Project Management
Project Management
2.1 PROJECT MODEL

2.2 PROJECT PLAN & SCHEDULING
2.3 RISK MANAGEMENT
HGCE(IT)
2.1 PROJECT MODEL:-

Iterative Model design
Iterative process starts with a simple implementation of a subset of the software
requirements and iteratively enhances the evolving versions until the full system is implemented.
At each iteration, design modifications are made and new functional capabilities are added. The
basic idea behind this method is to develop a system through repeated cycles (iterative) and in
smaller portions at a time (incremental).
Following is the pictorial representation of Iterative and Incremental model:
Fig 2.1 Iterative Model

Iterative and Incremental development is a combination of both iterative design or
iterative method and incremental build model for development. "During software
development, more than one iteration of the software development cycle may be in
progress at the same time." and "This process may be described as an "evolutionary
acquisition" or "incremental build" approach."
In incremental model the whole requirement is divided into various builds. During
each iteration, the development module goes through the requirements, design,
implementation and testing phases. Each subsequent release of the module adds function
to the previous release. The process continues till the complete system is ready as per the
requirement.
HGCE(IT) 8
The key to successful use of an iterative software development lifecycle is rigorous

validation of requirements, and verification & testing of each version of the software against
those requirements within each cycle of the model. As the software evolves through successive
cycles, tests have to be repeated and extended to verify each version of the software.
Iterative Model Application
Like other SDLC models, Iterative and incremental development has some specific
applications in the software industry. This model is most often used in the following
scenarios:
• Requirements of the complete system are clearly defined and understood.
• Major requirements must be defined; however, some functionalities or requested
enhancements may evolve with time.
• There is a time to the market constraint.
• A new technology is being used and is being learnt by the development team while
working on the project.
• Resources with needed skill set are not available and are planned to be used on contract
basis for specific iterations.
• There are some high risk features and goals which may change in the future.
• Integration and Testing: All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.
• Deployment of system: Once the functional and non functional testing is done, the
product is deployed in the customer environment or released into the market.
• Maintenance: There are some issues which come up in the client environment. To fix
those issues patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.
• All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases.
HGCE(IT) 9
2.2 PROJECT PLAN & SCHEDULING:-

• Requirement Analysis: -All important requirements of the system to be developed are
captured in this phase and documented in a requirement specification done.
• System Design: -In this phase the requirement specifications from first phase are analysis
in this phase and system design is ready to prepare. System Design helps to specifying the
hardware and system requirements and also helps to defining overall system architecture.
19/06/2018 08/08/2018 27/09/2018 16/11/2018 05/01/2019 24/02/2019 15/04/2019
Project definition selection
Requirement Analysis
Select server and softwares
designing of application
static pages
connect static pages
connect with data base
testing by inserting each entity
maintanence
Fig 2.2 Time duration chart

• Implementation: -In which inputs from system design and the system was developed in
small programs called units and integrated in the next phase. In which each unit is
developed and tested for its functionality which is called Unit Testing.
• Testing: -All the units developed by the implementation phase, which are integrated with
a system after testing of each unit.
HGCE(IT) 10
• Maintenance: - There are some problems which come up in the client environment. To fix
those problems are released. Also to enhance the product efficiency and extend the versions
are released. Maintenance is done to deliver these changes in the customer environment.
Roles and Responsibilities:

There are role of the user to first of all analysis, designing, coding, testing and documentation.
The main responsibility of the system is to satisfy the institute’s requirement and provide all
facility which institute demanded.
RESPOSIBILITY MEMBER
Analysis Urvi Shah
Design Urvi Shah
Coding Urvi Shah
Testing & Implementation Urvi Shah
Documentation Urvi Shah
Table 2.1 Roles and Responsibility

2.3 RISK MANAGEMENT:-
Risk management defines the process of measuring, or assessing, risk and developing
strategies to manage it. In which Strategies involve the transferring the risk to another party and
avoiding the risk and also reducing the negative effect of the risk, and accepting some or all of the
other sequences of a particular risk.
Traditional risk management focuses on risks stemming from physical and legal causes
(e.g. natural disasters or fires, accidents, death, and lawsuits). Financial risk management focuses
on risks that can be manage by traded financial instruments. In ideal risk management, a
prioritization process is follow the process of the risks with the greatest loss and the greatest
probability of occurring are manage by first, and risks with lower probability of occurrence and
lower loss are manage by later.
HGCE(IT) 11
2.3.1 RISK IDENTIFICATION

Risk Identification is a systematic attempt to specify threats to the project plan. By
identifying the known and predictable risks, the project manager takes a first step towards avoiding
them when possible and controlling them when necessary.
One method of identifying risks is to create a risk item checklist. The checklist can be used
for risk identification and focuses on some subset of known and predictable risks in the following
subcategories.
• Product Size –risks associated with the overall size of the software to be built or
modified.
• Business impact –risks associated with constraints imposed by management.
• Customer Characteristics – risks associated with the sophistication of the customer and
the developer’s ability to communicate with the customer in a timely manner.
• Process Definition – risks associated with the degree to which the software process has
been defined and is followed by the development organization.
• Development Environment – risks about the availability and quality of the tools to be
used to build the project.
• Technology to be built – risk on the complexity of the system to be built and the newness
of the technology.
• Staff size and experience – risks with the overall technical and project experience of the
software engineers who will handle the work.
2.3.2 RISK ANALYSIS

Regardless of the prevention techniques employed, possible threats that could arise
inside or outside the organization need to be assessed. Although the exact nature of
potential disasters or their resulting consequences are difficult to determine, it is beneficial
to perform a comprehensive risk assessment of all threats that can realistically occur to the
organization.
Types of Risks: -
• Performance Risk – The degree of uncertainty that the product will meet its
requirements and be fit for its intended use. As we are trainees, the performance risk is
there in our project.
HGCE(IT) 12
• Cost Risk – The degree of uncertainty that the project budget will be maintained. The
cost of our project is already decided by management.
• Support Risk – The degree of uncertainty that the resultant software will be easy to
correct, adapt, and enhance. Client of this project is in different premises.
• Project Risks – Threaten the project plan. If project risk become real, it is likely that
project schedule will slip and that costs will increase. The budget of this
project was decided before starting the project and it is enough to complete it. All the works
are divided between team members. Required all the resources are available.
• Technical Risks – Threaten the quality and timeliness of the s/w to be produced. If
technical risk becomes real, implementation may become difficult or impossible.
Technology is already decided for this project.
• Business Risks – Threaten the viability of the s/w to be built. This is live project so no
business risk is there.
• Known Risks – are those that can be uncovered after careful evaluation of the project
plan.
• Experience Risks – Are extrapolated from past project experience. As we are trainees,
make this project no such experience is there.
2.3.3 RISK PLANNING (IDENTIFY STRATEGIES TO MANAGE THE RISK)

To mitigate the risks, project management must develop a strategy for reducing turnover.
Among the possible steps to be taken are:
• Meet with current staff to determine causes for turnover (e.g. poor working
conditions, low pay competitive job market)
• Reduce those causes that are under our control before the project starts.
• Organize project teams so that information about each development activity is
widely dispersed.
• Conduct peer reviews of all work.
• Assign a backup staff member for every critical technologist.
HGCE(IT) 13
2.4 ESTIMATION :-
“Software project scheduling is an activity that distributes estimated efforts across the planned
duration by allocating the effort to specific software engineering tasks.”
2.4.1 EFFORT ESTIMATION

Project Estimation proper evaluation of the system and to get the estimation of the
project, it was needed to do some metrics calculation for this project. Software
project metrics are the way to do this task efficiently.
For this project, function-oriented metrics were used to get the size of the project
at the abstract level (without taking the language in consideration). For that
purpose, Function Points (FP) was used.
• Number of external inputs (EIs) – inputs given by a user or another

system
• Number of external outputs (EOs) – outputs derived within the system
or given to another system
• Number of external inquiries (EQs) – as an online input that results
in generation of some immediate software response in the form of an
on-line output.
• Number of internal logical files (ILFs) – logical grouping of data that
resides within the application’s boundary and is maintained via external
inputs.
• Number of external interfaces files (EIFs) - logical grouping of data
that resides external to the application but provides data that may be of
use to the application
HGCE(IT) 14
Information Domain values defined as under

Measurement Parameters Count Simple Average Complex Total
Number of user inputs 2 X 3 4 6 = 6
Number of user outputs 4 X 4 5 7 = 20
Number of user inquiries 5 X 3 4 6 = 20
Number of files 20 X 7 10 15 = 200
Number of external 4 X 5 7 10 = 28
interfaces
Count=Total 274
Table 2.2 Effort Estimation
Question 0 1 2 3 4 5
1. Does the system require reliable backup and

recovery?
2. Are data communications required?
3. Are there distributed processing functions?
4. Is performance critical?
5. Will the system run in an existing, heavily

utilized operational environment?
6. Does the system require on-line data entry?
HGCE(IT) 15
7. Does the on-line data entry require the input

transaction to be built over multiple screens or
operations?
8. Are the master file updated on-line?
9. Are the inputs, outputs, files, or inquiries

complex?
10. Is the internal processing complex?
11. In the code designed to be reusable?
12. Are conversion and installation included in

the design?
13. Is the system designed for multiple

installations in different organizations?
14. Is the application designed to facilitate

change and ease of use by the user?
Total
36
Table 2.3 Questions

Formula = count x [0.65+0.01 x SUM [fi]]
The Function Point is: 179.0864
HGCE(IT) 16
Programming Language LOC/FP (average) Select
Assembly Language 320
C 128
COBOL 105
Fortran 105
Pascal 90
Ada 70
Object-Oriented Languages 50
Fourth Generation Languages (4GLs) 20
Code Generators 15
Spreadsheets 6
Graphical Languages (icons) 4
Table 2.4 Language Selection

LOC/FP = 50
Software LOC Effort Rs Paper work Errors Defects People
Project Approx
Booking of 23000 4.00 92000 300 500 50 1

rooms
HGCE(IT) 17
2.4.2 COST ANALYSIS

Error per person= total error/total people = 50/1 = 50
LOC per person= total LOC/total people = 92000/1 = 92000
0.5 rupee per paper of documentation = total Rs. = 250
Total cost of project (in rupees) = sum of Rs = 92000
Other expense = 27000
Total project cost = 92000+27000 = 1,19,000
HGCE(IT) 18
Project ID : 34347 System Requirement Study
System
Requirement Study
3.1 USER CHARACTERISTICS
3.2 HARDWARE AND SOFTWARE SPECIFICATION
3.3 CONSTRAINTS
HGCE(IT)
3.1 USER CHARACTERISTICS:

It is mandatory that the user of any application should be very well aware of how to use
the application or their user interface of the application should be such that the user can easily get
hands on it. The user have the knowledge about using the system and the system is made according
to their convenience. User must have the clear definitions what he is supposed to necessitate from
the system. In this system, there are three types of users,
1. Admin
2. Employee
3. Hotel Manager
4. Guest User
1. Admin:
• He is the key person for controlling the whole system. He will give appropriate
permissions to the users for performing a specific task. He will cover areas such as
database, security and integration.
• He can add, update and delete the record of hotels and conference rooms. He can
do all kind of alteration in a database. He can also block user.
• He provides authority to respective person. He has authority to add different
conference rooms.
• He will provide permission to company to access rooms information.
2. Employee:
• He can search conference rooms for business meeting purpose also he can search
available timings.
• He can update his company details.
• He can book meeting , cancel meeting. Also make payment.
3. Hotel manager:
• He can update hotel details.
• Provide facilities. Receive Payments.
4. Guest User :
• He can check out the rooms.
• He can select the room also he can register to application .
HGCE(IT) 19
3.2 HARDWARE AND SOFTWARE REQUIREMENTS:

• Hardware Requirements
- Android Device
- 512 MB RAM
- 100MB disk Space
- 4.4 KitKat or higher version
System Development Environment
PC/laptop Configuration
- Windows 8.1
- 4/8 GB RAM
- 500GB/1TB Hard Disk
• Software Configuration
- Android Studio
- Android SDK
- Version 2.1.1. or later
- Support repositories
- Virtual Emulator
- GenY motion
3.3 CONSTRAINTS:
• This system work with the hardware defined or higher.

• This system can work with Android KitKat 4.4 or higher.
• This system can work with Firebase.
• This system can work with Internet connection only.
HGCE(IT) 20
Project ID : 34347 System Analysis
System Analysis
4.1 STUDY OF CURRENT SYSTEM

4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM
4.3 REQUIREMENTS OF NEW SYSTEM
4.4 FEASIABILITY STUDY
4.5 REQUIREMENTS VALIDATION
4.6 FUNCTIONS OF SYSTEM
4.7 DATA MODELING
4.8 FUNCTIONAL AND BEHAVIOUR MODELING
4.9 MAIN MODULES OF NEW SYSTEM
4.10 SELECTION OF HARDWARE & SOFTWARE
JUSTIFICATION
HGCE(IT)
4.1 STUDY OF CURRENT SYSTEM :

After analyzing current system I realized that there are many applications which provides
room booking system.
There are applications which are for particular one hotel , but not for multiple hotels. So in
this application you can get multiple options for booking.
Also there are applications available for particular limited rooms but not for all hotels of
city so this app will cover all these points.
But the important part of my application is to provide conference rooms which provides
facilities as per requirements also gives filtrations for price and facilities.
4.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM:

• Totally Time consuming process
• Information is not accurate
• Not available for all conference rooms
• Not providing exact timings
4.3 REQUIREMENTS OF NEW SYSTEM

Complex to find out perfect conference rooms around you. So by using this application
you can get a good conference room near you.
New system provides you an interactive way to manage your business meetings. Easy way
to find out conference rooms as per your choice.
This system also provides filtration by which you can filter the conference rooms as per
your requirements.
• Advantages of Proposed System :-
- No external software required.
- No requirement for expensive hardware.
- No technical knowledge required to manage data.
- As this is an application, one can access from anywhere.
- Information will be updated and in proper manner.
- Time saving process.
HGCE(IT) 21
- Attractive and user friendly User interface (UI).

- One can book room fast in proper manner.
- Members of site will be verified so no privacy concern and no worry about data
security.
- New technology can be implemented in future.
- New facilities can be added in future.
4.4 FEASIBILITY STUDY:
A feasibility study is undertaken to determine the possibility or probability of either
improving the existing system or developing a completely new system.
It helps to obtain an overview of the problem and to get rough assessment of whether
feasible solution exists.
• Need for Feasibility Study :-
The feasibility study is needed to
(1) Answer the question whether a new system is to be installed or not?
(2) Determine the potential of the existing system.
(3) Improve the existing system.
(4) Know what should be embedded in the new system.
(5) Define the problems and objective involved in a project.
(6) Avoid costly repairs at a later stage when the system is implemented.
(7) Avoid crash implementation of a new system.
(8) Avoid the ‘Hardware Approach’ i.e. getting a computer first and then deciding
how to use it.
• Technical Feasibility: -
Technical feasibility corresponds to determination of whether it is technically
feasible to develop the software.
- Necessary technology exists to do what is suggested and required by the
organization.
- The hardware needed to develop and implement the system is adequate.
- The software guarantees accuracy, reliability and ease of access and data
security.
HGCE(IT) 22
• Economic Feasibility: -
A system that can be developed and that will be used if installed must still be a
good investment for the organization. Financial benefits must equal or exceed the costs.
The financial and economic issues raised are as under:
- No extra cost is incurred for developing the system.
- No extra cost for the modification or addition of software and hardware will
require in case of future expansion of the current system.
- The company will be at profit if they implement this system because of the
cost of implementation is nominal as compared to the profit they will be
earning in terms of efficiency.
• Operational Feasibility: -
Operational feasibility focuses on whether the system will work when it is
developed and installed. Operationally the system is feasible because:
- There is sufficient support for the project from management and user. The
system is well liked and used to the extent that persons will not be able to
see reasons for change. The proposed system will not cost any harm to the
existing system and its users.
4.5 REQUIREMENTS VALIDATION:

• User Id and Password validation that is compulsory to enter within system.
• Phone no. Must be Numeric and length is of maximum10 Digit.
• Name must be character not in Digit.
• Email ID must enter properly.
• Can’t enter value more than its size.
• Most of field are mandatory and user must enter its value.
HGCE(IT) 23
4.6 FUNCTIONS OF SYSTEM:

USE CASE :
Fig 4.1 Employee Use Case
HGCE(IT) 24
Fig 4.2 Use case of Hotel Manager
HGCE(IT) 25
Fig 4.3 Use Case of Admin
HGCE(IT) 26
4.7 DATA MODELING:

4.7.1 E-R DIAGRAM
Fig 4.4 E-R Diagram
HGCE(IT) 27
4.7.2 SEQUENCE DIAGRAM :
Fig 4.5 Sequence Diagram of Admin
HGCE(IT) 28
Fig 4.6 Sequence Diagram Of Hotel Manager
HGCE(IT) 29
Fig 4.7 Sequence Diagram Of Employee
HGCE(IT) 30
4.7.3 FLOW CHART :
Fig 4.8 Flow Chart Of Admin
HGCE(IT) 31
Fig 4.9 Flow Chart Of Employee
HGCE(IT) 32
Fig 4.10 Flow Chart Of Hotel Manager

4.7.4 DATA DICTIONARY
Data Dictionary is an important part of a project or system which contains all definition of
elements in the system. In Data Dictionary you will find a list of all elements composing the data
flowing through a system. The major elements of a system:
(1) Data Flow
(2) Data Store
(3) Processes
HGCE(IT) 33
A data dictionary is a catalog of the elements in a system. As the name suggests, these
elements are structured around data in a way to meet the user and the organization requirements.
A data dictionary is a list of elements that composes all the data flow process through a system.
It stores details and description of the data flows, data storing and processes. If analyst
wants to know by what other names is a table or a data item referenced in a system, or where it is
being used the answers are properly developed in data dictionary.
The dictionary is developed during data flow analysis and assists the analysts involved in
determining system requirements. However its content is used during system design as well.
Why is Data Dictionary important?
• To manage the details in large system.
• To communicate a common meaning for all system elements.
• To facilitate analysis in order to determine where the changes are to be made.
• To locate errors and omissions in the system.
DATABASE DESIGN
Fig 4.11 Data Dictionary
HGCE(IT) 34
Fig 4.12 Booking Data Dictionary
Fig 4.13 Employee Data Dictionary
Fig 4.14 Payment Data Dictionary

HGCE(IT) 35
Fig 4.15 Hotel Data Dictionary
Fig 4.16 Feedback Data Dictionary
Fig 4.17 Help Data Dictionary

HGCE(IT) 36
4.8 FUNCTIONAL AND BEHAVIOUR MODELING

4.8.1 CONTEXT LEVEL DIAGRAM :
Fig 4.18 DFD level-0
HGCE(IT) 37
Fig 4.19 DFD level-1 Admin
4.8.2 PROCESS SPECIFICATION

Process 1:
• Process Name: Login
• Description: This process is use only by Admin.
• Input: id and password
• Preconditions: must be valid user id and password.
• Output: Access to the application.
HGCE(IT) 38
Process 2:
• Process Name: Manage Booking
• Description: This process is used by only Admin.
• Input: Booking tInformation.
• Output: Booked room.
Process 3:
• Process Name: Manage Record
• Description: This process is used by Admin.
• Input: Record Information
• Output: Get Information about Employees and Rooms.
Process 4:
• Process Name: Manage Profile
• Input: Requests for change ID/Password
• Output: Confirmation of changes .
Process 5:
• Process Name: Manage Payment
• Input: Analyze payment
• Output: Payment Details.
HGCE(IT) 39
Fig 4.20 DFD level-1 Employee

Process 1:
• Process Name: Register
• Description: Registration Process
• Input: Employee Details
• Output: User gets access
HGCE(IT) 40
Process 2:
• Description: Login process
Process 3:
• Process Name: Check List of Rooms
• Description: This process is use only by users.
• Input: Search Room As per Requirement
• Output: Result of search.
Process 4:
• Process Name: Manage Room Booking
• Description: This process is used by only Employee User.
• Input: Select and book Room.
• Output: Confirmation of Booked room.
Process 5:
• Description: This process is used by Employee User.
• Input: Requests for change ID/Password also Info About Company
• Output: Confirmation of changes.
Process 6:
• Description: This process is used by Employee User.
• Input: Make payment
• Output: Payment receipt.
HGCE(IT) 41
Fig 4.21 DFD level-1 Hotel Manager

Process 1:
• Process Name: Register
• Description: Registration Process
• Input: Manager Details
• Output: User gets access
HGCE(IT) 42
Process 2:
• Description: Login process
Process 3:
• Process Name: Manage Room Booking
• Description: This process is used by only Hotel Manager User.
• Input: Accept room Booking
• Output: Confirmation of Booked room.
Process 4:
• Process Name: Manage Offers
• Description: This process is use only by Hotel Manager users.
• Input: Add/Update/Delete offers
• Output: Result of Changes.
Process 5:
• Description: This process is used by Hotel Manager User.
• Input: Requests for change ID/Password also Info About Hotel Room
• Output: Confirmation of changes.
Process 6:
• Description: This process is used by Hotel Manager User.
• Input: Accept payment
• Output: Payment receipt.
HGCE(IT) 43
4.9 MAIN MODULES OF NEW SYSTEM

• Easy searching Rooms: You can search any kind of available room near you.
• Easy to Filter room : You can choose as per your requirement and as per facilities.
• Easy online Room Booking : This module is the fastest and easiest way of meeting
booking. A user can book any kind of conference room as per requirements.
4.10 SELECTION OF HARDWARE & SOFTWARE

4.10.1 Hardware Justification
• Android Mobile: Android Mobile with higher version of Android 5.0.
• RAM: Required minimum 2GB ram for supporting and running the application.
• Processor: Minimum required processor 1.7 GHz Snapdragon 520.
HGCE(IT) 44
Project ID : 34347 System Design
System Design
5.1 DATABASE DESIGN/DATA STRUCTURE DESIGN

5.2 SYSTEM PROCEDURE DESIGN
5.3 INPUT/OUTPUT AND INTERFACE DESIGN
HGCE(IT)
5.1 DATABASE DESIGN/DATA STRUCTURE DESIGN

5.1.1 MAPPING OBJECTS/CLASSES TO TABLES
Design Approach
All Software design methods share the same goal - to transform a set of data processing
requirements into a computer program. The major objectives of the software design process are to
document in sufficient detail the software design based on the software requirements and
traceability to specifications.
The output is complete, consistent, correct, testable and understandable information that
can be used as input for code generation. The Functional Specifications and the system
specifications are used as inputs for this process. The process ends when all the objectives of the
software requirement document are met.
System Design
System Design is an important phase in which quality is fostered in software development
design is the process that actually transforms the requirements in to a finished software product
(or) system.
Design is the process of translating the requirement prepared during system study into
design. The system design phase employs a variety of tools such as class diagram and so on.
System design is primarily a synthesis function. In designing a new system, one must have
a clear picture of what is required and what must be done in order to achieve the requirement. Web
pages are designed in such a way that it should be easily understandable for a layman.
Output Design
The output is the most important direct source of information to the user. Intelligent output
Design will improve the systems relationship with the user and also helps in decision making, once
the output requirement is determined, the system designer can decide, what to include in the system
and how to structure it, so that the required output can be produced.
Hence the output requirements are to be determined before going to actual system design.
Output design is based on the following factors.
• Layout for the presentation of outputs.
• A simple and neat format is preferred rather than complex form of output.
HGCE(IT)
45
Input Design
Input Design is a part of overall system design which requires very care attention. If an
error occurs in the input data then the result of that error may lead to unwanted problems. Errors
committed by users can be controlled by a proper input design.
Normally the data will be keyed into the system through the standard input device like
keyboard. In such case, a validation program should be there to check the validity of the data.
Database Design
Database design is the most critical part of the design phase. An elegantly designed, well-
defined database can play as a strong foundation for the whole system. Database design transforms
the information domain model created during the analysis into the data structures that will be
required to implement the software system.
Conceptual Level
Conceptual level describes the major data objects and relationship between them. This level
uses symbols from a modeling method called Entity Relationship Analysis. Entity Relationship
Analysis uses three major abstractions to describe data.
They are as follows,
• Entities: Distinct objects of the system an entity is a conceptual representation of
an object.
• Attributes: Properties of the entities.
• Relationship: Meaningful interaction between entities. Relationship between
entities makes up the database structure.
• Three types of relationship exist among entities. They are,
• One-to-One: Association between two entities.
• One-to-Many: Association between one entity with two or more entities.
• Many-to-One: Association between two or more entities in both directions.
Detailed design
The database used here is designed using Fire Base. It has very advanced security features
which are very essential while storing the data.
HGCE(IT)
46
Normalization
First Normal form
The tables are in 1NF if every value of the table, every tuple contains exactly one
value for each attribute. By the definition above all the tables are in 1NF as each and every
attribute contains only one value.
Second Normal form
The tables are in 2NF if every non-key attribute is irreducibly dependent on the
primary key. By the definition above all the tables in the database are in 2NF. All the other
attributes other than the primary key are not dependent on each other except on the primary
key.
Third Normal form
The tables are in 3NF if and only if it is in 2NF and every non key attribute is non
transitively dependent on the primary key. It means there are no mutual dependencies
between the attributes. By the definition above all the tables are in 3NF. There is no
dependency between the attributes if one is to be changed it is not necessary to change the
value of the other attribute and there is primary key in the table on which the attributes
depend.
Forth Normal form
When Attributes in a relation have multi valued dependency, further normalization
to 4NF is required. It means in 4NF a attribute has no more than one independent multi
valued multi valued dependency or one independent multi valued dependency with
functional dependency.
HGCE(IT)
47
5.2 SYSTEM PROCEDURAL DESIGN

5.2.1 DESIGNING PSEUDO CODE OR ALGORITHM FOR METHOD OR
OPERATIONS
Admin
• Open the Application
• Admin enters his/her id and password.
• Contents are submitted to the server machine.
• If User is Admin then
• Open the home page.
• Select the appropriate module.
• Opens any module.
• View/Access the record.
If User wants to view some details
• Select the desired detail
• View the details
Else
• No change.
• Logout
Guest user
• Open Application
• Check out the process of Application
Select the room
• Redirect page to login page
Else
• No change.
• Logout.
HGCE(IT)
48
Employee user
• Open the application.
• Employee enter his/her user ID & password
If User want to book the room
• Select the Room
• Check required facilities
Else
• No change.
• Logout.
Hotel Manager user
• Open Application.
• Hotel Manager enter user ID & password
If User wants to view some Details of his/her task
• Select the desired detail
If User want to update profile
• Add Details
• Update Details
• Delete Details
Else
• No change.
• Logout.
HGCE(IT)
49
5.2.2 ACTIVITY DESIGN
Fig 5.1 Activity Diagram Of Admin
HGCE(IT)
50
Fig 5.2 Activity Diagram Of Employee
HGCE(IT)
51
Fig 5.3 Activity Diagram Of Manager
HGCE(IT)
52
5.3 INPUT/OUTPUT AND INTERFACE DESIGN

REGISTRATION PAGE:
Fig 5.4 Registration Page
This is the REGISTRATION page of the application. By this page the user can
register into application. This page contains basic information of the user. There are two
types of user in this page employee and manager. Manager have hotel information and
employee having company information.
HGCE(IT)
53
LOGIN :
Fig 5.5 Login Page
This is LOGIN page of this application. In this page User have to insert user ID and
password. If the password is incorrect user can not able to access the application. If user
forget password then he/she also can redirect to forget password page and get the password.
If user is not registered then he/she will redirected to sign up page.
HGCE(IT)
54
FORGET PASSWORD PAGE :
Fig 5.6 Forget Password Page
This is FORGET PASSWORD page which is used when any user forget his/her
password. At that time he/she can enter his/her password any get the reset link on registered
email ID.
HGCE(IT)
55
Project ID : 34347 Implementation Planning and Details
Implementation
Planning and Details
6.1 IMPLEMENTATION ENVIRONMENT

6.2 PROGRAM MODULES AND SPECIFICATION
6.3 SECURITY FEATURES
6.4 CODING STANDARDS
6.5 SAMPLE CODE
HGCE(IT)
6. IMPLEMENTATION PLANNING AND DETAILS

6.1 IMPLEMENTATION ENVIRONMENT
6.1.1 SINGLE VS. MULTI USER
As the “Meet-Buss” going to be developed as an Application, at the time of implementation
it should be kept in mind that application will be used concurrently. So, the development
approach would remain for the concurrent use.
6.1.2 GUI VS. NON-GUI
The application is completely ONLINE GUI. This is because now a days employees facing
lots of issues for finding out the particular hotel/conference room as per requirements for
business meetings. So by using this application user can easily find and book the room. Thus
, application is user friendly.
6.2 PROGRAM/MODULES SPECIFICATION
There are many modules associated with the system and they are as follows:
Admin:
He is the key person for controlling the whole application. He will give appropriate
permissions to the users for performing a specific task. He will cover areas such as database,
security and integration.
He can add, update and delete the record of hotels, bookings and users. He can do
all kind of alteration in a database. He can also block users.
User:
He can insert update or delete their data. He can book the rooms and check booking
history. He can cancel booking.
6.3 SECURITY FEATURES
The security feature is the main important feature of the application, it is random
code generation of particular hotels which is created by admin. No Spam or fake users are
allowed to this application. User cannot let book the room unless it cannot register and its
correct id and password. If the user is blocked he cannot login to the application. All the
data entry must be according to required pattern. If the email_id is already existing he cannot
use the same email_id. password can be reset only via registered email only.
HGCE(IT) 56
6.4 CODING STANDARDS

The coding standard is the well-defined and standard style of coding. With the help
of the coding standards any person can go into any code and figure out what’s going on and
new people can get up to speed quickly. Some coding standard ways of doing several things
such as the way variables are to be named, the code is to be laid out, the comments are to
be described, the work of function are to be carried out. This section describes the coding
standards, which we have used in the program. In the context of coding standard, the tag
consists.
6.5 SAMPLE CODE
Login.xml page :
<?xml version = "1.0" encoding = "utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
xmlns:app="http://schemas.android.com/apk/res-auto"
android:orientation="vertical"
tools:context=".Activity.Login_Page"
android:padding="12dp"
android:weightSum="10"
android:background="@drawable/back_ground">
<TextView
android:id="@+id/textview"
android:layout_weight="1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="Login"
android:textColor="@color/blue"
android:textSize="35dp"
android:textStyle="bold"
android:layout_gravity="center"/>
<ImageView
android:id="@+id/image"
android:layout_width="60dp"
android:layout_height="40dp"
android:background="@drawable/user"
android:layout_gravity="center"/>
<android.support.design.widget.TextInputLayout
android:id="@+id/edit_txt1"
android:layout_height="wrap_content">
HGCE(IT) 57
<EditText
android:id="@+id/editText"
android:layout_weight="0.5"
android:hint="Email"
android:inputType="textEmailAddress"/>
</android.support.design.widget.TextInputLayout>
<android.support.design.widget.TextInputLayout
android:id="@+id/edit_txt2"
android:layout_height="wrap_content">
<android.support.v7.widget.AppCompatEditText
android:id="@+id/editText2"
android:hint="Enter Password"
android:inputType="textPassword" />
</android.support.design.widget.TextInputLayout>
<CheckBox
android:id="@+id/checkbox"
android:checked="true"
android:text="Keep me logged in" />
<Button
android:id="@+id/button"
android:layout_gravity="center"
android:layout_marginTop="10dp"
android:background="@android:color/holo_blue_dark"
android:text="Login"
android:textColor="@android:color/white"/>
<TextView
android:id="@+id/fgt_pwd"
android:text="Forgot password ?"
android:layout_margin="10dp"
android:textColor="@android:color/holo_blue_dark"/>
<TextView
android:id="@+id/sign_up"
android:text="Sign UP?"
android:textColor="@android:color/holo_blue_dark"/>
</LinearLayout>
HGCE(IT) 58
Login.java page :
login_btn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
if (editText.getText().toString().isEmpty())
{
editText.setError("empty not allowed");
}
else if (editText2.getText().toString().isEmpty())
{
editText2.setError("empty not allowed");
}
else
{
showProgressDialog("Login", "Authenticating...");
mAuth.signInWithEmailAndPassword(editText.getText().toString(),editText2.getText().toSt
ring()).addOnCompleteListener(Login_Page.this, new OnCompleteListener<AuthResult>()
{
@Override
public void onComplete(@NonNull Task<AuthResult> task)
{
if (task.isSuccessful())
{
// Sign in success, update UI with the signed-in user's information
Log.d("login444", "signInWithEmail:success");
cancelProgressDialog();
FirebaseUser user = mAuth.getCurrentUser();
if (page_name != null && page_name.equalsIgnoreCase("next_place"))
{
Intent i = new Intent(Login_Page.this, Book_Page.class);
startActivity(i);
}
else
{
Intent i = new Intent(Login_Page.this, Dashboard_employee.class);
startActivity(i);
}
//finish();
}
else
{
cancelProgressDialog();
// If sign in fails, display a message to the user.
Log.w("login444", "signInWithEmail:failure", task.getException());
Toast.makeText(Login_Page.this, "Authentication failed.",Toast.LENGTH_SHORT).show();
}
}
});
}
}
});
HGCE(IT) 59
Testing
7.1 TESTING PLAN

7.2 TESTING STRATEGIES
7.3 TESTING METHODS
7.4 TEST CASES
HGCE(IT)
7. TESTING
7.1 TESTING PLAN
A test plan is the cornerstone of a successful testing implementation. The testing plan
represents the overall approach to the test. In many ways, the test plan serves as a summary of the
test activities that will be performed. It shows how the tests will be organized, and outlines all of
the tester’s needs that must be met in order to properly carry out the test. The goal of test planning
is to establish the list of tasks that, if performed, will identify all of the requirements that have not
been met in the software. There are many standards that can be used for developing test plans.
Early in the deployment planning phase, the testing effort, and identifies the methodology that
your team will use to conduct tests. It also identifies the hardware, software, and tools required for
testing and the features and functions that will be tested. A well-rounded test plan notes any risk
factors that jeopardize testing and includes a testing schedule. So, we can say that Test Planning
details the activities, dependencies and effort required to conducting the system test.
7.2 TESTING STRATEGIES
The test strategy is a formal description of how a software product will be tested. A test
strategy is developed for all levels of testing, as required. The test team analyses the requirements,
writes the test strategy and reviews the plan with the project team. The test plan may include test
cases, conditions, and the test environment, a list of related tasks, pass/fail criteria and risk
assessment. The purpose of the testing strategy is to define the overall context for the entire testing
process. The process is different depending on the specific characteristics of your solution. In many
respects, this is the most important part of the testing process since all future testing decisions will
be made within the context of the strategy. As a programmer, we have to just do a unit testing
which is a part of White Box testing. Other type of the testing in each phase of the software is done
by testing department. Unit testing begins at the vortex of the spiral and concentrates on each unit
(i.e. component) of the software as implemented in source code.
➢ Unit testing
Unit testing is a software development process in which the smallest testable parts
of an application, called units, are individually and independently scrutinized for proper
operation. Unit testing is often automated but it can also be done manually. Unit testing
involves only those characteristics that are vital to the performance of the unit under test.
HGCE(IT) 60
The unit test verifies that the requirements are being met. The unit testing generally
tests two types of requirements.
➢ User requirements
User requirements typically specify some combination of function, performance,
data, and workflow. A general template for this can be illustrated as: The user typically
thinks in terms of the user interface, clicking on a button that does something, and having
the user interface change as a result. The user also specifies the data, from the presentation
level perspective.
The program implements this workflow by decomposed into a set of functions,
again, often functions familiar to the customer. Unit testing of the customer requirements
therefore consists of several things, each at a different quantization. From bottom up:
• Testing each function
• Testing each process
• Testing the workflow
➢ Implementation requirements
During the design/implementation phase, what’s really going on is that the
programmer is translating the customer requirements to schemas and implementations. The
following is a rough idea of this concept. Unit tests that test implementation requirements
are often different from unit tests that test user requirements.
• Translating between user data presentation to more optimal internal data
presentation.
• Translating functions into objects.
• Translating data store into schemas.
1) White Box Testing
Fig. 7.1 White Box Testing

It is performed to reveal the problems related to the internal structure of the program. This
requires that the tester should have the detailed knowledge about the internal structure of the
HGCE(IT) 61
program. A common goal of white-box testing is to ensure a test exercises covering every path
through a program. A fundamental strength that all white box testing strategies share is that the
entire software implementation is taken in to account during testing, which facilitates error
detection even when the requirement specification is vague or incomplete. The effectiveness or
thoroughness of white-box testing is commonly expressed in terms of test or code coverage
metrics, which measure the fraction of code exercised by test cases.
Control-flow testing, loop testing, and data-flow testing, all maps the corresponding flow
structure of the software into a directed graph. Test cases are carefully selected based on the
criterion that all the nodes or paths are covered or traversed at least once. By doing so we may
discover unnecessary "dead" code - code that is of no use, or never get executed at all, which
cannot be discovered by functional testing.
2) Black-box Testing:
Fig. 7.2 Black Box Testing

The black-box approach is a testing method in which test data are derived from the
specified functional requirements without regard to the final program structure. It is also termed
data driven, input/output driven or requirements-based testing. Because only the functionality of
the software module is of concern, black-box testing also mainly refers to functional testing – a
testing method emphasized on executing the functions and examination of their input and output
data. The tester treats the software under test as a black box -- only the inputs, outputs and
specification are visible, and the functionality is determined by observing the outputs to
corresponding inputs. In testing, various inputs are exercised and the outputs are compared against
specification to validate the correctness. All test cases are derived from the specification. No
implementation details of the code are considered.
It is obvious that the more we have covered in the input space, the more problems we will
find and therefore we will be more confident about the quality of the software. Ideally, we would
be tempted to exhaustively test the input space. But exhaustively testing the combinations of valid
HGCE(IT) 62
inputs will be impossible for most of the programs, let alone considering invalid inputs, timing,
sequence, and resource variables. Combinatorial explosion is the major roadblock in functional
testing. To make things worse, we can never be sure whether the specification is either correct or
complete. Due to limitations of the language used in the specifications (usually natural language),
ambiguity is often inevitable. Even if we use some type of formal or restricted language, we may
still fail to write down all the possible cases in the specification.
The research in black box testing mainly focuses on how to maximize the effectiveness of
testing with minimum cost, usually the number of test cases. Domain testing partitions the input
domain into regions and considers the input values in each domain an equivalent class. Domains
can be exhaustively tested and covered by selecting a representative value(s) in each domain.
Boundary values are of special interest. Experience shows that test cases that explore boundary
conditions have a higher payoff than test cases that do not. The difficulties with domain testing are
that incorrect domain definitions in the specification cannot be efficiently discovered. This testing
was done with dummy data created by us.
• Specifications: - In this type of testing first of all we have to compare the requirement
specification along with existing system to see whether actual requirement is satisfied.
• Navigation: - secondly, how system works and how you will navigate the entire the system.
i.e. System navigation flow that should be clear.
• Field size & validity: - It determines size of the field and any validation like whether field
is mandatory or not. Some of the fields have alphabets only such as name field. Here only
alphabets must be allowed.
• Add, Modify, delete (Storage): - After completion of all the types of above mentioned
testing types, carry out the testing for add, modify, Delete functionality of system. Here
you have to test whether you can add the data in database modify the data in database and
delete the data from the database.
• Black-box testing attempts to find errors in the following Categories:
• Incorrect or missing function.
• Interface errors.
• Errors in fetching external data.
• Behavior or performance errors.
• Initialization and termination error.
HGCE(IT) 63
7.3 TESTING METHODS

Involve execution and implementation of the software with test data and examining
the outputs of the software and its operational behavior to check that it is performing as
required.
7.3.1 Defect Testing
Intended to find inconsistencies between a program and its specification.
These inconsistencies are usually due to program faults or defects.
7.4 TEST CASES
Admin side:
Purpose Required Input Expected Result
Login into the Valid username and password Identify the user and give the
Firebase rights according to the user
Adding new All the required fields must be New record is inserted in
record in table entered database
Editing tables Just select the record which is Updates the record in table
content supposed to be updated
Table 7.1 Admin Activities
User side:
Purpose Required Input Expected Result
Registration in to the Valid username, user_id, Identify the user details
application password
Login into the Valid username and Identify the user and return
application password homepage according to user
Check List of Rooms Search as per requirement Filtered list of rooms as per
requirement
Book Room Enter number of person , Room booked
date and time
Make Payment Bank details - Valid Payment successfully done
Invalid Bank Details Payment Failed
Table 7.2 User Activities
HGCE(IT) 64
Project ID : 34347 Screen shots and User Manual
Screen shots
and User Manual
HGCE(IT)
8.0 SCREEN SHOTS AND USER MANUALS
ADMIN AUTHENTICATION PAGE :
Fig 8.1 Admin Authentication Page
This is ADMIN AUTHENTICATION page which is used by Admin only. He can add or
delete user from here. He can manage users and provide authentication to them.
HGCE(IT) 65
ADMIN DATA MANAGE PAGE :
Fig 8.2 Admin Data Manage Page
This is ADMIN DATA MANAGE page which is used by Admin only. He can add or delete
DATA from here. He can manage DATA.
HGCE(IT) 66
FIREBASE DATABASE PAGE :
Fig 8.3 Admin Data Manage Page
This is ADMIN DATA MANAGE page which is used by Admin only. He can add or delete
user from here. He can manage users and provide authentication to them.
HGCE(IT) 67
PAYMENT DETAILS PAGE :
Fig 8.4 Admin Side Payment Page
This is ADMIN SIDE PAYMENT page which is used by Admin only. He can manage
payment from here and can able to check payment history.
HGCE(IT) 68
DASHBOARD PAGE:
Fig 8.5 Dashboard Page
This is the DASHBOARD for this application. This Page will contain Information
about basic options and modules of the main project. By this the user can access the
application.
HGCE(IT) 69
LIST OF ROOMS PAGE :
Fig 8.6 List Of Room Page
This page is about list of rooms . In this page we can see the list of rooms which
are available or unavailable. Also we can see the rating of that room.
HGCE(IT) 70
FILTER DIALOG PAGE :
Fig 8.7 Filter Page
This is FILTER page which contains filters like ratings , price and facilities. By
choosing this we can filter out rooms as per requirement. This also contains filter of area.
Using this filter you can find out the nearly available hotel/conference room by selecting
particular area.
HGCE(IT) 71
PLACES(ROOM) PAGE :
Fig 8.8 Room Details Page
This is ROOM page which contain information of rooms. In this page the page
contain pictures of room , ratings of that room/hotel , availability of that room , description
of that room , contact number , email ID , also fax ID.
HGCE(IT) 72
REGISTRATION PAGE:
Fig 8.9 Registration Page
This is the REGISTRATION page of the application. By this page the user can
register into application. This page contains basic information of the user. There are two
types of user in this page employee and manager. Manager have hotel information and
employee having company information.
HGCE(IT) 73
LOGIN :
Fig 8.10 Login Page
This is LOGIN page of this application. In this page User have to insert user ID and
password. If the password is incorrect user can not able to access the application. If user
forget password then he/she also can redirect to forget password page and get the password.
If user is not registered then he/she will redirected to sign up page.
HGCE(IT) 74
email ID.
HGCE(IT) 75
email ID.
HGCE(IT) 76
BOOKING PAGE :
Fig 8.13 Booking Page
This is BOOKING page which contains information of booking (i.e. date of

booking , starting time , end time And also Number of persons.)
HGCE(IT) 77
PAYMENT PAGE :
Fig 8.14 Payment Page
This is PAYMENT page which helps user to make payment of conference rooms.
HGCE(IT) 78
PAYMENT PAGE :
Fig 8.15 Payment Page
This is PAYMENT page shows that you have successfully done your payment.
HGCE(IT) 79
CONFIRMATION MAIL PAGE :
Fig 8.16 Confirmation Mail Page
This is CONFIRMATION MAIL page which contain information of booking. It

contains all the details of user's booking (i.e. booking time , booking date , hotel name ,
hotel contact number etc.)
HGCE(IT) 80
BOOKING HISTORY PAGE :
Fig 8.17 Booking History Page
This is BOOKING HISTORY page which contain information of all booking. In

this page the page contain time and date of booking , also contains other details about
booking.
HGCE(IT) 81
FACILITIES PAGE :
Fig 8.18 Facilities Page
This is FACILITIES page which contain information of all facilities provided by

hotels. In this page the page contains all detailed information of facilities.
HGCE(IT) 82
ACCOUNT SETTINGS PAGE :
Fig 8.19 Account Settings Page
This is ACCOUNT SETTINGS page which contain information of user. User can
able to manage his/her profile. He/she can update profile, change password etc.
HGCE(IT) 83
HELP PAGE :
Fig 8.20 Help Page
This is HELP page which basically for users who are facing any issues. So by
submitting their problem here they can contact with the exert and get the solution.
HGCE(IT) 84
FAQ PAGE :
Fig 8.21 FAQ Page
This is FAQ page which contain frequently asked questions by users and solution
of that. By which if any user is facing issue from that then can easily get the solution.
HGCE(IT) 85
FEEDBACK PAGE :
Fig 8.22 Feedback Page
This is FEEDBACK page which contains a form for giving feedback by user about
the application.
HGCE(IT) 86
CONTACT US PAGE :
Fig 8.23 Contact Us Page
This is CONTACT US page which is used for contacting to the admin by user. By
using this page any user can contact with admin.
HGCE(IT) 87
TERMS & CONDITIONS PAGE :
Fig 8.24 Terms & Condition Page
This is TERMS & CONDITION page which contain information of terms and
conditions provided by the hotels/conference rooms.
HGCE(IT) 88
Project ID : 34347 Limitations and Future Enhancement
Limitations
And
Future Enhancement
9.1 LIMITATIONS AND FUTURE ENHANCEMENT
HGCE(IT)
Project ID : 34347 Limitations and Future Enhancement
9.1 Limitations:
• This application can not work on android devices having less android versions from
KitKat 4.1.
• This application cannot work without internet connection.
• Sometimes implementation on large field and data is challenging.
• It cannot work on IOS and Microsoft devices.
• At present situation refund generation of advanced payment is difficult and
complicated.
• Sometimes there would be multiple entries of booking at the same time so it is
challenging to give priority to them.
9.2 Future Enhancement:
• In future we can try to solve above mentioned problems.

• For now, this application is limited for small scale i.e. Ahmedabad. But in future we
can develop this application for large scale i.e. Country level.
• We can also add full online payment.
• I will complete remaining pages of the application which are necessary.
• Admin panel of the application must be completed so I will also work on it.
• There are some validations which are required which should be improved.
• Database connectivity of the pages of the application.
• New features as per technology have to be added into application.
• Testing of the application is also required before launching this application.
• Updates as per requirements.
HGCE(IT) 89
Project ID : 34347 Conclusion
Conclusion
HGCE(IT)
Project ID : 34347 Conclusion
10. Conclusion:
Basically, in this application “MEET-BUSS” any company can book the conference hall
for meeting purpose. Here it will provide multiple choice for meeting of the hotel rooms or any
conference hall which is registered by their owner.
If any company want to book any conference hall/room then he/she can register and find
the places as per their requirements. For security purpose there will some token amount as advanced
payment.
For multiple requests at the same time of booking there will be automatic system that the
data base will automatically solve that situation and it will allocate only one company for that
particular time slot. If any hall is already booked and someone want that hall then it will show the
pop-up that that particular hall is already booked.
Any company who is regularly arranging meeting at the same hotel/hall then the hotel gives
first priority to that company. The hotel manager can also provide some offer to them who are
regularly arranging the meeting but this all depends upon that hotel/hall manager. Revenue
generation from this application is via advertisement.
HGCE(IT) 90
Project ID : 34347 Appendix
Appendix
HGCE(IT)
PMMS STATUS
Fig. 11.1 PMMS Status
HGCE(IT) 91
PERIODIC PROGRESS REPORT (PPR) :
Fig. 11.2 PPR Status
PATENT SEARCH AND ANALYSIS REPORT (PSAR)
Fig. 11.3 PSAR Status
HGCE(IT) 92
DESIGN ENGINEERING SHEETS :
Fig. 11.4 Design Engineering Sheets Status
AEIOU :
Fig. 11.5 AEIOU Sheet
HGCE(IT) 93
EMPATHY CANVAS :
Fig. 11.6 Empathy Canvas Sheet
HGCE(IT) 94
IDEATION CANVAS :
Fig. 11.7 Ideation Canvas Sheet
PRODUCT DEVELOPMENT CANVAS :
Fig. 11.8 Product Development Sheet
HGCE(IT) 95
BUSINESS MODEL CANVAS :
Fig. 11.9 Business Model Canvas
Fig. 11.10 Business Model Canvas Sheet

HGCE(IT) 96
BUSINESS MODEL CANVAS :
Fig. 11.11 Patent Drafting Exercise
HGCE(IT) 97
3/18/2019 PDE Details
College : HASMUKH GOSWAMI COLLEGE OF ENGINEERING, VAHELAL

Department : Information Technology
Discipline : BE
Semester : Semester 8
Project Name : Meet-Buss
Team ID : 34347
Form 1 – APPLICATION FOR GRANT OF PATENT

Applicants :
Sr.
Name Nationality Address Mobile No. Email Id
No
Information Technology
,
HASMUKH
Shah Urviben GOSWAMI COLLEGE
1 Indian 9157802202 urvishah2227@gmail.com
Rajeshkumar OF ENGINEERING,
VAHELAL ,
Gujarat Technologycal
University.
Inventors :
Sr.
Name Nationality Address Mobile No. Email Id
No
Information
Technology ,
HASMUKH
Shah Urviben GOSWAMI COLLEGE
1 Indian 9157802202 urvishah2227@gmail.com
Rajeshkumar OF ENGINEERING,
VAHELAL ,
Gujarat Technologycal
University.
I/We, the applicant(s) hereby declare(s) that:
Following are the attachments with the applications :
Form 2 - PROVISIONAL/COMPLETE SPECIFICATION

1 . Title of the project/invention :
Meet-Buss
2. Preamble to the description :
Provisional
3. Description
a) Field of Project / Invention / Application :
This invention relates to Finding the place for meeting which is as per the requirements is quite difficult on local
websites. It is also a time-consuming process to find out a perfect place. So, this idea is about meeting booking.
By which company manager can find out a particular place. Basically, in this application any company can book
the conference hall for meeting purpose.
b) Prior Art / Background of the Project / Invention :
Now a days everyone is going online for each work. Each people always used to find a short way to complete
their work. So basically, in this application any company can book the conference hall for meeting purpose.
It is tough to find out relevant options for booking conference hall. Normally if we want to book any place we
have to search it and find out relevant place if we do not satisfy then again search for it. Here we are providing
1/3
multiple choice for meeting of the hotel rooms or any conference hall which is registered by their owner.
So by using this application easily anyone can find out a perfect choice as per requirements. Also it is very good
opportunity for hotels and conference room owners to advertise their facilities.
The major purpose of this document will be to describe in brief about the Meet-Buss. All the processes which are
included in hotels and company will be described in this document.
The main characteristic of the system regarding its input and output process and all the facilities which will be
included in the operation and is described in this document. The basic idea of how the work is going in this
project will described in this document.
A meeting room booking system can give venue owners a more effective and more profitable way of managing
their spaces. Even managing a single space can be difficult if it is in high demand, and if a venue owner relies on
analog methods, it is only a matter of time before the space is double booked or a client uses the space without
paying.
c) Summary of the Project / Invention :
The major purpose of this document will be to describe in brief about the Meet-Buss. All the processes which are
included in hotels and company will be described in this document. The main characteristic of the system
regarding its input and output process and all the facilities which will be included in the operation and is
described in this document. The basic idea of how the work is going in this project will described in this
document.
Admin is responsible for all the management of data. Hotel and Company do registration itself. Only registered
persons can access the booking part of the application and only authorized members can generate report and got
notification. Guest user can see options about available rooms but can not access booking of that room without
register.
d) Objects of Project / Invention :
1. This application will reduce complex work like finding places as per requirements.
2. If this project is implemented successfully then each company must join to this
3. Integrate with any existing online application.
4. One can make dynamically changes.
5. Employees and managers can generate notification.
6. In future new technology can be applied.
7. It can be used for all the companies and hotels so they can take advantage of it
8. Main objective of the this is to reduce struggle and save everyone’s valuable time.
9. User interface would be user friendly so operator can easily operate system.
e) Drawings :
f) Description of Project / Invention : (full detail of project) :

Finding the place for meeting which is as per the requirements is quite difficult on local websites. It is also a
time-consuming process to find out a perfect place. So, this idea is about meeting booking. By which company
manager can find out a particular place. Basically, in this application any company can book the conference hall
for meeting purpose. Here it will provide multiple choice for meeting of the hotel rooms or any conference hall
which is registered by their owner. There are mainly three types of registration/login i.e. company registration,
conference hall/hotel manager registration and guest registration. The places for meeting are registered by their
owners. If any company want to book any hall/room then he/she can register and find the places as per their
requirements. The places are filtered by their price and facilities. Hotel manager can manage all the new updates
which are newly available and attract users. So this application is beneficial to hotels too.
g) Examples :
h) Claims (Not required for Provisional Application) / Unique Features of Project
This application provide a real time application that means it will respond as per your requirements. So by sing
this you can get the place which ever you want. Meeting rooms booking system can give venue of owner’s place
a more effectively and more profitable way of managing their spaces. Even managing a single space can be
difficult if it is in high demand. By this you can also get if the place is available or not and also get the ratings of
that particular room.
For now it is only for Ahmadabad so in future if this project will get successful then we can develop it on the
large base (i.e. Gujarat ).
4. Claims
5. Date and signature
2/3
6. Abstract of the project / invention :

Finding the place for meeting which is as per the requirements is quite difficult on local websites. It is also a
time-consuming process to find out a perfect place. So, this idea is about meeting booking. By which company
manager can find out a particular place. Basically, in this application any company can book the conference hall
for meeting purpose. Here it will provide multiple choice for meeting of the hotel rooms or any conference hall
which is registered by their owner. There are mainly three types of registration/login i.e. company registration,
conference hall/hotel manager registration and guest registration. The places for meeting are registered by their
owners. If any company want to book any hall/room then he/she can register and find the places as per their
requirements. The places are filtered by their price and facilities. Hotel manager can manage all the new updates
which are newly available and attract users. So this application is beneficial to hotels too.
Form 3 – STATEMENT AND UNDERTAKING UNDER SECTION 8

Name of the applicant(s) : I/We, Shah Urviben Rajeshkumar
Hereby declare :
Name,Address and Nationality of (i) that I/We have not made any application for the same/substantially the same
the joint applicant : victim invention outside India.
(ii) that the rights in the application(s) has/have been assigned to

Name of the Date of Application Status of the Date of Date of
Country Application Number Application Publication Grant
N/A N/A N/A N/A N/A N/A
(iii)That I/We undertake that upto the date of grant of the patent by the
Controller, I/We would keep him informed in writing the details regarding
corresponding applications for patents filed outside India within three months
from the date of filing of such application.
Dated this 18 day of March 2019
To be signed by the applicant or
his authorised registered patent Signature.................
agent :
Name of the Natural Person who
Shah Urviben Rajeshkumar
has signed :
To,
The Controller of Patents,
The Patent Office,
At Mumbai
3/3
Project ID : 34347 References
REFERENCES:
[1] Reference Book : The Complete Reference, Java 2
Author : Herbert Schild
Publisher : TMH
[2] Reference Book : Software engineering- A practitioner’s Approach
Author : Roger S.Pressman
Publisher : McGraw-Hill International
[3] Reference Book : Android Application Development (With Kitkat Support),Black Book
Author : Pradeep Kothari ,KLSI
Publisher : Dreamtech Press
[4] Google Developers Training July 20,2018
[online] https://developers.google.com/training/android
[5] Tutorials Point July 28,2018
[online] https://www.tutorialspoint.com/android
[6] Code Mentor Community August 15,2018
[online]https://www.codementor.io/learn-android-development
[7] Quora.com July 26,2018
[online]https://www.quora.com/top-issues-in-conference-room-booking
[8] Online Conference Room Booking System
[online] https://fischerkerrn.com/products/room-booking
[9] Robin.apk [Robin-meeting room booking] Sept 10,2018
[online]https://play.google.com/store/apps/details?id=com.robin
HGCE(IT) 98

MeetBuss Report

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MeetBuss Report

Hochgeladen von

Copyright:

Verfügbare Formate

MEET - BUSS

Book Your Business Meetings

Urvi Shah (150240116036)

Prof. Sanjay Makwana

DEPARTMENT OF INFORMATION TECHNOLOGY

Hasmukh Goswami College of Engineering, Ahmedabad.

Gujarat Technological University, Ahmedabad

Department of Information Technology

Internal Guide: Head of Dept.:

Prof. Sanjay Makwana Prof. Hitesh Patel

Asst. Professor, IT Dept. Head, IT Dept.

HGCE, Vahelal HGCE, Vahelal

Sign of External Examiner:

This is to certify that, Shah Urviben Rajeshkumar ( Enrolment Number -

Periodic Progress Reports (PPR) Completed

Business Model Canvas (Image) Completed

Business Model Canvas (Report) Completed

Patent Drafting Exercise (PDE) Completed

Final Plagiarism Report Completed

Final Project Report Completed

Signature of Student : _____________ *Signature of Guide : ________________

Company Name : Teksun Microsys Pvt. Ltd.

Words 990 Date March 26,2019

Characters 6277 Exclude Url

Content Checked For Plagiarism

Android: Java, C or C++? - Stack OverﬂowCompare text

Android ArchitectureCompare text

Android Application Penetration Testing - Part 1- Android Pentesting...Compare text

Student name Urvi Shah

We are thankful to Dr. J. K. Ratnadhariya, Principal Of Hasmukh Goswami

Urvi Shah (150240116036)

FIGURE NO FIGURE NAME PAGE NO.

FIGURE NO FIGURE NAME PAGE NO.

LIST OF SYMBOLS AND ABBREVIATIONS

Symbol Name Notation

Use Case Diagram:

Data Flow Diagram:

Entity Relationship Diagram:

Abbreviated Form Expanded Form

SRS Software Requirement Software

DBMS Database Management System

GUI Graphical User Interface

OOP Object Oriented Programming

UML Unified Modeling Language

Department of Information Technology,

Hasmukh Goswami College of Engineering, Vahelal.

1.1 PROJECT SUMMARY

1.1.1 WHAT IS MEETING ROOM BOOKING SYSTEM?

1.4 TECHNOLOGY AND LITERATURE REVIEW

1.1 Project Summary

1.1.1 What is Meeting Room Booking System?

1.4 TECHNOLOGY AND LITERATURE REVIEW

Fig 1.1 Android Architecture

• Resource Manager − Provides access to non-code embedded resources such

2.1 PROJECT MODEL

2.1 PROJECT MODEL:-

Fig 2.1 Iterative Model

The key to successful use of an iterative software development lifecycle is rigorous

2.2 PROJECT PLAN & SCHEDULING:-

19/06/2018 08/08/2018 27/09/2018 16/11/2018 05/01/2019 24/02/2019 15/04/2019

Project definition selection

Select server and softwares

connect static pages

Signature of Student : _ *Signature of Guide : ____