Enterprise GTD ^{Presentation PDF}

Fix on iteration 3 comments

General aspect:

• You should either commit the ORMLite jar to the repository or set up Maven to fetch it automatically.

  Updated. Moved common jars and dependencies into common project, and added necessary jars into corresponding projects.

• You should commit your appcompat directory.

  Committed appcompat directory so that everyone share a same version, and the new user could clone the whole project without explicitly importing appcompat project.

• Another good general rule is that you should not commit anything which is generated: Do not commit class files, the gen directory, the bin directory, etc. You should fix your .gitignore to account for these. For example, to ignore .class files, the line should be "*.class", not just ".class" You should also make sure to run "git rm" to get rid of them.

  Fixed.

• A repository should be poratable: You have some paths in your Eclipse projects that point to files by absolute path; this means that another computer can't just use the repository as-is.

Fixing.

Webpage aspect:

• It's good that you managed to set up a VM and the /service/list link on your webpage is a good idea. However, when running my own server, I get exceptions (InstantiationError) when going to the /service/list url; you should fix this.

  Fixing.

Project aspect:

• I assume that you know that you should not store passwords in plain text in a database and that you're simply doing so for now for convenience; you should fix this before iteration 5 at the latest.

  Fixing. Expecting to fix before iteration 5.

• You are hard-coding the database url in the server, including the IP address, which is definitely wrong and means that I can't run the server properly. You are also running as the mysql root user and hardcoding the mysql root password into your code, which is probably wrong. Consider using a configuration file an java.util.Properties.

  Migrate the settings to a database.properties file. Currently still using root user, but Sql scripts is ready to be employed, expecting to fix that before iteration 5.

• The assertEquals(boolean, boolean) warnings should be fixed by just using assertTrue() or assertFalse(). The Assert is deprecated warnings should be fixed like in this SO post: http://stackoverflow.com/q/24013210/52310

  Re-implemented the whole JUnit test on loginServiceImpl class, fixed all problems mentioned.

• I don't see the point of the gender and birthday fields in your database; justify them or remove them.

  We planned to have an access to google account later, so this could be used to store user information for further use.

• Your login screen fails silently if the login is incorrect; you should notify the user instead.

  Import Crouton package to display messages, and validation check. So that user knows what blocks their login.

• You SHOULD NOT have empty catch blocks. Ever. In development, you should at least have a TODO there.

  Fixed.

• In your register page, the text overlaps with the entry field and the right-hand side is cut off; this is probably the result of the particular emulator size I'm using, but you should fix it nonetheless.

  Fixing. Expect to be fixed before iteration 5.

Test aspect:

Added a lot more JUnit test.

See Progress.

Iteration Plan

Check out current implemented functions on our server.

1. Iteration 3
   • Achieve connection between client, server, database
   • Update Javadoc on Android Activities
   • Write Junit test class structure
   • Re-evaluate resource requirements

100% completed.

2. Iteration 4
   • Complete login & register function and unit test
   • Part of dashboard function
   • Update Javadoc

125% completed.

See Progress.

3. Iteration 5
   • Complete all of the key function
   • Anticipate alpha stage
   • Start scenario test
   • Update Javadoc
   • Refactoring
4. Iteration 6
   • Implement some extend features if possible
   • Fixed all known bugs
   • Give beta version out to students
   • Prepare presentation demo and materials

Project progress and status

What we have done?

Function:

• Fully functioning Login, Register including validation check
• Import Crouton to show message on android client
• Almost functioning Project function implementation on both server and client side.
• Almost functioning Task function implementation on both server and client side.
• Significantly improved UI.
• Gestures is now supported.

Unit test:

• Deploy test database on each unit test, so that each test is independent.
• All test case on Login and Register on server side.
• Partial test case on Task, Project on server side.

Architecture:

• Encapsulate error message class to pass between client and server.
• Universal database Sql scripts.

Login Screen

Java Docs

Have a insight of our java doc.

Updated Java Docs for

• Android client activity
• Android client proxy
• Server DAO
• Server Helper
• Unit Test on Login and Register
• New Function
• Model Relation
• Error Message Exception
• Utility Classes

Update of Resource

Architecture

• Java
• Virtual Machine from CS Department to host our webserver and database
• Hibernate ORMLite
• MySQL

Resource

• Android SDK
• Android Devices
• Geny Motion Android Emulator
• Libraries
  • Java-json-rpc
  • Jackson Core
  • Crouton