GameTrader project
Upcoming SlideShare
Loading in...5
×
 

GameTrader project

on

  • 213 views

 

Statistics

Views

Total Views
213
Views on SlideShare
213
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • The short Description should not be more than 4 or 5 lines lines.
  • In this slide, describe 3 to 5 major reasons of implementing this system: Each reason should not be more than 2 lines
  • In this slide, provide the major parts of your ER diagram. The font size of your text should be 20. Use the notation used in the course slides. It’s better that you have one connected diagram instead of separating it to several diagram If you cannot fit your complete ER diagram in one slide, just show the main part of it. For example, remove some of the attributes.
  • In this slide, provide the major parts of your Database Schema. The font size of your text should not be less than 20. It’s very important that your database schema be match (and reflecting) your ER-diagram. Specify the Primary key and foreign keys very similar to the notation used in course slides. If you cannot fit your complete DB schema in one slide, just show the main part of it. For example, remove some of the attributes.
  • Show the screenshot of your user interface in this slide. Make sure that the font size of your scrreenshot is readable enough and is also in accordance with other slides.
  • Show another main of your project in this slide. Make sure that the font size of your screenshot matches the previous slide.
  • Show a snapshot of your current real data in this slide. You do not need to show all rows of your tables. Also you need not to show all tables of your database. The font size should not be less than 18.
  • Copy one or two (piece’s) of your code in this slide. Choose a good pieces of your code. Assume you want to have a tutorial session. The font size should not be less than 16

GameTrader project GameTrader project Presentation Transcript

    • Team Members:
    • Juan P. Aleman: Grad. student, Year 2
    • Ashley D. Rivera: ICOM student, Year 6
    • Kevin J. Baez: ICOM student, Year 4
    … is a web application designed to facilitate the exchange of video games by the use of search functionalities, maps and social networks. We aim to provide gamers with a trading community, where users can be aware of games people are willing to trade around their area.
  • Motivation
    • We consider ourselves gamers and as gamers we were concerned by the following:
    • What should I do with my old games?
    • Retail stores pay less than the value of the games.
    • What if a could build my own trading community, where I'm aware of games people are willing to trade near my area.
  • Entity-Relationship Diagram
    • Screenshot of GameTrader's ER-Diagram.
    • Our data base design was successfully tested to be BCNF.
    • View full size diagram at:
    • http://136.145.34.11/~g4/files/ICOM5016_Phase3_G4.pdf
  • Database Schema
    • Screenshot of GameTrader's Schema.
    • Contains at all:
      • 17 tables
      • For a total of 68 attributes.
    • For full size schema visit:
    • http://136.145.34.11/~g4/files/ICOM5016_Phase4_G4.pdf
  • User Interface Home Page
  • User Interface Game Page
  • Database Instance DBMS: PostgreSQL
  • Sample Code @login_required def myProfile(request): prueba = "esta afuego!!!" if request.user.is_authenticated(): gtuser = request.user.username else: gtuser = None return render_to_response('gtUsers/myProfile.html', { 'prueba': prueba, 'gtuser': gtuser}, context_instance = RequestContext(request)) Context(request))
  • Miscellaneous Information
    • Development tools: Django
    • DBMS: PostgreSQL
    • Approximate total lines of code: ~ 7,000
    • Approximate lines of SQL: ~ 500
    • Approximate development man-hours: 500
    • Number of tables: 17
    • Number of columns: 68
  • Further Information
    • To see the application, visit
    • http://136.145.116.93/gametrader/
    • To see the source code, visit
    • http://136.145.34.11/~g4/
    • To see the ICOM5016 course page, visit
    • https://ece.uprm.edu/~ahchinaei/courses/2010sep/icom5016/index.html
    • To contact us, email
    • [email_address]
    • [email_address]
    • [email_address]