|
|
|
|
|
|
|
|
|
|
We will expect certain minimal functionality in each AuctionBase system -- beyond that, possibilities are unlimited. Minimal functionality includes a variety of queries and browsing capabilities over the current items up for auction, the bids on those items, and the sellers and bidders. AuctionBase also must provide a means for entering bids, and for concluding auctions on individual items. Various integrity constraints must be monitored. Although AuctionBase uses SQLite and therefore has transaction support, multi-user issues are not a focus of the project.
Web programming skills are not required for the AuctionBase project. We will provide skeleton PHP code for most aspects of the web interface. Those students savvy in web programming may rewrite or extend the interface as they please.
At the end of the course, there will be a small contest in which we select a few of the best AuctionBase systems to be demonstrated in class and linked to the course home page. No extra credit is given, but winners will be invited to enjoy lunch at the Stanford Faculty Club with Prof. Widom, the TAs, and the other contest winners.
The scope of the AuctionBase project is such that it can easily be completed by each student in the class individually -- partners or teams will not be used.
To develop the project all students will use the open-source SQLite relational database management library and the PHP scripting language, running under Unix. (See Interfacing with Stanford's Unix Machines.) An initial part of the project involves standalone parsing and processing of XML data, which is typically done using Java. We will assume students are proficient already with Unix and Java, but we are not assuming familiarity with web or database programming -- help sessions will be provided.
In general, students are welcome to use alternative languages, systems, and tools if they wish. However, only SQLite and PHP on the Stanford Unix Corn machines will be supported by the course staff, and the specifications for the project must be met regardless of the languages or tools used. We will provide an XML parser in Java for processing the initial XML data, but students may use other tools or languages if they prefer.
Important note: Students using alternative languages, systems, and tools must be able to submit all of their code using the standard submission procedure. Furthermore, the TAs must be able to compile and run all submitted code on the Stanford Unix Corn machines without any additional packages or runtime support, and with no additional effort over that required for projects using the supported languages and tools.
You will be given a large volume of data downloaded from the eBay web site and stored in XML files. You will examine the data and design a good (we hope) relational schema for it. You will then write a program or scripts to transform the data from its XML form into SQLite's load file format, conforming to your relational schema. You will create your schema in your own SQLite database and load the data.
You will incorporate data integrity checking into your AuctionBase database using SQLite constraints and triggers. You will also add a "current time" feature.
As a baseline, you will design an appropriate set of queries and updates for your AuctionBase system and create a simple web interface for them. Ambitious students may migrate the simple front-end into a user-friendly web interface that looks like a real auction site, and may exploit triggers, views, or other SQLite features for additional functionality. Use your creativity. Several projects will be selected to be demonstrated on the last day in class (for glory, not grades).
|
|
|
|
Please note that sometimes during regrading we discover a grading
error or misjudgement in which too many points were awarded. In this
case, your score will be lowered. In other words, a regrade
request may result in a higher score, a lower score, or no change.
|
|
Under the Honor Code at Stanford, each of you is expected to solve the automated quizzes and exercises independently, and to submit your own original work for challenge problems, database queries, and the programming project. On many occasions when working on assignments (but never exams!) it is useful to ask others -- the instructor, the TAs, or other students -- for hints, or to talk generally about aspects of the assignment. Such activity is both acceptable and encouraged, but you must indicate on all submitted work any assistance (human or otherwise) that you received. Any assistance received that is not given proper citation will be considered a violation of the Honor Code. In any event, you are responsible for understanding, performing or writing up, and being able to explain on your own, all quiz answers and other work that you submit. The course staff will pursue aggressively all suspected cases of Honor Code violations, and they will be handled through official University channels.
If you have any questions about this policy or about the degree to which we will pursue Honor Code violations, please discuss your concerns with the course staff immediately.