0% found this document useful (0 votes)
21 views6 pages

Milestone#2

The document discusses software engineering and choosing an agile methodology for developing a restaurant reservation application. It provides reasons for selecting agile such as flexibility, improving customer satisfaction, reducing development time, and increased collaboration. It also includes use cases for the customer and restaurant actors.

Uploaded by

9xcwr5h9c4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views6 pages

Milestone#2

The document discusses software engineering and choosing an agile methodology for developing a restaurant reservation application. It provides reasons for selecting agile such as flexibility, improving customer satisfaction, reducing development time, and increased collaboration. It also includes use cases for the customer and restaurant actors.

Uploaded by

9xcwr5h9c4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Software Engineering

Dr. Mashael Alsulami

Milestone #2

Team members:

Student name ID

Atheer Hamad Al-juaed 44006351

Dana hamad alrogi 44106777

Shaima hassan alharthi 44101435

Dhay masheal almalky 44105336

Muradi khaled almutairiy 44100871


Determine the software methodology you will use. Give all the necessary
justifications for your decision:

In software development there are many methods and methodologies that can be
used to manage reservations in active restaurants and connect customers to
available restaurants within a time range. The best type for this applications is Agile,
which is known for its flexibility and iterative approach.

What are the reasons to choose Agile:

Agile methodology is a popular software development approach that emphasizes


flexibility, collaboration, and rapid iteration. In the context of restaurant reservation
software, Agile methodology can be used to quickly develop and test new features,
respond to changing customer needs, and improve the overall user experience.

For example, Agile methodology can help restaurant reservation software:

Flexibility: Restaurants often have changing requirements due to several factors,


including variations in seasonal menus, during special events, or availability of
traditional dishes by region. This agile methodology allows the flexibility to adapt to
these changes quickly and without disrupting the development process.

Improve customer satisfaction: Using Agile methodology, developers can quickly


identify and address issues with the reservation process, such as long wait times or
reservation errors. This can help improve the overall customer experience and
increase customer satisfaction.

Reduce development time: Agile methodology focuses on rapid iteration and


constant feedback, which can help reduce the time required to develop new
features or fix bugs. This can help restaurant reservation software stay competitive
by responding quickly to changing market conditions.

Increased Collaboration: Agile methodology emphasizes collaboration between


developers, stakeholders, and customers. This can help ensure that the final
product meets the needs of all stakeholders and aligns with overall business goals.

Quality Improvement: The Agile methodology focuses on continuous testing and


providing feedback, which can help identify and fix problems early in the
development process. This can help improve the overall quality of the final product.
Actor: CUSTOMER
Use Case 1: Account Creation
1. The client opens the application and selects the option to create a new account.
2. The application prompts the client to enter their personal information such as name, email
address, and password.
3. The client provides the required information and submits the registration form.
4. The application verifies the entered information and creates a new account for the client.
5. The application displays a success message and redirects the client to the login page.

Use Case 2: Login


1. The client opens the application and selects the login option.
2. The application presents the client with a login form, requesting their email address and
password.
3. The client enters their registered email address and password.
4. The application verifies the entered credentials and grants access to the client's account.
5. The application redirects the client to the main dashboard.

Use Case 3: Search for Nearby Restaurants


1. The client logs into their account and accesses the main dashboard.
2. The client selects the "Search for Restaurants" option.
3. The application displays a search bar and prompts the client to enter their location or
enable location services.
4. The client enters their location or allows the application to access their current location.
5. The application retrieves a list of nearby restaurants based on the provided location.
6. The application displays the list of restaurants with relevant details such as name, cuisine
type, and ratings.

Use Case 4: Restaurant Testing


1. The client selects a restaurant from the list displayed in the previous use case.
2. The application presents detailed information about the selected restaurant, including
menu, reviews, and photos.
3. The client explores the menu and reviews to gather information about the restaurant.
4. The client decides to test the restaurant and selects the "Make a Reservation" option.

Use Case 5: Reservation Confirmation


1. The client is redirected to the reservation page.
2. The application prompts the client to select the date, time, and number of people for the
reservation.
3. The client provides the required details and selects the "Confirm Reservation" option.
4. The application checks for availability and confirms the reservation.
5. The application displays a confirmation message with reservation details, including date,
time, and restaurant information.

Use Case 6: Reservation Cancellation


