Re presentation-flow

307 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
307
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Re presentation-flow

  1. 1. Group 20 …… and why you shall<br />sign our contract!<br />“If you don’t know where you’re going, you’re unlikely to end up there. “ – Forest Gump<br />
  2. 2. vision<br />
  3. 3. 4<br />system corner stones<br />
  4. 4. mobile application<br />… on user smartphones<br />
  5. 5. think locally …<br />… act globally<br />storage?<br />
  6. 6. database<br />… stores all the information<br />information?<br />
  7. 7. server interface<br />… feeds the application with information.<br />
  8. 8. web service<br />control<br />… serves your customers, <br />the restaurants.<br />
  9. 9. as well as…<br />… lets you control the information.<br />
  10. 10. your needs<br />
  11. 11. … so, what did we find?<br />
  12. 12.
  13. 13. core requirements<br />(functional)<br />mobile<br />
  14. 14. mobile application<br />search<br /> show<br /> present<br /> route<br />search<br />
  15. 15. search<br />“the user shall be able to search for restaurants within a five kilometer radius.”<br />
  16. 16. show<br />“the application shall be able to show search results.”<br />
  17. 17. present<br />“the application shall be able to present information about a restaurant.”<br />
  18. 18. route<br />“the application shall be able to show a route from a user chosen location to the restaurant location.”<br />
  19. 19. database and <br />server interface<br />storage<br /> communication<br />
  20. 20. storage<br />“a database shall store information about restaurants and different kind of user accounts.”<br />
  21. 21. communication<br />“a server interface shall handle the communication between the database and the mobile application(s).”<br />
  22. 22. web service<br />apply<br /> accept<br /> pay<br /> profile<br /> management<br />
  23. 23. apply<br />“a restaurant shall be able to apply for an account to the system.”<br />
  24. 24. accept<br />“the petition shall be accepted by an administrator before the restaurant gets an account.”<br />
  25. 25. pay<br />“restaurants shall have to pay for their restaurant to be shown in the system.”<br />
  26. 26. profile<br />“restaurants shall be able to edit their information in the system.”<br />
  27. 27. management<br />“there shall be administrator accounts for management of the system.”<br />
  28. 28.
  29. 29. quality<br />performance<br />interface<br /> hardware<br />
  30. 30. performance<br />“the system shall be able to handle at least 500 users simultaneously.”<br />
  31. 31. interface<br />“there shall be an intuitive interface. <todo>”<br />
  32. 32. hardware<br />“the system shall support all major smartphone brands and their operating systems.”<br />
  33. 33. conclusion<br />
  34. 34. intuitive user interface<br />Find me food!<br />
  35. 35. attract users<br />
  36. 36. attract restaurants<br />
  37. 37. profit<br />

×