Inception

1

• Inception
• Phase

Mesekach Kaleem Ullah, Melody Parsa, Charmie
Dela Cruz, Setareh Vali
MeSeKaCh
2
Vision and business case

• To develop a booking system for the restaurant
• Improve the hand written booking system
• 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.

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
3
Boundaries

• Software boundary Payment subsystem is not
  supposed to be implented in this particular
  project.
• Hardware boundary Project will be developed for
  windows flatform.

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
4
RequirementsWorkflow
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
5
Glossary

• Menu - Order items
• Booking Manager - Control class/server
  
• Order Number - Specific order a unique customer
  has made
• Vision - Goal and purpose of this project
• Artifact - Any object made, modified, or used by
  people

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
6
Requirements
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
7
Functional Requirements

• R1. The system shall create and store information
  for new user.
• R2. The system shall provide limited access for
  guest.
• R3. The system shall provide log in.
• R4. The customer should login before making
  reservation.
• R5. The system shall provide access of the
  customers reservation.
• R6. The system shall update restaurants
  capacity.
• R7.The system shall keep a record of all the
  information that has been stored.
• R8. The system shall provide access to the
  restaurants menu.
• R9. The system shall accept order online.
• R10. The system shall accept payment online
  through credit card.
• R11. The system shall issue a unique reservation
  number.
• R12. The system shall send an email for
  confirming the reservation.
• 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 reservations
  information.
• R2. It shall take 5 seconds to store information.
• R3. System shall use C language.

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
9
Supplementary Requirement

• The system shall only take reservation of a
  maximum of two hours.
