1. 12015-09-10 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 2009/2010). 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! NOTICE!

2. 22015-09-10 Distributed Software Development

3. 32015-09-10 QR marks the spot Requirements Definition and Design Description Renato Šoić

4. Table of Contents General requirements Requirement groups –Game –Web Services –Database –Web Site Diagrams Architecture and technologies 42015-09-10

5. General Requirements MVC architecture –Web Site game accessible world-wide –Web Services System funcionalities –Database Store relevant data 52015-09-10

6. Game Requirements Games are accessible world-wide –QR codes used in the games  QR code readers on mobile phones needed –The game takes place in the real world –2 game types supported Treasure hunt & Race Variations of these 2 types (i.e., public / private, time limited / unlimited) –User-created games 62015-09-10

7. Database Requirements Technology: MySQL (free) All relevant data stored in the DB –Users data, games data, locations of the QR codes, users’ private messages, game comments Hibernate –For mapping the DB Table in the DB == Object in Java Column in the DB == Attribute in Java 72015-09-10

8. Web Service Requirements Web services described with WSDL Process all the data exchanged between the DB and the Web Site –Tasks: Storing / Retrieving user data while Signing up / in Storing created game and its preferences Retrieving the data about specific game that a specific user is playing (i.e., user’s game status in this game) Changing game preferences etc. 82015-09-10

9. Web Site Requirements Web site –makes the game accessible worldwide –provides a user-friendly interface for Communicating with the system / other players Playing or creating the game Updating user’s game status Getting the information user is interested in For visitors  Sign Up option Various existing APIs should be used (i.e., GoogleMaps, Facebook, Twitter) 92015-09-10

10. Use Case Diagrams 102015-09-10

11. 112015-09-10

12. MVC Architecture 122015-09-10

13. Database 132015-09-10

14. Web Services The link between the database and the Web Site –Storing / Retrieving user data while Signing up –Changing game preferences –Search actions –etc. 142015-09-10

15. Web Site 152015-09-10 SIGN IN A simple example:

16. 162015-09-10 Basic web site organization

17. Questions? 172015-09-10