Android Applicaton Development: Mandatory assignment

This text is preliminary: I might add more requirements, hints, etc. later.

This is the mandatory assignment for the 4th semester elective course Android Application Development.

Your solutions to this assignment must be "passed" before you can attend the 4th semester elective exam.

The case: Room reservations

In a few years the all educations at ZIBAT (EASJ) will move to a new location. Here we need an system to take care of room reservations. You must make an Android based prototype of this system.

Outside each class room, meeting room, etc. there will be an Android table showing reservations etc. for the room.

Teachers, students, administrations, etc. can see room reservations etc. on their Android devices (mobile phones etc.)

Users must be able to do CUD (Create, Update and Delete) on reservations.

The back-end

I have made a simple prototype of the back-end of the system: Some REST services accessible on http://anboroomreservation.cloudapp.net/Service1.svc/

GET methods

• http://anboroomreservation.cloudapp.net/Service1.svc/cities/
  Returns a list of cities where Zibat is present
• http://anboroomreservation.cloudapp.net/Service1.svc/buildings/
  Returns a list of all the builings (ie. adresses) of Zibat
• http://anboroomreservation.cloudapp.net/Service1.svc/building/2
  Returns infomation about the building with id=2
• http://anboroomreservation.cloudapp.net/Service1.svc/buildings/city/Roskilde
  Returns a list of all buildings (ie. adresses) there city=Roskilde
• http://anboroomreservation.cloudapp.net/Service1.svc/buildings/city/4
  Returns a list of all buildings (ie. addresses) where cityId =4
• http://anboroomreservation.cloudapp.net/Service1.svc/rooms/
  Returns a list of all rooms in all buildings of Zibat
• http://anboroomreservation.cloudapp.net/Service1.svc/rooms/building/1
  Returns a list of all rooms in the buidling with id=1
• http://anboroomreservation.cloudapp.net/Service1.svc/users/
  Returns a list of all users
• http://anboroomreservation.cloudapp.net/Service1.svc/user/1
  Return information abous a single user with id=1
• http://anboroomreservation.cloudapp.net/Service1.svc/room/1/2016-02-27
  http://anboroomreservation.cloudapp.net/Service1.svc/reservations/1/2016-02-27
  Return a list of all reservations for the room with id=1 on the date 2016-07 (format yyyy-mm-yy)
• http://anboroomreservation.cloudapp.net/Service1.svc/reservations/room/1/
  Returns a list of all reservations for the room with id=1
• http://anboroomreservation.cloudapp.net/Service1.svc/reservations/user/1/
  Returns a list of all reservations for the user with id=1.

POST methods

Add a new reservation to the back-end

http://anboroomreservation.cloudapp.net/Service1.svc/reservations

Request body format JSON
{
"RoomId": 1,
"UserId": 1,
"FromTimeString": "2016-03-02 13:00",
"ToTimeString": "2016-03-02 15:30",
"Purpose": "DSR meeting",
"DeviceId": "ksff4ld"
}

Hint: Use your browser and/or Postman to try the back-end before you use it in your application.

Hint 2: Information about DeviceId

Hint 3: DeviceId is a string "....", not an integer.

PUT methods

Updates an existing reservation

http://anboroomreservation.cloudapp.net/Service1.svc/reservations/5
Updates the reservation with id=5

Request body format JSON
{
"FromTimeString": "2016-03-15 8:20",
"Purpose": "Android lessons",
"RoomId": 1,
"ToTimeString": "2016-03-15 13:50",
"UserId": 2,
"DeviceId": "ksff4ld"
}

DELETE methods

• http://anboroomreservation.cloudapp.net/Service1.svc/reservations/7
  Delets the reservation with the specified id - 7 in this case.

Changing the back-end

If you want more service from the back-end you can ask for it in an email anbo@easj.dk. If I find you request relevant (and easy) I might implement it ... some day.

You are allowed to make your own back-end, but this is NOT part of the mandatory assignment.

Technical requirements

Activities

• The application must at least two (probably more) Activities

Screen size and density

• The application must look OK on screens of different sizes (phones and tables) and densities.
• The application must show more information on larger screens than on smaller screens.

Screen orientation

• The application must look OK in landscape and portrait orientation.
• No data is lost during change of screen orientation.

Lists

• The application must use list: ListActivity and/or ListView

Gestures

• The application must use swipe or other gestures.

Error handling

• The application must inform the user about communication errors (exceptions), etc.
  Just ignoring exceptions is not acceptable
• The application must use logging, specially for error conditions Log.e(..., ...)

Extras

• The user must login to the system to do CUD (Create, Update and Delete) on reservations
• The informations must look good on a big TV screen.
• Internationalization and locatization.
• GPS to go straight to the nearest building (or even room)
• Remember which room the user looked at last time he used the app - and start from there.