[go: up one dir, main page]
Scribd
Upload
112 views3 pages

Homework3 PDF

The document describes the database tables for a room rental application. It includes tables for user accounts and permissions, student and owner profiles, bookings, houses and individual rooms, maps and location features, and relationships between owners and permissions. The application allows administrators to input amenity details, view room listings from owners, and approve or reject listings for public view.

Uploaded by

Bikesh Mufc Twanabasu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
112 views3 pages

Homework3 PDF

The document describes the database tables for a room rental application. It includes tables for user accounts and permissions, student and owner profiles, bookings, houses and individual rooms, maps and location features, and relationships between owners and permissions. The application allows administrators to input amenity details, view room listings from owners, and approve or reject listings for public view.

Uploaded by

Bikesh Mufc Twanabasu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Homework Exercise 1

Point (PointID, CoorX, CoorY, ScenaryId, Name)

Scenary (ScenaryId, Description, WebLink, RouteID)

Vegetation (Name, Species, WebLink)

Route (RouteID, Length, Difficulty, ParkID)

Line (LineID, NumberofPoints, RouteID)

Park (ParkID, Name)

Area (AreaID, Name, Surface, PolyID, ParkID, category)

ProtectedArea (AreaID, ProtectionID, Regulations)

Polygon (PolyID, NumberofPoints, FillingColor)

FindArea (RouteID, Name, area)

Poly_Point (PointID, PolyID, PointPosition)

Line_Point (PointID, LindID, PointPosition)


Exercise 2

Admin (username, password, email, contact)

Permission (accountID, type, accessLevel, username)

Owner (nif, name, address, email, contactNo)

Payment (paymentID, dateOfPayment, creditCard, debitCard, bankTransfer, bookingID, nie, nif)

Student (nie, name, universityName, faculty, address, email, contacts, accountID)

Booking (bookingID, duration, nie)

House (polygonID, houseID, houseNo, description, address, municipalityID)

Room (roomID, address, share, rent, description, houseID)

MapLayers (mapID, localityInfo, weatherInfo, cultureInfo, username)

PointFeature (pointID, xcoordinate, ycoordinate, category, mapID)

LineFeature (lineID, curvature, startPoint, endPoint, category, mapID)

PolygonFeature (PolygonID, noOfSide, category, mapID)

Facilities (pointID, name, supermarket, hospitals, busStation, trainStation, bicicasStation, security,


others)

RoadNetwork (lineID, routeID, name, type)

Country (countryName, countryID, continent)

Province (provinceID, name, countryName)


Municipality (municipalityID, name, population, provinceID)

Owner_Permission (nif, accountID)

The UML diagram represent the administrator component of the RoomFetch application. It’s a web
based application which facilitates renting a room or an apartment especially for students foreign to
a city. The application will provide information on login details of the students and room owners for
the administrator. And administrator will have the facility to input the details of amenities such as
locations and details of services. Administrator also have the facility to view the room details provided
by the owners and can either approve or reject listing of the room in the publicly viewable list.

The database table is created based on the UML diagram.

You might also like