Repository navigation
Iteration_3
Ashwin174 edited this page Dec 4, 2020
·
21 revisions
User case Diagram for Iteration 3
| Test Name | Description | Expected Output | Tested By | Date/time | Pass /fail |
|---|---|---|---|---|---|
| Customer Registration and Login | Customer input valid user name and password to get authentication and then it takes to the main page | Testing processed and customer is good to register and login | Ashwin | November-03-2020 | Pass |
| Employee Registration and Login | Employee input valid user name and password to get authentication and then it takes to the main page | Testing processed and customer is good to register and login | Ashwin | November-03-2020 | Pass |
| Customer and Employee logout | Customer and Employee can click the log out button to exit from the main page | Testing processed and logout function is working | Ashwin | November-03-2020 | Pass |
| Customer Reservation | Customer can reserve the seat by providing details of time, date, number of people | Testing processed and customer is good to register and login | Ashwin | November-15-2020 | Pass |
| Employee Approval | Employee can approve the reservation and it will be shown in the record list | Test successfully and after approval customer name appeared in the list | Ashwin | November-17-2020 | Pass |
| Make Payment by Employee | Employee will make payment for the customer and can view whether customer has paid or not in the list | Test successfully and predicted output received | Ashwin | November-23-2020 | Pass |
| payment Confirmation by Customer | Customer can confirm the payment and can see the previously paid bills | Test successfully and predicted output received | Ashwin | November-25-2020 | Pass |
| Support Category | Refactoring Category | Item Description | Identified By | Hours Estimation |
|---|---|---|---|---|
| Adaptions | Data Refactoring | Customer should wait for the response from the employee to know whether they got reservation. There is no other option | Ashwin | 3 hrs |
| Enhancement | Code Refactoring | For the payment section, transaction through the card can be developed | Ashwin | 3 hrs |
| Enhancement | Architectural Refactoring | For the regular customer we can give any special offers or discount | Ashwin | 3 hrs |
| Adaption | Code Refactoring | Customer can check for the availability of seats | Ashwin | 3 hrs |
| Enhancement | Code Refactoring | Special Deals in the restaurant should be make available to the customer | Ashwin | 2 hrs |
| Adaption | Code Refactoring | Customer will get the notification when the seat is free | Ashwin | 4 hrs |
| Enhancement | Data Refactoring | Employee can view the list of reservation based on the reservation time of each customer | Ashwin | 3 hrs |
| Corrections | Data Refactoring | Every time Customer has to confirm the payment then only it will appear in the paid list of the employee part. | Ashwin | 2 hrs |
| Corrections | Architectural Refactoring | Customer can delete the reservation by themselves and when the do so, it should be notified by the employee | Ashwin | 4 hrs |
Currently we are working to add more features and ideas to the project so that in the upcoming years we would be able to develop our project to a higher level so that it will meet all the requirements of the client. Some of the features that we are planning is that, customer would get the notification of the current status of the seats available reservation and customer can select the available tables.