1. The client logs into their account and accesses the reservation section.
2. The client selects the reservation they wish to cancel.
3. The application displays the reservation details and provides a "Cancel Reservation"
option.
4. The client selects the "Cancel Reservation" option.
5. The application prompts the client for confirmation.
6. The client confirms the cancellation, and the application cancels the reservation.
7. The application displays a cancellation confirmation message.
Actor: Restaurant's:
Use Case 1: Customer Create an Account include user and credit cards information:
1. The customer opens the restaurant booking app.
2. The customer is presented with a login or signup screen.
3. The customer selects the login option.
4. The customer provides their personal information, including their name, email address, and
phone number.
5. The customer also enters their credit card information for payment.
6. The app verifies the information.
7. The customer is now logged in and ready to use the app.

Use Case 2: Customer Chooses a Restaurant and Views the Menu:


1. The customer logs into the restaurant booking app.
2. The customer is presented with a list of nearby restaurants or a search feature.
3. The customer selects a restaurant from the list.
4. The app displays the restaurant's details, including its name, location, and average ratings.
5. The customer can extend the restaurant's information to view its menu.
6. The menu displays various food and drink items with descriptions and prices.
7. The customer can browse the menu, make selections, and view prices.

Use Case 3: Customer Chooses a Restaurant, Views Available Tables and Times:
1. The customer logs into the restaurant booking app.
2. The customer selects a restaurant from the list or search results.
3. The app displays the restaurant's details, including its name and location.
4. The customer can extend the restaurant's information to view available tables and time slots.
5. The app provides a list of available tables for reservation and their seating capacities.
6. The customer can also see the available time slots for reservations.
7. The customer can choose a specific table and time slot for their booking in addition to the
number of chairs on the table.

Use Case 4: Customer Chooses a Restaurant and Books an Available Table


1. The customer logs into the restaurant booking app.
2. The customer selects a restaurant from the list or search results.
3. The app displays the restaurant's details, including its name and location.
4. The customer extends the restaurant's information to view available tables and time slots.
5. The app provides a list of available tables and their seating capacities.
6. The customer selects a preferred table and a suitable time slot for their reservation.
7. The app prompts the customer to confirm their booking and provides a summary of the
reservation, including the date, time, table number, and total cost.
8. The customer confirms the booking, and the app processes the payment using the previously
saved credit card information.
9. The app generates a booking confirmation, which is sent to the customer's email or available
in the app for reference.
10. The customer's booking is now confirmed, and they can manage their reservations through
the app
Actor: System
Use Case1: Customer Confirms Reservation and Pays Deposit
1. Customer logs into the Booking Restaurants app using their credentials.
2. The system presents the customer with a list of available restaurants and the option to make a
reservation. The customer selects a restaurant they want to book.
3. The system displays the details of the selected restaurant, including the available time slots for
reservations and the estimated cost.
4. The customer selects their preferred reservation date and time from the available options.
5. The system prompts the customer to provide the number of people in their party and any
special requests, such as dietary restrictions or seating preferences.
6. The customer enters the required information and reviews their reservation details, including
the total cost.
7. The system then asks the customer if they would like to confirm the reservation and proceed
with the booking.
8. The customer confirms their reservation, and the system calculates the required deposit based
on the restaurant's policy, which may be a percentage of the total cost or a fixed amount.
9. The system requests the customer's payment information, such as credit card details, and
securely processes the deposit payment.
10. After successful payment, the system sends a confirmation email to the customer's registered
email address. The email includes the reservation details, the amount paid as a deposit, and a
summary of the reservation terms and conditions.

Use Case2: Customer Receives Reservation Confirmation Email

1. The customer, after confirming the reservation and making the deposit payment, receives a
confirmation email from the system in their inbox.
2. The email subject line indicates that it's a reservation confirmation from the restaurant.
3. The email contains the following information:
- Reservation date and time
- Number of people in the table
- Special requests and preferences
- Restaurant name and address
- Total cost of the reservation
- Amount paid as a deposit
- Reservation terms and conditions
4. The customer reviews the email to ensure that all the information is accurate and that the
reservation is in order.
5. If the customer has any questions or concerns, they can contact the restaurant or the
customer support provided by the app using the contact details provided in the email.
6. The customer can also save or print the email for their reference.
These use cases provide a detailed scenario for how a customer interacts with the restaurant
booking app, from creating an account to making a reservation at their chosen restaurant and
this scenario outlines how the booking restaurants app allows customers to confirm their
reservations, make deposit.

You might also like