Casual Format Use Case

College of Business | worldwide.erau.edu

All rights are reserved. The material contained herein is the copyright property of Embry-Riddle Aeronautical University, Daytona Beach, Florida, 32114. No part of this material may be reproduced, stored in a retrieval system or transmitted in any form, electronic, mechanical, photocopying, recording or otherwise without the prior written consent of the University.

Requirements Definition

Functional Requirements

1. Functional requirement #1: Seats booking management

1.1. The system should allow user registration.

1.2. The system user interface should be easy to understand.

1.3. The system should notify customers on availability of seats reservations.

2. Functional requirement #2: Payment Management

2.1. The system allows the customer to choose the type of class of the seat.

2.2. The system allows customer to choose the mode of payment.

2.3. The system processes the payments of customers.

Non-Functional Requirements

1. Operational

1.1. The system should be compatible with both PCs and mobile devices to allow customers’ booking at any time.

1.2. The system should run in all browsers.

2. Performance

2.1. The system should have a response time of two seconds maximum.

2.2. The system should update availability of seats every minute.

3. Security

3.1. The system should ensure customer’s accounts and data are safe.

3.2. The system should ensure that users access exactly what they are intended to access.

4. Cultural & Political

4.1. The company requires that all the gadgets needed should be purchased from HP.

4.2. The system should offer translation functionality to enable usage of global customers.

Page 5 of 5