Book Auctioning System

1
Book Auctioning System

• Blue Jays

2
System Overview

• Our system is a book auction website for DePaul
  University. Students have the opportunity to buy
  and sell books in an auction structured system.
• The University also has the ability to publish
  sell the books directly to the students.

3
Book Auctioning System

• Types of User
• Application Administrator
• Auctioneer
• Buyer
• Seller

4
Why???

• Why a Book Action Site???
• Bookstores overprice their books
• Will encourage students to buy all their books
  for classes.
• Some Students only buy books for a particular
  quarter and have no use for them afterwards.
• Students can now sell them back for a good price!
  
• Students can save money on shipping by selling
  books to on campus students.
• Students will always need books thus, it is in
  demand- the market is there!

5
With That In Mind

• Here is our system

6
-Book Auction Website-

• http//www.skitowns.us/auction/main.php
• First, I will explain a few requirements from the
  site.
• Then, Sergey will follow with design and code.
• Next, Zuku will discuss the XML integration into
  our system.
• Finally, I will conclude our presentation.

7
Requirements (Logging In)

• -Main Page User Login Requirements-
• Requirement 2.1.1- User Login
• There will be a section to enter in a logon id as
  well as a corresponding password in the Interface
  of the main page. Also, contain a link for users
  without a login or password (users who have not
  logged in) to a page where they can submit any
  information need to become registered on the
  system.
• Requirement 2.1.1.1- Login and Password
• The system should display a means of input for
  the user on the main page to provide a login and
  password string acquired through the signup
  procedure (2.2) which the server side will
  verify, and then log the user into the system

8
Design Implementation (Logging In)
9
Design Implementation (Logging In)

• lt?php
• include_once("autoloader.php")
• login _GET'login'
• pass _GET'password'
• conObj new DBCon()
• con conObj-gtopenCon()
• uid UserDBcheckLogin(login, pass, con)
• if(uid gt 0)
• admin UserDBisAdmin(uid, con)
• user new User()
• user-gtUid(uid)
• user-gtLogin(login)
• user-gtAdmin(admin)
• user-gtupdateSession()

10
Requirements (Sign-Up)

• -Client-Side User Interface Registration-
• Sign Up page
• Additionally, the system should provide a link on
  the main page that will allow non-registered
  users to sign up to be able to use the system.
  Users will need to provide the following details
  in a form Username, Password, Password
  verification, E-mail, First Name, Last Name,
  Address, City, State, Zip, CC Number, CC
  Expiration date, and Campus. Once the information
  is submitted it, must wait for approval by the
  Administrator and will be confirmed via email.

11
Requirements (Sign-Up)

• -Client-Side User Interface Registration-
• Username The string that the user would like to
  use on the system. The system must validate that
  usernames are unique and up to 8 characters
  long.
• Password The string of the password that the
  user would like to use on the system, which must
  be 8 characters long. The password cannot be the
  same as the username, and the system should
  validate this on submission.
• Password verification The system should provide
  a means of input for the user to re-enter the
  password for verification. If the password and
  the password verification strings do not match,
  the system should inform the user in a message
  that the two must match.
• E-mail The system will provide a means of input
  for the user as a textbox to enter an E-mail
  address. The system should validate the e-mail
  addresses to see if they are Like _at_.,
  which is a check to see if the e-mail is in
  correct format. The e-mail address will be used
  in the verification process of a new user into
  the system.
• First Name The system should provide a means of
  input for the first name of the user, which must
  be a string no larger than 16 characters.

12
Requirements (Sign-Up)

• -Client-Side User Interface Registration-
• Last Name The system should provide a means of
  input for the last name of the user, which must
  be a string no larger than 16 characters.
• Address The system should provide a means of
  input for the street address location of the
  user. The address field should be optional to
  the user.
• City The system should provide a means of input
  for the user to enter the city, which will be
  required information.
• State The system should provide a means of
  input for the user to select the state out of a
  selection pick-list control that will contain the
  2-character abbreviation for each of the 50
  states.
• Zip-Code The system should provide a means of
  input for the user to enter a zip code. The
  system must validate the entry to be a 5-digit
  numeric input.

