-
Notifications
You must be signed in to change notification settings - Fork 5
sds
This document purpose is to design the implementation of "Click-A-Table" in terms of architecture and data storage according to the use cases and the user stories that described on the SRS page.
The goal of design page are:
* Preparation for the realization of our software. * Checking correctness of software design. * Help us to split the tasks of the implementation between team members. * Focus and prioritize the developments we should think about in advance, before we start coding. * Realization and treatment of risks.| Main ability | Description | Risks | |
|---|---|---|---|
| 1 | Login | Only registered users can connect to the application | Medium |
| 2 | Select restaurant | User can select a restaurant he wants to visit | Low |
| 3 | Order table | User can save available table in the selected restaurant to specific hour | High |
| 4 | View menu | User can view the reach menu | Low |
| 5 | View course details | User can view all the details about specific course including its price. | Low |
| 6 | Order course | User can add specific course to the current order | Low |
| 7 | View order details | User can view all the courses in the current order | Low |
| 8 | Call a waiter | User can call a waiter for any request. | Low |
| 9 | Request a billing | User can call waiter to pay his order | Low |
#Related Documentation
This document contain 4 diagrams:
This diagram describe the hardware with software components in the system and the interface between them.
This department diagram describes the structure of the system by showing its departments, their properties and relationships between departments. The diagram describing the departments and their responsibilities and also show the connections between them.
This diagram describe the process and explain how the system and its components perform this process.
The data will be saved in the Data store. The tables and the relationship are describe in the diagram
| Requirement | Description |
|---|---|
| Accessibility | Easy and simple to use design for a better user experience. |
| Backup | Ensure our database safety in case of a data loss event. |
| Compatibility | Supporting as many browsers from different platforms. |
| Documentation | Reasonable documentation with functional specifications. |
| Extensibility | Adding features and customizations according to user's feedback. |
| Price | Free of charge, anyone can use it. |
| Privacy | Not allowing access to other user's list to respect their privacy. |