🆕 ⚠️ Please go to the UPDATE.md file for the latest details about the project ‼️.

Members:

• Timur Kartaev 727642
• Satenik Hovsepyan 727561
• Bruno Duarte 727396

1. Authentication
2. Basic player functionalities
3. Basic developer functionalities
4. Game/service interaction
5. Quality of Work
6. Non-functional requirements

1. Register, login and reset the password is already implemented in Django and we just plan to use them.
2. We are going to create models to represent the games, purchases, and the search feature and also built in constraints on what each user can play according to their purchases.
3. We are going to create a model "profile" to extend Django's user model and represent Developers/Players. Developers can add or remove games from their shelf.
4. We are going to use messages for communication between the game and the game service.
5. All code is going to be documented and separated in files to accordingly apply the DRY paradigm.

1. Mobile Friendly
2. Social media sharing
3. RESTful API
4. 3rd party login
5. Save/load and resolution feature
6. Own game

1. We plan to use bootstrap for the mobile friendly components
2. We plan to use OpenGraph.
3. Different views for providing the REST service.
4. We are going to use the third party app (python-auth) for Social Media login
5. We are going to store the state of the game in a model
6. We are going to develop a very basic game of guessing cards/values.

Note: We plan to start implementing extra features in aforementioned order and implement as many of them as we have time for using our best effort.

• Profile
  • role = CharField
  • games = ManyToMany(Game)
• Category
  • title = CharField
  • slug = SlugField
• Game
  • title = CharField
  • url = URLField
  • price = PositiveInegerField
  • category = ForeignKey(Category)
  • developer = ForeignKey(User)
  • status = CharField
  • is_deleted = BooleanField
• Order
  • code = UUID4Field
  • user = ForeignKey(User)
  • cart = ForeignKey(Cart)
  • status = CharField
  • total_amount = PositiveIntegerField
• Cart
  • user = ForeignKey(User)
  • status = CharField
  • created = DateTimeField
• OrderItem
  • game = ForeignKey(Game)
  • cart = ForeignKey(Cart)
  • price = PositiveIntegerField
  • amount = PositiveIntegerField
• Payments
  • order = ForeignKey(Order)
  • status = CharField
• GameScore
  • game = ForeignKey(Game)
  • user = ForeignKey(User)
  • score = IntegerField
• GameState
  • game = ForeignKey(Game)
  • user = ForeignKey(User)
  • state = JSONField
  • saved = DateTimeField

• LoginView
• RegisterView
• PasswordResetView

• GameListView
• GamePlayView
• CartView
• CheckOutView
• OrderFinishedView
• ProfileView

• GameListView
• CreateGameView
• EditGameView
• RemoveGameView
• SaleStatisticsView

• SaveUserScoreView
• ScoreDashboardView
• SaveGameStateView
• LoadGameStateView

• GameListView
• HighScoresView
• StatisticsView

1. We plan to have regular meetings, at least once a week to split tasks and assign features.
2. We would use GDrive for collaborative common documents and to eventually use them as a reference in our day-to-day tasks.
3. We would use Aalto Gitlab to keep track of our project and source code.

• Week 0 is the week 52 from 2018
• Week 1 corresponds to the week 1 from 2019