1 / 17

BTW ”I f you go , my advice to you” - Distributed Software Development

BTW ”I f you go , my advice to you” - Distributed Software Development. What’s on menu for today?. Customers wishes Requirements Architecture Google “all-mighty” Diagrams. What customers Want (MDH). What customers Want (MDH) Suggestions. Mix text and picture to provide information .

lilly
Télécharger la présentation

BTW ”I f you go , my advice to you” - Distributed Software Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BTW ”If you go, my advice to you”-Distributed Software Development

  2. What’s on menu for today? • Customers wishes • Requirements • Architecture • Google “all-mighty” • Diagrams

  3. What customers Want (MDH)

  4. What customers Want (MDH)Suggestions • Mix text and picture to provide information. • E.g. Show the picture of the place • Too much detail can make it a mess • Location of ATMs

  5. What customers Want (FER) Continue cooperation (precentage of yes) : 52%

  6. What customers Want (FER)Suggestions • Pictures (video not so important) , small symbols. • Locations: • Banks • ATMs • Parking places • Playgrounds • Public institutions • Public transport (Tram, Taxi and Bus)

  7. Functional Requirements • 1. Insert Departure and Arrival destination • 2. Users choose type of travel offered by Google ( Driving, walking, public transportation * ) • 3. User chooses type of advice ( default user preferred are automatically checked ) • 4. User should be able to register • 5. Registered users have to be able to do login and logout • 6. Registered users have to be able to write advices • * NOTE will be available by Google in future, for now users can draw the transportation lines on map

  8. Functional Requirements • 7. Admin has to be able to delete or modify an advice • 8. Users can flag advice as inappropriate • 9. Admin can promote an user as Moderator • 10.Admin can remove inappropriate users and all their content • 11. Moderator and admin can remove flags if content is ok • 12. Users can report content (advice and comments)

  9. Non Functional Requirements • 1. When the user click the button "search" the system have to respond fast enough - It depends of the connection's type ADSL,T1 etc. • 2.The system should work on all the browsers • 3. Every image should have appropriate tags to enhance web accessibility

  10. Architecture

  11. Database

  12. Map visualisation • Mapping web service (Google Maps) • Connector class (JavaScript) • extensibility • Based on KML

  13. Connector class • Display advice stored in database (KML) as map overlays • Provide an easy to use point-and-click interface • Place markers, draw lines and polygons • Edit existing objects • Retrieve routes from route calculation service

  14. Use Case Diagram

  15. Sequence Diagram – Insertingadvice

  16. Sequence Diagram – Getting advice

  17. Questions ?

More Related