• The system shall only take reservation of a
  maximum of eight people.

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
10
Diagrams
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
11
Use case Diagram
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
12
Use case DiagramUpdate Account
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
13
Include Use Case
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
14
DomainModel
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
15
Class Diagram
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
16
Use Case Specification
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
17
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 The use case starts when the user selects Create New Customer Account. 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. The system creates a new account for the user
Post condition A new account has created for the user.
Alternative Flow Invalid Details Cancel
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
18
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 The alternative flow starts after step 1 of the main flow. The system informs the user that an invalid detail has been entered.
Post condition None
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
19
Alternative Flow Create New Account Cancel
ID PB1.2
Brief Description The user cancels the account creation process.
Primary Actor User
Secondary Actor None
Precondition None
Alternative Flow The alternative flow starts anytime during the process of account creation. The customer selects cancel. The system cancels the account that is being created.
Post condition The new account creation on process has NOT been done.
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
20
Use Case Update Account
ID PB2
Brief Description The user wishes to update an account.
Primary Actor User
Secondary Actor None
Precondition User has to have an account.
Main Flow Use case starts when the user click on Update Account. If the user selects Delete Account 2.1.The system asks the user to enter primary detail thats 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. 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
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
21
Use Case Show Account
ID PB3
Brief Description The system displays user account.
Primary Actor User
Secondary Actor None
Precondition The user has to be logged on.
Main Flow The user selects Show Account. The system asks the user to enter the necessary details. The user enters the details needed. The system displays the details of the account.
Post condition An account has been shown.
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
22
Use Case Log On
ID PB4
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 The use case starts when the user selects Log On. User has to type in username. User has to type in password. While the users 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 users type.
Alternative Flow Invalid Username/ Invalid Password
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
23
Alternative Flow Log On Invalid Username/Password
ID PB4.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 The alternative flow starts after step 3 of the main flow. The system informs the user that an invalid username/password has been entered.
Post condition None
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
24
Use Case Make Reservation/Order
ID PB5
Brief Description The customer makes a reservation.
Primary Actor Customer
Secondary Actor None
Precondition The customer was able to log on.
Main Flow Customer selects the date and time of the reservation. Customer selects number of person for the reservation. The customer clicks search. 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. The system prompts the next user interface. The customer enters the necessary details. The customer click on next. 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
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
25
Alternative Flow Make Reservation/Order Makes Order Online
ID PB5.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 The alternative flow starts after step 8 of the main flow. The customer clicks on the food and drinks that she/he would like to order. The system shall inform the customer that the order has been made.
Post condition None
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
26
Alternative Flow Make Reservation/Order Payment
ID PB5.2
Brief Description The customer wants to pay online.
Primary Actor Customer
Secondary Actor None
Precondition The customer has made an order.
Alternative Flow The alternative flow starts after step 9 of the main flow. The system prompts a user interface where the customer can enter his/her credit card number. 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
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
27
Alternative Flow Make Reservation/Order Payment Invalid credit card
ID PB5.2.1
Brief Description The customers credit card is invalid or deactivated.
Primary Actor Customer
Secondary Actor None
Precondition The customer has entered an invalid credit card number.
Alternative Flow The alternative flow starts after step 2 of the alternative flow Payment. 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
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
28
Alternative Flow Make Reservation/Order Cancel
IDPB5.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 The alternative flow can begin anytime. The customer clicks on cancel. The system informs the customer that the reservation has been cancelled.
Post condition A reservation has NOT been made.
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
29
Use Case Access To Reservation
IDPB6
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 The management selects time and date of reservation that he/she wants to access. The management clicks on Show Reservation The system asks the management to select the table reserved. The management selects the table. The management click on next. The system shows the details of the reservation. The management click on Orders 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
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
30
Extension Use Case Print Order
ID PB7
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 The management selects Print Order. The system print out the order.
Segment 1 Post condition An Order has been printed.

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
31
Alternative Flow Access To Reservation Log Out
IDPB6.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 The alternative flow starts anytime. The system closes the window and return to the main page.
Post condition None
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
32
Use Case Cancel Reservation
ID PB8
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 The customer selects Cancel Reservation The system asks the customer to enter necessary details. The customer enters necessary details. The system searches for the reservation and cancel it. The system informs the customer that the reservation has been cancelled. The customer clicks on Done.
Post condition The system has cancelled a reservation.
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
33
Use Case Cancel Order
ID PB9
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 The customer selects Cancel Order The system asks the customer to enter necessary details. The customer enters necessary details. The system searches for the order and cancel it. The system informs the customer that the order has been cancelled. The customer clicks on Done.
Post condition The system has cancelled an order.
Alternative Flow None
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
34
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

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
35
Risk ID R001 Classification 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. Description Possibility of losing booking/ reservation if not noticed the first time. A risk that has something to do with the running program. 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. First Indicator None so far. First Indicator None so far.
Mitigation Approaches Keeping track of the all the details of reservation from the beginning for comparison. Mitigation Approaches Keeping track of the all the details of reservation from the beginning for comparison. 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 Current Status Current Status
Contingency Plan Contingency Plan Contingency Plan
Trigger for Contingency Plan Trigger for Contingency Plan Trigger for Contingency Plan
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
36
Risk ID R002 Classification Reliability Report Date 24 February 2006
Description Not to be able to rely on the system completely. Description Not to be able to rely on the system completely. 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. First Indicator None so far. First Indicator None so far.
Mitigation Approaches Keeping track of the all the details of reservation from the beginning for comparison. Mitigation Approaches Keeping track of the all the details of reservation from the beginning for comparison. 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 Current Status Current Status
Contingency Plan Contingency Plan Contingency Plan
Trigger for Contingency Plan Trigger for Contingency Plan Trigger for Contingency Plan

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
37
Analysis and DesignWorkflow
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
38
Phase Plan And Software Development Plan

• Finalized class diagram
• Activity diagram
• Sequence diagram

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
39
Appendix

• RUP Anthony Crain
• Rational up methods (RUP Iteration Planning
  2004)
• http// www-128.ibm.com/developer works
  /rational/litray/5335.html
• RMP Risk management Plan
• http//www.processimpact.com/process_assets/risk_m
  gmt_plan_template_doc.

Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
40
Prototype
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
41
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
42
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
43
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
44
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
45
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
46
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
47
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh
48
The End
Kaleem Ullah, Melody Parsa,
Charmie Dela Cruz, Setareh Vali
MeSeKaCh