13
Requirements (Sign-Up)

• -Client-Side User Interface Registration-
• Credit-Card Number The system should provide a
  means of input for the user to enter their
  credit-card number. The system must validate the
  entry to be a 16-digit numeric input. Credit
  Card Number input is optional.
• Credit-Card Expiration Date The system should
  have two selection pick-list controls one will
  contain each of the months of the year
  abbreviated as 2-character digits (01-12), and
  the other will contain each of the years starting
  with 2005 and ending at 2015. The credit card
  expiration date input is optional however, when
  there is an input for the credit card number, the
  expiration date input becomes required.
• Campus The system should provide a means of
  input to the user to select the campus of DePaul
  that they are attending. This will include Loop,
  Lincoln Park, Ohare, Barat, and Naperville.

14
Design Implementation (Sign-Up)
15
Design Implementation (Sign-Up)

• // db-gtopenCon() takes care of this
• //mysql_select_db(sDatabase)
• /function UserIDCheck(sValue, oStatus)
• global sTable
• sUserID addslashes(sValue)
• oStatus-gtbValid false
• oStatus-gtsErrMsg "User ID 'sValue'
  already exist"
• sQuery "SELECT UserID FROM sTable WHERE
  UserID 'sUserID'"
• if (rRecordset mysql_query(sQuery))
• oStatus-gtbValid mysql_num_rows(rRecord
  set) 0
• mysql_free_result(rRecordset)
• /
• UserID _POST'txtUserID'

16
Design Implementation (Sign-Up)

• db new DBCon()
• rConn db-gtopenCon()
• if(UserDBisLoginUnique(UserID, rConn))
• sQuery "INSERT INTO user ( Login ,
  Password , FirstName , LastName , Email ,
  Address , City , State , Zip , Active ,
  CCNumber , CCExpDate)
• VALUES (
• 'UserID', 'Password', 'FirstName',
  'LastName', 'Email', 'Address', 'City',
  'State', 'Zip', 0, 'CreditCard', 'CreditDate'
• )"
• mysql_query(sQuery, rConn)
• newUid mysql_insert_id(rConn)
• sQuery "insert into userrole values (newUid,
  2)"
• mysql_query(sQuery, rConn)
• else
• bad true

17
System Testing (Sign-Up)

• Each requirement was tested through a formal
  Quality Assurance lifecycle with an indication of
  P/F with comments if necessary.
• All requirements implemented were system tested
  in addition to the unit testing at the time of
  implementation by the developers.
• One sample test case for the Sign-Up page
  requirements demonstrated

18
Requirements (Active Users)

• -Activating Users (Administration)-
• Requirement 2.2.2- Administration
  Approval/Account Activation
• Administration Approval
• In addition to the user registration interfaces
  and forms, there must be a completion process
  that the Administrator must perform to
  successfully register the user into the system.
  To meet this requirement, which requires data
  verification and authentication by the system, an
  Administrator to accept the user and have the
  system send a notification, and the system to
  accept e-mail verification from the user.

19
Requirements (Add Book)

• Adding a Book-
• Requirement 1.2.2.1
• The Product Management section of the Inventory
  Administration Interface should have a section
  providing the Administrator the ability to add a
  book (with a Buy NOW price if applicable).
  Ideally, a user will add his/her book as an item
  in their auction interface however, the system
  should provide the ability to add a book if the
  business need arises.

20
Requirements (Add Book)

• Adding a Book (Available Only to Registered
  Users)-
• Requirement 2.1.4
• The system must check to validate whether the
  current user is logged in. If the user is not
  logged in, the system must provide a link to the
  user to log-in, and display a message stating
  that this functionality is for registered users
  only. If the user is logged in, the system will
  provide a means for the user to enter in the data
  on the book Title, ISBN, Author, Starting Bid,
  End Date of Auction, Payment Method Accepted, and
  Location.

21
Requirements (Add Auction)

• - Add an Auction with Item Registered users
  should have the ability to start a new Auction by
  adding it to the system. For this process, the
  system must gather all required input from the
  user, and then validate and activate the auction.
  2.3.1
