1 / 26

Comprehensive Requirements and Architecture for the Search4Yummy Mobile and Web Application

This document outlines the functional and non-functional requirements for the Search4Yummy application, designed for exploring restaurants and dishes. It details the user stories for customers, restaurant staff, and administrators, including browsing, searching, and providing feedback on food options. The system architecture follows a 3-tier model with distinct layers for presentation, business logic, and database interactions. Key considerations for usability, accessibility, performance, and privacy are included to ensure a seamless user experience.

buffy-strong
Télécharger la présentation

Comprehensive Requirements and Architecture for the Search4Yummy Mobile and Web Application

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. Distributed Software Development 2011/12

  2. Search4Yummy Requirements Definition and System Architecture • Muhammad Sulyman • Petar Paar • Yehui Wang • Ronald Wolvers • Jan Čustović • Andrej Garić • Ivan Bandalo • Lovro Maričić

  3. Outline • Functional Requirements • Usecase Models • Nonfunctional Requirements • External Interfaces • Components • System Architecture • Database Design

  4. Functional Requirements Mobile application Web application Customer Staff member Restaurant System administration Guest User Administrator

  5. Customer Requirements • Browse restaurants • Search restaurants • Popularity, location, type,seat availability, food offer, “I feel lucky” • Browse dishes • Search dishes • Price, type, restaurant

  6. Customer Requirements • Feedback • Comments, photos, likes, recommendations • News • Certain restaurant, type of restaurant • Check-in

  7. UC Model: Customer

  8. UC Model: Customer

  9. UC Model: Customer

  10. Restaurant Requirements • Menu update • Seat availability update • Restaurant info update • News update

  11. UC Model: Restaurant

  12. System Administration Requirements • User management • Restaurant management • Restaurant staff members management

  13. UC Model: Administration

  14. UC Model: Administration

  15. UC Model: Administration

  16. Nonfunctional Requirements 2014-11-08 16 Usability Accessibility Performance Privacy and safety Portability

  17. Requirement Group & definitions ADM RS USM GUM USW GUW NFR Must Should Could Would Requirementdefinition

  18. External Interfaces

  19. Components

  20. System Architecture • 3-tier application • Presentation layer • Bussiness logic • Database layer • Client/Server communications model • Each tier can be developed concurrently • Tiers communicate thru interfaces • Easy to change implementation of one tier without changing other tiers

  21. Presentation/Bussiness layer • Struts2 MVC • Spring, Spring security • View rendering: Tiles, Freemarker, taglib, JSON, XML

  22. Database layer • JPA/Hibernate ORM framework • Ehcache • Spring data

  23. Design patterns • One class must do one thing (decoupled as much as possible) • Tests for important parts • Use singletons when possible • Only object itself can change its state (use getters and setters) • Respect naming convention

  24. Stack overview

  25. Questions?

More Related