Group 4 Project Page

Overview

This iteration, our main focus was implementing the registration and log-in use-cases, as Professor Palmer suggested to us. Aside from a persistent Android runtime error, we have done so.

Iteration Plan

On Server side we:

Created a TCP connection between the server and the client using Kryonet
Set up Hibernate to keep the DB consistent with our server objects
Set up the JPA Model Service to abstract out Hibernate details
The server now can receive login and registration requests, passes them to the DB, and sends a response to the client
The JPA Model has methods to register and log-in users
The server sends back an error when logging in with incorrect credentials
The server sends back an error when registering with an e-mail already in the database
The JPA Model we are running has unit tests for logging in and registering located in the "test" folder under the "GarconServer" project

On Client side we:

Created the log-in page
Log-in page sends a request to the server
Created the registration page
Registration page sends a request to the server
Created the task list page
Implemented task searching on the task list
Created the "user profile" page
Created the "create task" page

In the Commons (Both Client and Server)

Created the AbstractRequest class which can be extended into specific requests (ie. LoginRequest, RegisterUserRequest) that can subsequently be sent to and unwrapped by the server
Extended AbstractRequest into LoginRequest and RegisterUserRequest
Created the Interfaces for Task and User

General Iteration Notes:

we have our server running and client set up, but have a single Android runtime error on the client that we cannot seem to fix. We commented out the part of the application causing this error, but now we cannot connect Android to server. We plan on coming in for help with the error Mon/Tues

Goals For Iteration 4

Completing the log-in and register user use cases
Implementing the "create task" and "view the tasklist" use cases
Cleaning the backend architecture by creating a "Request Processor" class to perform actions based on requests and a "Proxy Builder" to facilitate building proxy objects to send back to the server. These two changes will spread the backend work and better follow the OOP paradigm

Goals For Iteration 5