GameZone/architecture
CS290F Fall 2006 - UCSB Computer Science - Thorsten von Eicken
Home | Overview | Architecture | CriticalPath | Optimizations and Analysis | Performance on multiple servers | Caching | Conclusion
Contents |
[edit]
Project 2 Goals
- Develop scripts to populate DB with 100K records
- Design and implement all tables required keeping the core functionality in mind.
- Create basic browsing screens to view the DB.
- Create a user login screen.
- Implement all remaining features as spectified in part 2B
[edit]
Controllers
- account_controller - Has Functionality to signup,login,edit,change password,logout etc.Implemented using http://www.agilewebdevelopment.com/plugins/acts_as_authenticated plugin
- games_controller - Functionality to browse games,add games to cart,check out,save cart etc
- reviews_controller - Functionality to browse , add new reviews etc
- specs_controller - Functionality to list specifications etc
- search_controller - Functionality to search and view search results
[edit]
Models
- Products : contains basic info of the games. This is the Master Table.
- Reviews: contains zero or more ratings and reviews for each product in the products table.
- Specifications: contains info about product specifications. Used for displaying products based on spectific categories, such as software type, style, system requirements,etc.
- Users: contains basic account information, billing address, encrypted password, credit card info, etc.
- Cart: current contents in shopping cart.
- Wishlists: user wish lists placeholder
- Orders: All purchase transactions.
- Ordered_items : Details of the games in each order and the quantity purchased.
- Game_searches : A model corresponding to the MyISAM table of games with Full Text index on productname
[edit]

