1 / 6

e A u c t i o n

e A u c t i o n. Aditya Joshi, Abhijit Nukalapati , Saumit Sebastian, Fizi Yadav. User.

irving
Download Presentation

e A u c t i o n

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. eAuction Aditya Joshi, AbhijitNukalapati, Saumit Sebastian, FiziYadav

  2. User The base User Entity contains attributes that help define a user, such as name, email, phone number, etc. The username is a primary key and instead of storing the age, we store the Date of Birth so we don’t have to update it every day. We also store a password (or its hash) as a User attribute. People and Companies are both distinct types of Users. The Company entity has a revenue and a company category attribute. The Person has an income and gender attribute. The Person also has a relationship with a Credit Card entity. A Credit Card is owned by a Person. A User is also involved in a ternary relationship with a Rating entity. A User rates a User using a Rating entity.

  3. Item An Item entity is arguably the most important entity. It defines the item that is being auctioned. Every item is defined by a unique itemID. There is also a short description, an image, a URL, a Buy It Now price, as well as a Reserve Price. A User places a Bid on a Item. The Bid relationship has a Price attribute which defines the most recent bid by a given User on a given Item. The relationship between a User and an Item is two-fold since an Item is Owned_By a User, and a User places a Bid on an Item.

  4. Category An Item belongs to a Category. Categories have a unique catID, as well as a unique URL which returns results for all Items in that Category or its subcategories. Each category has a ParentOf relationship with a series of other Categories, except for categories which have no subcategories. Each Category knows the catID of its Parent, except the Category ‘All’, which has no parent.

  5. Shipment A Shipment entity is created after a purchase is made. It has a unique ShipmentID, and contains an Is_successful field to ensure that the Shipment was completed successfully. Item and User are related to Shipment. A purchased Item is Shipped In a Shipment to the User that placed the winning bid. A given Item can only have one Shipment, and a given Shipment can only have one User to which it is sent. Shipments can have multiple Items and Users can receive multiple Shipments.

  6. The End

More Related