These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer Science and Engineering, University of M

1
NOTICE!

• These materials are prepared only for the
  students enrolled in the course Distributed
  Software Development (DSD) at the Department of
  Computer Science and Engineering, University
  of Mälardalen, Västerås, Sweden and at the
  Faculty of Electrical Engineering and Computing,
  University of Zagreb, Croatia (year 2010/2011).
• For all other purposes, authors written
  permission is needed!
• The purpose of these materials is to help
  students in better understanding of lectures in
  DSD and not their replacement!

2
Distributed Software Development
3
Dajan Zvekic Toni Pivcevic
Transport4You1 Release Candidate presentation
4
Important events (1)

• Minor changes in requirements
• At this point core project requirements are
  stable
• No further changes of requirements are
  anticipated
• New version of web application
• Old version of web application dropped
• Problems with technology (Java Servlets)
• New version of web application is built from
  scratch in Apache Struts 2 framework

5
Important events (2)

• Formal methods project
• Three members are assigned to formal methods
  project
• Acceptance test plan document released

6
Development process - Scrum

• Benefits
• Meeting requirements on time
• Project was resistant to requirements changes
• Clear tasks for every week
• Problems identified early
• Costs
• Time
• 1 2 hours per week for every member (meetings
  and discussions)
• Additional 2 hours per week for scrum master
  (organization)

7
Project status (1)

• 78 of requirements fulfilled
• 60 for web application
• 85 for rest of system
• All requirements should be fulfilled by the end
  of semester
• For score competition we plan do add new feature
• Integration of system with google calendar

8
Project status (2)

• Added features since Beta Presentation
• New version of web application
• Google API for web application
• Identification of standard routes
• Interruption and modifications of routes handling
• Transport route interruptions/modifications
  notifications
• GPS module with iphone

9
Smart system (1)

• Smart detection of user inside vehicle
• User only needs to turn on on bluetooth, system
  does everything else
• User ticket is activated automatically when user
  is detected inside vehicle (billing)
• Depends on payment type (user options)
• Smart data handling system (multi-threaded)
• Coordinator thread, thread pool data queue
  (scalability)
• Smart scheduling of heavyweight tasks
• Standard route identification
• Standard route optimization (not implemented yet)

10
Smart system (2)

• Standard routes identification
• Identification based on week days
• Optimized SMS usage
• Ticket purchase reminder
• Purchase of ticket by SMS
• Confirmation of ticket purchase (Ticket control)
• Standard routes interruption notification
• Standard routes modification notification
• Ticket expiration notification (new ticket is
  bought if user still travels)

11
System integration (1)

• We completed several rounds of integration
  testing
• At this time we are capable of connecting all
  parts of system with real devices
• GPRS with tethering capable smartphone
• GPS with gps capable smartphone
• SMS gateway mobile phone connected to computer
  with gnokii library (send recieve)
• Bluetooth detection

12
System integration (2)
13
Video
14
Features presented (1)

• User registration on web
• User options
• Administrator inserts transport route
  interruption on web
• Standard route interruption notification (SMS)
• Smart detection inside vehicle (via bluetooth)
• GPS localization

15
Features presented (2)

• GPRS communication between application inside
  vehicle and mainframe.
• Mainframe automatically handles billing of users
  prepaid ticket
• Ticket activation notification