inception phase

Inception Inception

PhasePhase

Mesekach Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali

S

C

K

M

MeSeKaCh

S

C

K

M

Vision and business caseVision and business case

To develop a booking system for the To develop a booking system for the restaurant restaurant

Improve the hand written booking systemImprove the hand written booking system Executive summary:Executive summary:

TheThe vision behind this project is to vision behind this project is to develop, implement and test a working develop, implement and test a working digital booking system which can replace digital booking system which can replace the old hand writing booking the old hand writing booking system.system.

Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh ValiMeSeKaCh

Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali

S

C

K

M

BoundariesBoundaries

Software boundary – Payment Software boundary – Payment subsystem is not supposed to be subsystem is not supposed to be implented in this particular project.implented in this particular project.

Hardware boundary – Project will be Hardware boundary – Project will be developed for windows flatform.developed for windows flatform.

MeSeKaCh


S

C

K

M

RequirementsRequirementsWorkflowWorkflow

MeSeKaCh


S

C

K

M

GlossaryGlossary Menu - Order itemsMenu - Order items Booking Manager - Control class/server Booking Manager - Control class/server

Order Number - Specific order a unique Order Number - Specific order a unique

customer has madecustomer has made Vision - Goal and purpose of this projectVision - Goal and purpose of this project Artifact - Artifact - Any object made, modified, or Any object made, modified, or

used by people used by people

MeSeKaCh


S

C

K

M

RequirementsRequirements

MeSeKaCh

S

C

K

M

Functional RequirementsFunctional 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 R7.The system shall keep a record of all the information that has

been stored. 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 R12. The system shall send an email for confirming the

reservation.reservation. R13. It shall be able to print the reservation information for the R13. It shall be able to print the reservation information for the

user.user.


Non-Functional Non-Functional RequirementsRequirements

R1. It shall take 5 seconds to view R1. It shall take 5 seconds to view reservation’s information.reservation’s information.

R2. It shall take 5 seconds to store R2. It shall take 5 seconds to store information.information.

R3. System shall use C++ language.R3. System shall use C++ language.


S

C

K

M

MeSeKaCh


S

C

K

M

Supplementary Supplementary Requirement Requirement

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

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

MeSeKaCh


S

C

K

M

DiagramsDiagrams

MeSeKaCh


S

C

K

M

Use case Use case DiagramDiagram

BookingSystem

LogIN

Customer

MakeReservation/Order

CancelReservation

Management

AccessToOrders______________

Orders Made

«subsystem»Payment

«extends»

PrintOrder

CancelOrder

CreateNewAccount

ShowAccount

*

*

Update Account

MeSeKaCh


S

C

K

M

Use case Diagram:Use case Diagram:Update AccountUpdate Account System

CustomerManagement

Delete Account

Edit Account

MeSeKaCh


S

C

K

M

Include Use CaseInclude Use Case

User

Delete Account

Edit Account

Show Account

Find Account

MeSeKaCh


S

C

K

M

User

Customer

LogO

Employee

Booking Manager

Paymen Menu

DomainDomainModelModel

MeSeKaCh


S

C

K

M

-Order Number-Menu Order-Price

Menu

-Customer ID-Maneger ID-Order-Table ID-date-Time-Waiter-Number or name

Booking Manager

-CustomerID-Name-Mobile or Phone Nr.-E-mail

Customer

-Order-Number-Amount-Bool

Payment

-NameID-Name-Mobil-E-mail

Employee

1 1

0..*

1

10..*

1

1

-ID-Bool

LogOn

0..*

1

User

Class Class DiagramDiagram

MeSeKaCh

M C

S

K


Use Case SpecificationUse Case Specification

M C

S

K


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


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


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


S

C

K

M

Alternative Flow: Create New Account: Cancel

ID: PB1.2

Brief Description: The user cancels the account creation process.

Primary Actor: User


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.


MeSeKaCh


S

C

K

M

Use Case: Update Account

ID: PB2

Brief Description: The user wishes to update an account.

Primary Actor: User


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 needed2.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.


MeSeKaCh


S

C

K

M

Use Case: Show Account

ID: PB3

Brief Description: The system displays user account.

Primary Actor: User


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.


MeSeKaCh


S

C

K

M

Use Case: Log On

ID: PB4

Brief Description: The Customer shall be able to log on.

Primary Actor: User (Management and customer)


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


S

C

K

M

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


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.



MeSeKaCh


S

C

K

M

Use Case: Make Reservation/Order

ID: PB5

Brief Description: The customer makes a reservation.

Primary Actor: Customer


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


S

C

K

M

Alternative Flow: Make Reservation/Order : Makes Order Online

ID: PB5.1

Brief Description: The customer wants to make an order online.



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.



MeSeKaCh


S

C

K

M

Alternative Flow: Make Reservation/Order : Payment

ID: PB5.2

Brief Description: The customer wants to pay online.



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.


Alternative Flow: Invalid credit card

MeSeKaCh


S

C

K

M

Alternative Flow: Make Reservation/Order : Payment : Invalid credit card

ID: PB5.2.1

Brief Description: The customer’s credit card is invalid or deactivated.



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.



MeSeKaCh


S

C

K

M

Alternative Flow: Make Reservation/Order: Cancel

ID:PB5.3

Brief Description: The customer wants to cancel the reservation on process.



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.


MeSeKaCh


S

C

K

M

Use Case: Access To Reservation

ID:PB6

Brief Description: The management looks at the reservation that has been made.

Primary Actor: Management


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.


Alternative Flow: Log out

MeSeKaCh


S

C

K

M

Extension Use Case: Print Order

ID: PB7

Brief Description:Segment 1: The management staff selects to print out the order that has been made.



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


S

C

K

M

Alternative Flow: Access To Reservation: Log Out

ID:PB6.1

Brief Description: The management selects to log out.



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.



MeSeKaCh


S

C

K

M

Use Case: Cancel Reservation

ID: PB8

Brief Description: The Customer wishes to cancel reservation that has been done.



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.


MeSeKaCh


S

C

K

M

Use Case: Cancel Order

ID: PB9

Brief Description: The Customer wishes to cancel order that has been done.



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.


MeSeKaCh


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


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.

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


Risk ID: R002 Classification: 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


S

C

K

M

Analysis Analysis and Designand DesignWorkflowWorkflow

MeSeKaCh


S

C

K

M

Phase Plan And Software Phase Plan And Software Development PlanDevelopment Plan

Finalized class diagram Finalized class diagram Activity diagramActivity diagram Sequence diagramSequence diagram

MeSeKaCh


S

C

K

M

AppendixAppendix

[[RUP] Anthony Crain : RUP] Anthony Crain :

Rational up methods (RUP Iteration Planning Rational up methods (RUP Iteration Planning 2004)2004)

http:// www-128.ibm.com/developer works http:// www-128.ibm.com/developer works /rational/litray/5335.html/rational/litray/5335.html

[RMP] Risk management Plan :[RMP] Risk management Plan :

http://http://www.processimpact.com/www.processimpact.com/process_assets/process_assets/risk_mgmt_plan_template_doc.risk_mgmt_plan_template_doc.

MeSeKaCh


S

C

K

M

MeSeKaCh

PrototypePrototype


S

C

K

M

MeSeKaCh


S

C

K

M

MeSeKaCh

The End

inception phase

Documents

charmie dela cruz

melody parsa

update account kaleem

setareh valimesekachvision

reservation information

working digital booking

customers reservation

unique reservation number