1. InceptionPhase Mesekach Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

2. S C K M Vision and business case To develop a booking system for the restaurant To develop a booking system for the restaurant Improve the hand written booking system Improve the hand written booking system Executive summary: Executive summary: The vision behind this project is to develop, implement and test a working digital booking system which can replace the old hand writing booking system. The vision behind this project is to develop, implement and test a working digital booking system which can replace the old hand writing booking system. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali MeSeKaCh

3. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Boundaries Software boundary – Payment subsystem is not supposed to be implented in this particular project. Software boundary – Payment subsystem is not supposed to be implented in this particular project. Hardware boundary – Project will be developed for windows flatform. Hardware boundary – Project will be developed for windows flatform. MeSeKaCh

4. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Requirements Workflow MeSeKaCh

5. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Glossary Menu - Order items Menu - Order items Booking Manager - Control class/server Booking Manager - Control class/server Order Number - Specific order a unique customer has made Order Number - Specific order a unique customer has made Vision - Goal and purpose of this project Vision - Goal and purpose of this project Artifact - Any object made, modified, or used by people Artifact - Any object made, modified, or used by people MeSeKaCh

6. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Requirements MeSeKaCh

7. S C K M Functional Requirements R1. The system shall create and store information for new user. R1. The system shall create and store information for new user. R2. The system shall provide limited access for guest. R2. The system shall provide limited access for guest. R3. The system shall provide log in. R3. The system shall provide log in. R4. The customer should login before making reservation. R4. The customer should login before making reservation. R5. The system shall provide access of the customer’s reservation. R5. The system shall provide access of the customer’s reservation. R6. The system shall update restaurant’s capacity. R6. The system shall update restaurant’s capacity. R7.The system shall keep a record of all the information that has been stored. R7.The system shall keep a record of all the information that has been stored. R8. The system shall provide access to the restaurant’s menu. R8. The system shall provide access to the restaurant’s menu. R9. The system shall accept order online. R9. The system shall accept order online. R10. The system shall accept payment online through credit card. R10. The system shall accept payment online through credit card. R11. The system shall issue a unique reservation number. R11. The system shall issue a unique reservation number. R12. The system shall send an email for confirming the reservation. R12. The system shall send an email for confirming the reservation. R13. It shall be able to print the reservation information for the user. R13. It shall be able to print the reservation information for the user. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali MeSeKaCh

8. Non-Functional Requirements R1. It shall take 5 seconds to view reservation’s information. R1. It shall take 5 seconds to view reservation’s information. R2. It shall take 5 seconds to store information. R2. It shall take 5 seconds to store information. R3. System shall use C++ language. R3. System shall use C++ language. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

9. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Supplementary Requirement The system shall only take reservation of a maximum of two hours. The system shall only take reservation of a maximum of two hours. The system shall only take reservation of a maximum of eight people. The system shall only take reservation of a maximum of eight people. MeSeKaCh

10. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Diagrams MeSeKaCh

11. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use case Diagram MeSeKaCh

12. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use case Diagram: Update Account MeSeKaCh

13. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Include Use Case MeSeKaCh

14. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Domain Model MeSeKaCh

15. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Class Diagram MeSeKaCh

16. M C S K Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali MeSeKaCh Use Case Specification

17. M C S K Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali Use Case: Create New Account ID: PB1 Brief Description: The system creates new account for the customer. Primary Actor: User Secondary Actor: None Precondition: None Main Flow: 1.The use case starts when the user selects “Create New Customer Account”. 2.While the details are not valid 2.1.The system asks the user to enter necessary details. 2.2.The system validates the entered details. 3.The system creates a new account for the user Post condition: A new account has created for the user. Alternative Flow: Invalid Details Cancel MeSeKaCh

18. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Alternative Flow: Create New Account: Invalid Details ID: PB1.1 Brief Description: The system informs the user that he/she has entered an invalid detail. Primary Actor: User Secondary Actor: None Precondition: The user has entered an invalid detail. Alternative Flow: 1.The alternative flow starts after step 1 of the main flow. 2.The system informs the user that an invalid detail has been entered. Post condition: None Alternative Flow: None MeSeKaCh

19. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Alternative Flow: Create New Account: Cancel ID: PB 1.2 Brief Description: The user cancels the account creation process. Primary Actor: User Secondary Actor: None Precondition: None Alternative Flow: 1.The alternative flow starts anytime during the process of account creation. 2.The customer selects cancel. 3.The system cancels the account that is being created. Post condition: The new account creation on process has NOT been done. Alternative Flow: None MeSeKaCh

20. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use Case: Update Account ID: PB 2 Brief Description: The user wishes to update an account. Primary Actor: User Secondary Actor: None Precondition: User has to have an account. Main Flow: 1.Use case starts when the user click on “Update Account”. 2.If the user selects “Delete Account” 2.1.The system asks the user to enter primary detail that’s necessary. 2.2.The user enter the details needed 2.3.The system deletes the account. 2.4.The system informs the user that account has been deleted. 3.If the user selects “Edit Account” 3.1.The system asks the user for the necessary details. 3.2.The user enters the details necessary. 3.3.The system prompts another form where the user can input the new details necessary. 3.4.The user enters the details. 3.5.The system stores the details. 3.6.The system informs the user that the account has been edited. 4. The system updates an account. Post condition: An account has been updated. Alternative Flow: None MeSeKaCh

21. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use Case: Show Account ID: PB 3 Brief Description: The system displays user account. Primary Actor: User Secondary Actor: None Precondition: The user has to be logged on. Main Flow: 1.The user selects “Show Account”. 2.The system asks the user to enter the necessary details. 3.The user enters the details needed. 4.The system displays the details of the account. Post condition: An account has been shown. Alternative Flow: None MeSeKaCh

22. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use Case: Log On ID: PB 4 Brief Description: The Customer shall be able to log on. Primary Actor: User (Management and customer) Secondary Actor: None Precondition: The customer must have a USERNAME and a PASSWORD. Main Flow: 1.The use case starts when the user selects Log On. 2.User has to type in username. 3.User has to type in password. 4.While the user’s username/password is invalid 4.1. The system shall ask the user to enter the username/password once again. 4.2.System validates the log in. 5. Allows access to the system. Post condition: User Interface will pop up according to the user’s type. Alternative Flow: Invalid Username/ Invalid Password MeSeKaCh

23. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Alternative Flow : Log On: Invalid Username/Password ID: PB 4.1 Brief Description: The system informs the user that a wrong username/password has been entered. Primary Actor: User Secondary Actor: None Precondition: The user has entered an invalid username/ password. Alternative Flow: 1.The alternative flow starts after step 3 of the main flow. 2.The system informs the user that an invalid username/password has been entered. Post condition: None Alternative Flow: None MeSeKaCh

24. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use Case: Make Reservation/Order ID: PB 5 Brief Description: The customer makes a reservation. Primary Actor: Customer Secondary Actor: None Precondition: The customer was able to log on. Main Flow: 1.Customer selects the date and time of the reservation. 2.Customer selects number of person for the reservation. 3.The customer clicks search. 4.While table not available 4.1.The system asks the customer to choose another table. 4.2.The system searches for the table the customer wishes to reserve. 5.The system prompts the next user interface. 6.The customer enters the necessary details. 7.The customer click on next. 8.The system asks the customer if he/she would like to make an order. 8.1. If the customer clicks on NO, the system informs the customer that the reservation has been done. 9. The system asks the customer if she/he wants to pay online. 9.1 If the customer clicks on NO, the system informs the customer that the reservation has been made. 10. The system makes the reservation for the customer. Post condition: A reservation has been made. Alternative Flow: Makes Order Online, Payment, Cancel MeSeKaCh

25. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Alternative Flow: Make Reservation/Order : Makes Order Online ID: PB 5.1 Brief Description: The customer wants to make an order online. Primary Actor: Customer Secondary Actor: None Precondition: The customer was able reserve a table. Alternative Flow: 1.The alternative flow starts after step 8 of the main flow. 2.The customer clicks on the food and drinks that she/he would like to order. 3.The system shall inform the customer that the order has been made. Post condition: None Alternative Flow: None MeSeKaCh

26. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Alternative Flow: Make Reservation/Order : Payment ID: PB 5.2 Brief Description: The customer wants to pay online. Primary Actor: Customer Secondary Actor: None Precondition: The customer has made an order. Alternative Flow: 1.The alternative flow starts after step 9 of the main flow. 2.The system prompts a user interface where the customer can enter his/her credit card number. 3.While credit card number is invalid 3.1.The system asks the customer to enter his/her credit card number once again. 3.2.The system validates the credit card. 4. Payment has been made. Post condition: None Alternative Flow: Invalid credit card MeSeKaCh

27. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Alternative Flow: Make Reservation/Order : Payment : Invalid credit card ID: PB 5.2.1 Brief Description: The customer’s credit card is invalid or deactivated. Primary Actor: Customer Secondary Actor: None Precondition: The customer has entered an invalid credit card number. Alternative Flow: 1.The alternative flow starts after step 2 of the alternative flow: Payment. 2.The system informs the customer that the credit card number is invalid or that the credit card has been deactivated. Post condition: None Alternative Flow: None MeSeKaCh

28. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Alternative Flow: Make Reservation/Order: Cancel ID: PB 5.3 Brief Description: The customer wants to cancel the reservation on process. Primary Actor: Customer Secondary Actor: None Precondition: The customer is logged on. Main Flow: 1.The alternative flow can begin anytime. 2.The customer clicks on cancel. 3.The system informs the customer that the reservation has been cancelled. Post condition: A reservation has NOT been made. Alternative Flow: None MeSeKaCh

29. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use Case: Access To Reservation ID: PB 6 Brief Description: The management looks at the reservation that has been made. Primary Actor: Management Secondary Actor: None Precondition: The management has to be logged on. Main Flow: 1.The management selects time and date of reservation that he/she wants to access. 2.The management clicks on “Show Reservation” 3.The system asks the management to select the table reserved. 4.The management selects the table. 5.The management click on next. 6.The system shows the details of the reservation. 7.The management click on “Order’s Made”. extension point: Orders were made. 8. The management clicks “Payment”. 8.1. The system will inform the management whether the payment has been done or not. 9. A reservation has been viewed. Post condition: None Alternative Flow: Log out MeSeKaCh

30. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Extension Use Case: Print Order ID: PB 7 Brief Description: Segment 1: The management staff selects to print out the order that has been made. Primary Actor: Management Secondary Actor: None Segment 1 Precondition: The system has viewed the orders. Segment 1 Flow: 1.The management selects “Print Order”. 2.The system print out the order. Segment 1 Post condition: An Order has been printed. MeSeKaCh

31. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Alternative Flow: Access To Reservation: Log Out ID: PB 6.1 Brief Description: The management selects to log out. Primary Actor: Management Secondary Actor: None Precondition: The management has to be logged on. Alternative Flow: 1.The alternative flow starts anytime. 2.The system closes the window and return to the main page. Post condition: None Alternative Flow: None MeSeKaCh

32. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use Case: Cancel Reservation ID: PB 8 Brief Description: The Customer wishes to cancel reservation that has been done. Primary Actor: Customer Secondary Actor: None Precondition: The customer has to be logged on and has made a reservation. Main Flow: 1.The customer selects “Cancel Reservation” 2.The system asks the customer to enter necessary details. 3.The customer enters necessary details. 4.The system searches for the reservation and cancel it. 5.The system informs the customer that the reservation has been cancelled. 6.The customer clicks on “Done”. Post condition: The system has cancelled a reservation. Alternative Flow: None MeSeKaCh

33. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Use Case: Cancel Order ID: PB 9 Brief Description: The Customer wishes to cancel order that has been done. Primary Actor: Customer Secondary Actor: None Precondition: The customer has to be logged on and has made an order. Main Flow: 1.The customer selects “Cancel Order” 2.The system asks the customer to enter necessary details. 3.The customer enters necessary details. 4.The system searches for the order and cancel it. 5.The system informs the customer that the order has been cancelled. 6.The customer clicks on “Done”. Post condition: The system has cancelled an order. Alternative Flow: None MeSeKaCh

34. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali RISK LIST AND RISK MANAGEMENT PLAN Roles and Responsibilities Project Manager: Kallem Ullah Risk Officer : Charmie Dela Cruz Project Member Assigned a Risk : Setareh Vali and Melody Parsa S C K M MeSeKaCh

35. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali Risk ID: R001Classification: Lost of Booking Report Date: 24 February 2006 Description: Possibility of losing booking/ reservation if not noticed the first time. A risk that has something to do with the running program. Probability: Unknown yet. Impact: Failure to have a booking system Risk Exposure: Unknown yet. First Indicator: None so far. Mitigation Approaches: Keeping track of the all the details of reservation from the beginning for comparison. Date Started:Date to Complete:Owner: Setareh Vali Current Status: Contingency Plan: Trigger for Contingency Plan: S C K M MeSeKaCh

36. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali Risk ID: R002Classification: Reliability Report Date: 24 February 2006 Description: Not to be able to rely on the system completely. Probability: Unknown yet. Impact: Failure to have a booking system Risk Exposure: Unknown yet. First Indicator: None so far. Mitigation Approaches: Keeping track of the all the details of reservation from the beginning for comparison. Date Started:Date to Complete:Owner: Melody Parsa Current Status: Contingency Plan: Trigger for Contingency Plan: S C K M MeSeKaCh

37. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Analysis and Design Workflow MeSeKaCh

38. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Phase Plan And Software Development Plan Finalized class diagram Finalized class diagram Activity diagram Activity diagram Sequence diagram Sequence diagram MeSeKaCh

39. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M Appendix [ RUP] Anthony Crain : [ RUP] Anthony Crain : Rational up methods (RUP Iteration Planning 2004) Rational up methods (RUP Iteration Planning 2004) http:// www-128.ibm.com/developer works /rational/litray/5335.html http:// www-128.ibm.com/developer works /rational/litray/5335.html [RMP] Risk management Plan : [RMP] Risk management Plan : http://www.processimpact.com/process_assets/risk_mgmt_plan_t emplate_doc. www.processimpact.com/ MeSeKaCh

40. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh Prototype

41. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

42. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

43. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

44. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

45. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

46. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

47. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh

48. Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh The End