• Required Components of a New Auction
  (Requirements 2.3.1.1 2.3.1.8)
• Book Name In order to start an Auction, an item
  must be associated with the auction. The system
  should provide a means of input for the user to
  enter a name of the book. This should be a
  string input limited up to 100 characters in
  length.
• ISBN Number The system should provide a means
  of ISBN Number input from the user for every
  book. This should be a string input limited up
  to 100 characters.
• Book Details, Reviews The system should provide
  a means of free text input for the user for the
  item this information will be details about the
  book, and information such as how well it rates
  in the market. Any selling points from the user
  to persuade the audience to post a bid for the
  item will be inputted in this section.
• Authors Name The system should provide a means
  of input for the user to list the Author of the
  book. This information should be required, and
  validated by the system as a string input.

22
Requirements (Add Auction)

• - Add an Auction with Item Registered users
  should have the ability to start a new Auction by
  adding it to the system. For this process, the
  system must gather all required input from the
  user, and then validate and activate the auction.
  2.3.1
• Required Components of a New Auction
  (Requirements 2.3.1.1 2.3.1.8)
• Bid Start Price / Minimum Bid Price The system
  should provide a means for the user to input a
  start/minimum bid price for the user, which the
  system should mark as a required piece of numeric
  information for a new auction.
• Buy NOW Price The system should provide a means
  for the user to input a Buy NOW price that will
  be optional numeric information for an auction.
  The system should
• Bid End Date The system should provide a means
  of input from the user on the end date for the
  auction. The system must close the auction at
  1159 PM on that day, which will act as a cutover
  for the system to stop accepting bids. The
  system should send a notification message to the
  winning bidder and the auction owner user with
  the final bid.
• Preferred Payment Method The system should
  accept a preferred payment method from the user
  for each auction. The system should present
  these in a list of values in a pick-list that
  will include Credit Card, Cash, Check, Money
  Order, and Wire Transfer.

23
Requirements (Searching)

• -Searching-
• Requirement 2.1.2- Search for Books
• On the main page of the system, there should be
  another section that provides a function to
  search for books. There will be textboxes
  provided that will allow the user to search for
  books by any of the following Name, ISBN Code,
  Author, Categories, or Keywords. Upon completing
  the query, any auctions containing a product
  matching the information provided will be
  displayed on a new page (Product Auctions).

24
Requirements (Bidding)

• Bidding/Viewing Bids
• Requirement 2.3.3.1
• The system should provide a hyperlink on each bid
  that a user has received for an auction to view
  its details, which include the user who set the
  bid and the amount and time of the bid.

25
Requirements (Public Forum)

• -Public Forum-
• Requirement 2.1.5.1- Message Center (Planned for
  future expansion)
• On the main page, there will be a link to Message
  Center, which will allow users to send and
  receive messages to other users, and manage
  existing communication chains. There will be two
  options to a users Message Center. The system
  should first check to see if the user is logged
  in, and if so, the system will provide the user
  with two links
• (2) Message Board, which will display to the user
  all of the messages posted on the Message Board
  forum, with the ability to view and reply to any
  of the messages, and to add any new categories
  for a Message Board to start a new topic in the
  Message Board.

26
Requirements (XML)

• -XML Integration-
• We have developed an XML file that contains
  objects with attributes. The attributes of the
  XML file correspond to the attributes of an
  object (Book) in our business requirements.
  There are a few book objects with nodes that act
  as attributes for this object.
• An external script has been written to read these
  objects in the StockItems.xml file with the
  attribute nodes and, it inserts these objects as
  records into the Book table of our site.

27
Conclusion

• The Market for a Book Action Site will always be
  in demand and, it will only grow as the
  University continues to expand.
• The Book Auction System is a secure and easy way
  to get books to students
• Students can also expect better pricing when
  buying and cash back when selling
• The DePaul University Book Action System is also
  a great way to bring students together. Students
  can share a common interest among books on the
  site.

28
Conclusion

• Thank you!
• Thank you!
• Thank you!