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 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!

2
Distributed Software Development
3
Renato Šoic
QR marks the spot Requirements Definition and
Design Description
4
Table of Contents

• General requirements
• Requirement groups
• Game
• Web Services
• Database
• Web Site
• Diagrams
• Architecture and technologies

5
General Requirements

• MVC architecture
• Web Site
• game accessible world-wide
• Web Services
• System funcionalities
• Database
• Store
• relevant
• data

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

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

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., users game
  status in this game)
• Changing game preferences
• etc.

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 users 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)

10
Use Case Diagrams
11
(No Transcript)
12
MVC Architecture
13
Database
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.

15
Web Site

• A simple example

SIGN IN
16

• Basic web site organization

17
Questions?