Académique Documents
Professionnel Documents
Culture Documents
discussions, stats, and author profiles for this publication at: https://www.researchgate.net/publication/310122350
CITATIONS READS
0 2,525
2 authors:
All content following this page was uploaded by Bennet Mathew on 14 November 2016.
Report on
Tourism Management System
Authors
Bennet Mathew
Swetha Krishnamurthy Rao
Contents
1 Introduction 1
2 Assumptions 3
2.1 TourUser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Accommodation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 TouristPlace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4 Weather . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.5 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.6 Shopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.7 Transportation . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.8 PhotoAlbum . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.9 Emergency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.10 Restaurant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7 Relational Algebra 11
8 Conclusion 12
9 References 13
1. Introduction
1 Introduction
Nearly everyone goes on a vacation and a Tourism management system would
play a vital role in planning the perfect trip. The tourism management
system allows the user of the system access all the details such as weather,
location, events, etc. The main purpose is to help tourism companies to
manage customer and hotels etc. The system can also be used for both
professional and business trips. The proposed system maintains centralized
repository to make necessary travel arrangements and to retrieve information
easily.
2 Assumptions
There is a total of 10 entities with many attributes and keys. Attributes and
keys defines the entities.[?, ?, ?, ?, ?]
2.1 TourUser
This entity contains UserID, Name and Password where the primary key is
UserID. This acts as a login portal for the usage of this database.
2.2 Accommodation
Accommodation contains AccID, Name, Type, Location, MinCost, MaxCost,
Offer, WebsiteAndCost and PlaceID as foreign key from TouristPlace entity.
2.3 TouristPlace
TouristPlace holds the place where the user wishes to tour. Details such as
Name, Description, Type and PlaceID which is the primary key.
2.4 Weather
A perfect tour can always be ruined by bad weather. Weather entity holds
the MinTemp, MaxTemp and a WebLink for further insights. WeatherID is
the primary key.
2.5 Events
Events entity displays any event present near the user’s tourist spot. Details
such as EventID, EventType, StartDate, EndDate, Name and PlaceID.
2.6 Shopping
Shopping entity holds details about shopping spot around the area. Shop-
pingID, PlaceID, Category, Name and Location are stored.
2.7 Transportation
Transportation entity assist the user to move from one place to another. It
consists of TransID , PlaceID, Name, Area, ContactInfo,Category.
2.8 PhotoAlbum
This entity holds the picture album of each tour. It contains AlbumID,
PlaceID, Name.
2.9 Emergency
In case of any emergency such as health deterioration, loss of property etc.,
Emergency entity provides details such as Type, Contact, Address etc.
2.10 Restaurant
A lot of people find it difficult to find an eatery which caters to their needs.
Restaurant entity comes handy here. ResID, Name, Location, contactinfo,
type etc. are attributes of this entity.
5.2 Accommodation
The functional dependencies are {AccID, Name} , {AccID → Type} , {AccID
→ Location} , {AccID → MinCost} , {AccID → MaxCost} , {AccID →
Offer} , {AccID → WebsiteAndContact} There exists full functional depen-
dency. Hence table is in 3NF.
5.3 TouristPlace
The functional dependencies are {PlaceID → Name} , {PlaceID → Descrip-
tion} , {PlaceID → AccID} , {PlaceID → WeatherID, EventID, ShoppingID,
TransID, AlbumID, ResID, EmergencyID} Since all the attributes depend on
primary key and has no transitive dependency, the table is in 3NF.
5.4 Weather
The functional dependencies are {WeatherID → MinTemp}, {WeatherID
→ MaxTemp}, {WeatherID → WebLink}. The attributes depend only on
primary key. Therefore, the table is in 3NF.
5.5 Events
The functional dependencies are {EventID → EventType} , {EventID →
StartDate} , {EventID → EndDate} , {EventID → Name} There exists
fully functional dependency. Therefore, the table is in 3NF.
5.6 Shopping
The functional dependencies are {ShoppingID → Category} , {ShoppingID
→ Name} , {ShoppingID → Location} Table is in 3NF.
5.7 Transportation
The functional dependencies are {TransID → Name} , {TansID → Category}
, {TransID → Area} , {TranID → ContactInfo} , {TransID → Area} There
exist partial dependency and transitive dependency. Therefore, the table is
in 3NF.
5.8 PhotoAlbum
The functional dependencies are {AlbumID → Name} The table is in 3NF.
5.9 Emergency
The functional dependencies are {EmergencyID → Type} , {EmergencyID
→ Contact, Address} The attributes are fully functional dependent on Emer-
gencyID. The table is in 3NF.
5.10 Restaurant
The functional dependencies are {ResID → Name} , {ResID → Location} ,
{ResID → ContactInfo} , {ResID → type} The attributes are fully functional
dependent on ResID. The table is in 3NF.
2. Which is the most liked place and the least liked one?
3. List a place where users have gone more than once and list the counts
if they have gone more than once. [?]
5. List the means of transport used where climate is too hot and too cold?
[?]
7 Relational Algebra
1. ΠE.Name(σ(A.EndDate-A.StartDate) = 3 ∧ Max(cnt)γE.EventID,count(E.EventID)
→ cnt,Max(cnt)[ρA(Accommodation) ./ A.PlaceID = T.PlaceID [ρE
(Event) ./ E.PlaceID = T.PlaceID ρT(TouristPlace)]]) [?, ?, ?]
8 Conclusion
Tourism management system proves to be a strong system which has fol-
lowed all the industrial standards. Normalization is applied on all the tables
and are found to be in 3NF. The functional dependencies are also listed.
Working with such a system can enable the user to get any information with
low performance cost and increased throughput. As the database is created
with good design, the system can comply with any demand in the future. The
most widely used complex queries are also stated above. Also, the relational
algebraic translation proves that the database is designed properly.
9 References
[1] Barták, R., Zhou, N.: On modeling planning problems: Experience from
the petrobras challenge. In: Espinoza, F.C., Gelbukh, A.F., González-
Mendoza, M. (eds.) Advances in Soft Computing and Its Applications -
12th Mexican International Conference on Artificial Intelligence, MICAI
2013, Mexico City, Mexico, November 24-30, 2013, Proceedings, Part
II. Lecture Notes in Computer Science, vol. 8266, pp. 466–477. Springer
(2013)
[2] Barták, R., Zhou, N.: Using tabled logic programming to solve the
petrobras planning problem. TPLP 14(4-5), 697–710 (2014)
[4] Basseda, R.: Planning with Transaction Logic. Ph.D. thesis, Stony
Brook, NY, USA (2015)
[5] Basseda, R., Kifer, M.: Planning with regression analysis in transaction
logic. In: ten Cate, B., Mileo, A. (eds.) Web Reasoning and Rule Systems
- 9th International Conference, RR 2015, Berlin, Germany, August 4-5,
2015. Proceedings. Lecture Notes in Computer Science, vol. 8741, pp.
29–44. Springer (2015)
[6] Basseda, R., Kifer, M.: State space planning using transaction logic. In:
Pontelli, E., Son, T.C. (eds.) Practical Aspects of Declarative Languages
- 17th International Symposium, PADL 2015, Portland, OR, USA, June
18-19, 2015. Proceedings. Lecture Notes in Computer Science, vol. 9131,
pp. 17–33. Springer (2015)
[7] Basseda, R., Kifer, M., Bonner, A.J.: Planning with transaction logic.
In: Kontchakov, R., Mugnier, M. (eds.) Web Reasoning and Rule Sys-
tems - 8th International Conference, RR 2014, Athens, Greece, Septem-
ber 15-17, 2014. Proceedings. Lecture Notes in Computer Science, vol.
8741, pp. 29–44. Springer (2014)
[8] Blum, A.L., Furst, M.L.: Fast planning through planning graph analysis.
Artificial Intelligence 90(12), 281 – 300 (1997)
[9] Blum, A.L., Furst, M.L.: Fast planning through planning graph analysis.
Artif. Intell. 90(1-2), 281–300 (Feb 1997)
[11] Fikes, R.E., Nilsson, N.J.: STRIPS: A new approach to the application
of theorem proving to problem solving. Artificial Intelligence 2(34), 189
– 208 (1971)
[12] Giunchiglia, E., Massarotto, A., Sebastiani, R.: Act, and the rest will
follow: Exploiting determinism in planning as satisfiability. In: Pro-
ceedings of the Fifteenth National/Tenth Conference on Artificial Intel-
ligence/Innovative Applications of Artificial Intelligence. pp. 948–953.
AAAI ’98/IAAI ’98, American Association for Artificial Intelligence,
Menlo Park, CA, USA (1998)
[13] Kautz, H., Selman, B.: Planning as satisfiability. In: Proceedings of the
10th European Conference on Artificial Intelligence. pp. 359–363. ECAI
’92, John Wiley & Sons, Inc., New York, NY, USA (1992)
[14] Kautz, H., Selman, B.: Pushing the envelope: Planning, propositional
logic, and stochastic search. In: Proceedings of the Thirteenth Na-
tional Conference on Artificial Intelligence - Volume 2. pp. 1194–1201.
AAAI’96, AAAI Press (1996)
[15] Stefik, M.: Planning with constraints (MOLGEN: part 1). Artif. Intell.
16(2), 111–140 (1981)
[16] Stefik, M.J.: Planning with Constraints. Ph.D. thesis, Stanford, CA,
USA (1980), aAI8016868
[17] Zhou, N., Dovier, A.: A tabled prolog program for solving sokoban.
Fundam. Inform. 124(4), 561–575 (2013)