Scribd
Upload
39 views3 pages

Faculty of Computer Science and Information Technology: Prepared For

This document contains an assignment for a software design and architecture course. It includes instructions to (1) draw a use case diagram for an online restaurant booking system, (2) provide a description of a "happy day" use case for making a booking assuming availability, and (3) identify three additional "alternate flows" that could occur, such as if the restaurant is full or the customer does not confirm.

Uploaded by

mohandass selvakumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
39 views3 pages

Faculty of Computer Science and Information Technology: Prepared For

This document contains an assignment for a software design and architecture course. It includes instructions to (1) draw a use case diagram for an online restaurant booking system, (2) provide a description of a "happy day" use case for making a booking assuming availability, and (3) identify three additional "alternate flows" that could occur, such as if the restaurant is full or the customer does not confirm.

Uploaded by

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

FACULTY OF COMPUTER SCIENCE AND INFORMATION

TECHNOLOGY

ISS 2263
Software Design & Architecture

ASSIGNMENT 1

PREPARED FOR :
AZALIZA BINTI ZAINAL

PREPARED BY :
KEESHANRAJ A/ L BALASINGAM (4141006271)

DATE OF SUBMISSION :
11/3/2015

A) Draw a use case diagram identifying the Actors and Use Cases required for
the Pierres restaurant on-line system

B) Provide an outline happy day use case description for making a booking through the
on-line booking system. This scenario SHOULD assume that the restaurant has
availability and therefore a booking can be made

Use case: Make booking


1. Customer make a booking.
2. Customer request date and number of guest in booking.
3. System checks availability on the booking date.
4. If there is availability, system confirms availability and requests further booking
details.
5. System prompts customer to confirm booking details.
6. Customer confirms the booking details.
7. System confirms the booking.

C) For the use case description described in part a), identify an additional three alternate
flows that COULD be invoked from the basic flow
I.
If the restaurant is full - provide an alternate date to customer.
II.
If the restaurant is full - add customer booking into waiting list.
III.
If customer not confirms - The booking will be cancelled.

You might also like