SRS Document

116  Download (0)

Full text

(1)

SWE 215 – Software Requirements Engineering

Term 091

Car Rental System

(CRS)

www.shaeqkhan.com

January 28

2010

(2)

Page 2

Table of Contents

1. Introduction ... 6 i. Purpose: ... 6 ii. Scope: ... 6 iii. References: ... 7 iv. Overview: ... 7 2. Overall Description ... 9 i. Product Perspective ... 9

ii. Product Features and User Requirements ... 11

iii. User and User Characteristics... 13

iv. General Constraints ... 14

v. Assumption and Dependencies ... 14

3. System Architecture ... 16

4. System Requirements... 18

i. Use Case Diagrams ... 18

 Receptionist ... 18  Accountant... 19  Dispatch Department ... 20  Fleet Inspection ... 21  Administrator ... 22  Branch Manager ... 23

ii. Use Case Description ... 24

1. Book Car ... 24 2. Modify Booking ... 26 3. Cancel Booking ... 27 4. Search Booking ... 28 5. Add Customer ... 29 6. Modify Customer ... 31 7. View Customer ... 32 8. Search Customer ... 33 9. Receive Payment... 34 10. Transfer Fund... 35 11. Settle Bill ... 36 12. Issue Coupon ... 37 13. Receive Car ... 38 14. Dispatch Car... 40 15. Update Record ... 41 16. Issue Form ... 42 17. Report Repair ... 43

(3)

19. Update Received Car ... 45

20. Update Car Status ... 46

21. Add Account ... 47 22. Delete Account ... 48 23. Modify Account ... 49 24. Search Account ... 51 25. Backup System ... 52 26. Add Category ... 53 27. Modify Category ... 54 28. View category ... 55 29. Delete Category ... 56 30. Generate Report ... 57 31. Remove Car ... 58 32. Modify Car ... 59 33. Add Car ... 60 34. Delete Customer ... 61

iii. Non-Functional Requirement: ... 62

5. Analysis Model ... 64 i. Interaction Diagrams ... 64 1. Book Car ... 64 2. Modify Booking ... 65 3. Cancel Booking ... 66 4. Search Booking ... 67 5. Add Customer ... 68 6. Modify Customer ... 69 7. View Customer ... 70 8. Search Customer ... 71 9. Receive Payment... 72 10. Transfer Fund... 73 11. Settle Bill ... 74 12. Issue Coupon ... 75 13. Receive Car ... 76 14. Dispatch Car... 77 15. Update Record ... 78 17. Report Repair ... 80 18. Search Car... 81

19. Update Received Car ... 82

20. Update Car Status ... 83

21. Add Account ... 84

(4)

Page 4 23. Modify Account ... 86 24. Search Account ... 87 25. Backup System ... 88 26. Add Category ... 89 28. View Category ... 91 29. Delete Category ... 92 30. Generate Report ... 93 31. Remove Car ... 94 32. Modify Car ... 95 33. Add Car ... 96 34. Delete Customer ... 97

ii. Class Diagram ... 98

iii. Data Dictionary ... 99

1. Category ... 99

2. Booking ... 100

3. Car... ...102

4. Car History ... 103

6. Customer History ... 105

6. External Interface Requirements ... 107

i. User Interface Screens ... 107

1. Login Screen ... 107 2. Add Customer ... 108 3. Add Category ... 109 4. Add Car ... 110 5. Add Account ... 111 6. Issue Coupon ... 112 7. Dispatch Car ... 113 8. Book Car ... 114 7. Evolution ... 116

i. Assumptions on which system is based ... 116

(5)
(6)

Page 6

1. Introduction

i.

Purpose:

 This document contains the software requirements for the Car Rental System CRS. The main purpose of a Car Rental System to be implemented is to manage information about Cars, Customers and the system users related to the company.

 This is the first version of the SRS document. The purpose of this document is to state all system requirements clearly for usage in the development stages ahead.

 This document is meant to be viewed by the project development team, users and the stakeholders. All requirements for the system have been stated clearly in the document and this is used to make sure that everyone related to the system directly or indirectly understands all requirements stated in this document.

ii.

Scope:

This document covers the entire system and all its subparts. The purpose of this system is as follows:

Efficiency:

This system provides quick addition, deletion or search for various types of data which are a part of the system. This decreases the process time for employees and manual search work that could take hours can be done in just a few seconds or minutes.

Accurate Records:

There is no fear of manipulation of records by unauthorized personnel. All records stored in the system are protected. Files in storage may catch fire or be spoilt in water. But data storage in repositories reduces those risks.

Accountability:

Any transaction made through the system is kept track of and in case anything goes wrong with customer dealings, the fault can be traced back to the origin very easily.

Generating Reports:

The system is capable of producing weekly and monthly reports on cars, customers and system users.

(7)

iii.

References:

 Dean Leffingwell and Don Widring, “Managing Software Requirements: A Use Case Approach”, Addison-Wesley, 2004.

 Sommerville book.

iv.

Overview:

In the document, the following things will be discussed ahead –

 Overall Description

o The perspective of the product

o Product Features and User Requirements o Users and user characteristics

o General Constraints

o Assumption and Dependencies

 System Architecture

 System requirements o Use case diagrams o Use case descriptions

o Non functional requirements

 Analysis Model

o Interaction Diagram o Class Diagram o Data dictionary

 User Interface Screens

 Evolution

o Assumption on which system is based o Anticipated changes

(8)

Page 8

(9)

2. Overall Description

The main purpose of this document is to give details about what the user can expect from the Car Rental System (CRS). This document provides an important overview of the system according to the requirements that have been given to us during the requirement analysis for this Car Rental System (CRS).

In the next section, we introduce product perspective followed by description of product features and user requirements in section 2. User and user characteristic in section 3 followed by general constrains in section 4. In section 5 we have assumptions and dependencies.

i.

Product Perspective

Our company has been handed over the task to carry out the requirements analysis to implement a

Car Rental System (CRS). We want this software to completely be a front desk system and hence

will only be used by the salespeople and an Branch manager and administrator. We have realized that there are three ways to implement the Car Rental System (CRS) and they are stated as follows -

The existing software at the company can be upgraded to form the new Car Rental System

(CRS).

A new Car Rental System (CRS) can be created from scratch.

 We can follow the Component based development technique to create the system from scratch.

We believe that the best way to implement the Car Rental System (CRS) is to create a new one. The reasons are as follows –

 In case we plan to upgrade the existing system, then we will have to work on integrating the system with a legacy system database. This might create problems for us since experts in the legacy system are not readily and cheaply available.

 We will be able to create a system of better quality. This will be possible if we review the faults in the old system and learn from the mistakes made during the various processes that were involved to create the old system.

 The new system will have better performance due to usage of new and time efficient data searching algorithms which will increase the efficiency of the workplace.

 The new system will provide a new user friendly Graphic User Interface (GUI) which will also help to increase the efficiency of the work place.

 The new system will be compatible with a new database that will be created along with it. A new database has to be created due to the increase in the amount and type of information that has to be stored.

(10)

Page 10

 The new system will be able to undergo evolution in a much simpler way and will be more adaptable to the changing systems. The upcoming changes in the near future will be predicted and the system will be designed in a way to adapt to the changes that will occur over the years.

Figure 1: The above diagram shows the actors and the subsystems contained in the Car Rental System.

The system allows the stake holders to run an efficient business by providing company reports, stock inventory and sales information data. All these functionalities of the system provided in a timely and organized way will help the business to expand to generate more revenue and prevent losses.

(11)

ii.

Product Features and User Requirements

The following are the features of the product –

User Account Management:

The system will allow every Receptionist, Accountant, Fleet inspection and Dispatch to have a different account to login from. This will keep a record of their work time without them having to enter it every time they leave or enter the workplace.

Sales Record system:

The system will allow all the salesmen account to keep a record of the sales that have been made by the account for the week in order to calculate the commission and monthly to calculate the bonus to be awarded by the company.

System Backup:

The system will have a 24 hour backup to record car rental applications from users in case the server goes down.

High system security:

The system will employ a fulltime high security antivirus and a secure network so that the system cannot be illegally modified or hacked into.

Car Information system:

This system gives the ability to the company to keep track of the information on all the cars that are available in the branch’s stock. All relevant information related to the car such as colour, license plate, registration, model number, insurance etc. is stored in the system database. It will record the cars ages and update their condition and rent life. The system will show the car’s status (whether under maintenance, available or rented). The system will provide information about the rate of rent for a car for different periods of time (weekdays, weekends, holidays, Umrah).

User Information System:

This system gives the ability to the company to keep track of the information on the customers in order to classify their association with the company. All customers will be classified according to the frequency with which they rent cars and offer them satisfactory discounts for usage.

Emergency Issue System:

In case of emergency, if a car is not available, the Receptionist, Accountant, Fleet inspection and Dispatch can view the inventory of other branches and issue a car.

(12)

Page 12

Bank to Branch Link System:

When a customer will pay using a bank card rather than cash, it is necessary that a link is always maintained between the branch and bank for successful transaction.

Data Backup System:

In case the system goes down due to server crashes or power failure or any other calamity, all operations are being run such as updating data, carrying requests etc. will be saved to a backup system. All of this will then be copied on to the original database as soon as the system is up and running.

The user requirements for the Car Rental System (CRS) has been listed as follows -

Branch manager:

1. The system shall allow Branch manager to add, modify, search and delete a car. 2. The system shall allow Branch manager to add, modify, view and delete a category.

3. The system shall allow Branch manager to manager to add, modify, view, search and delete a customer.

4. The system shall allow Branch manager to generate reports.

Administrator:

1. The system shall allow administrator to add, modify, search and delete an account. 2. The system shall allow administrator to backup the system.

Receptionist:

1. The system shall allow receptionist to book a car, modify, search and cancel booking. 2. The system shall allow to receptionist to add, modify, view, search and delete a customer.

Accountant:

1. The system shall allow to accountant to receive payment.

Fleet Inspection:

1. The system shall allow to fleet inspection to update received car. 2. The system shall allow to fleet inspection to report repair.

Dispatch Department:

1. The system shall allow dispatch department to receive a car. 2. The system shall allow dispatch department to dispatch a car.

(13)

iii.

User and User Characteristics

The main people who have been identified as regular system users are as follows –

1. Branch Manager 2. Administrator. 3. Receptionist 4. Accountant 5. Fleet Inspection 6. Dispatch Department

The users can be classified according to their frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience they have to the Car Rental System (CRS).

Branch manager and administrator are supposed to have the following characteristics –

o On the whole, Branch manager and administrator spend comparatively lesser time than others on the system. Usually they would access the system when they are required to make reports or something else.

o They should have high technical expertise. They have to be fluent in the system usage and should be well aware of all the system functionalities.

o Branch manager and administrator have access to all security levels as they have to access and maintain the system occasionally.

o Branch manager and administrator should have experience in handling a system of this domain. He must be able to identify errors caused due to improper data entries.

Receptionist, Accountant, Fleet Inspection and Dispatch Department supposed to have the

following characteristics –

o They spend the maximum amount of time on the system in the form of entering information, updating it or deleting the information.

o They are not required to have technical expertise. The most they would need is to be computer literate to understand the working of the system and use it efficiently.

o They have very low security access. They cannot access quite a few functionalities of the system except the one’s they really have to use.

o They should have good communication skills and even if they have no experience in system usage, it’s not a big problem.

(14)

Page 14

iv.

General Constraints

These are some of the constraints that can be faced by the Car Rental System (CRS) –

 Schedule and Resource Constraints

o Time can be listed as a constraint. We are expected to finish this SRS document within 4 months with distractions in between due to the time demanded by the other courses.

o There may be budget constraints where the allocated amount for implementation might not be enough.

o To understand the things that were missing from the previous software, we may need the old requirements documents to identify the features that are required now. There is a possibility that the old system documents have been damaged due to improper storage or misplaced.

 Political Constraints

o It may be a long procedure to acquire access to the Ministry database for customer identification.

 Technology Constraints

o The branch may house defective hardware which can delay the deployment of our system.

v.

Assumption and Dependencies

We have made the following assumptions to the development of the Car Rental System (CRS) –

 We assume that the development team has all the software’s and tools that will be required to complete this project on time.

 We assume that at the time of the system deployment, the branches will have computers with the minimum system requirements as per required by the software for efficient runtime.

 We assume that our project team has been finalized and no new member will be added nor a present member will leave the group in the middle of the project.

 We assume that all the requirements we get from our sources are correct and achievable. These are a few dependencies we have for the system –

 The system is based dependent on ministry database.

 The system has efficient run time on Windows platform.

(15)
(16)

Page 16

3. System Architecture

(17)
(18)

Page 18

4. System Requirements

i.

Use Case Diagrams

Receptionist

(19)

Accountant

(20)

Page 20

Dispatch Department

(21)

Fleet Inspection

(22)

Page 22

Administrator

(23)

Branch Manager

(24)

Page 24

ii.

Use Case Description

1. Book Car

Use Case Number 1

Use Case Name Book Car

Author/Source Abdulaziz Alamoudi

Date of Creation November 10, 2009

Precondition(s) The user has logged in to the system.

Successful Post Condition The car is booked for the customer and a booking ID is

generated.

Actors Receptionist

Priority High

Related Use Cases 2. Modify booking. 3. Cancel Booking. 4. Search Booking. 5. Add customer. 6. Modify customer. 7. View customer. 8. Search customer. Basic flow Steps

1 The use case begins when the user selects “Book Car”.

2 The system prompts the user to enter the customer’s file number.

3 The user enters the customer’s file number and clicks “OK”.

 A1: Add Customer.

 A2: Search Customer.

 A3: Modify Customer.

 A4: View Customer.

4 The system displays the booking screen along with the discount offer.

 A5: The user entered an invalid file number.

5  The user selects the type of car in the checkbox that contains:

o Sports car. o SUV.

o Station wagon. o Other car types.

 The user enters the start/end date of car rental.

6 The system displays cars available with the faire per period.

(25)

requests.

8 The system displays a confirmation screen that contains:

 The car rented.

 The start/end date.

 The amount the customer has to pay.

 The discount offered. 9 The user confirms the criteria. 10 The use case ends.

Alternate Flow: A1 (Add Customer)

1 The “Add Customer” use case is executed. 2 The flow goes to step 4 of the primary flow.

Alternate Flow: A2 (Search Customer)

1 The user selects “Search Customer” 2 The “Search Customer” use case is

executed.

3 The flow goes to step 4 of the primary flow.

Alternate Flow: A3 (Modify Customer)

1 The “Modify Customer” use case is executed.

2 The flow goes to step 4 of the primary flow.

Alternate Flow: A3 (View Customer)

1 The “View Customer” use case is executed. 2 The flow goes to primary flow, step 4.

Alternate Flow: A5 (Invalid File Number)

1 The system displays a message that the entered file doesn’t exist.

2 The user confirms the message.

3 The flow returns to step 3 of the primary flow.

Alternate Flow: A6 (No Cars Available)

1 The system displays a message that there are no cars available.

2 The user confirms the message.

3 The flow returns to step 5 of the primary flow.

(26)

Page 26

2. Modify Booking

Use Case Number 2

Use Case Name Modify Booking

Author/Source Abdulaziz Alamoudi

Date of Creation November 17, 2009

Precondition(s) A valid booking must exist in the customer’s file.

Successful Post Condition - The return date of the booked car is changed. - The car booked might be changed.

Actors Receptionist

Priority Medium.

Related Use Cases 4. Search Booking

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user selects “Modify Booking”.

2 The system prompts the user to enter the customer’s booking number.

 A1: Search Booking.

3 The user enters the booking number and clicks “View”.

 A2: Invalid Booking Number. 4 The system displays the booking profile. 5 The user changes the required information:

 Return date.

 Car rented.

6 The system generates a confirmation message.

7 The user confirms the message. 8 The use case ends.

Alternate Flow: A1 (Search Booking)

1 The “Search Booking” use case is executed. 2 The flow goes to the basic flow, step 3.

Alternate Flow: A2 (Invalid Booking Number)

1 The system displays a message that the entered booking number doesn’t exist. 2 The user confirms the message.

(27)

3. Cancel Booking

Use Case Number 3

Use Case Name Cancel Booking

Author/Source Abdulaziz Alamoudi

Date of Creation November 17, 2009

Precondition(s) - The car must be booked.

- The receptionist must enter the booking number.

Successful Post Condition The car booking is canceled. Actors Receptionist

Priority Medium.

Related Use Cases 4. Search Booking

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user enters the customer’s booking number.

 A1: Search Booking.

2 The system displays the booking profile.

 A2: The booking number doesn’t exist.

3 The user cancels the booking.

4 The system generates a confirmation message.

5 The user confirms the message. 6 The use case ends.

Alternate Flow: A1 (Search Booking)

1 The “Search Booking” use case is executed. 2 The flow goes to the basic flow, step 2.

Alternate Flow: A2 (The booking number doesn’t exist)

1 The system displays a message that the entered booking number doesn’t exist. 2 The user confirms the message.

(28)

Page 28

4. Search Booking

Use Case Number 4

Use Case Name Search Booking

Author/Source Abdulaziz Alamoudi

Date of Creation November 17, 2009

Precondition(s) In the case that the customer lost the booking number, the receptionist needs to enter the customers name or mobile number in the required field.

Successful Post Condition The booking file is viewed. Actors Receptionist

Priority Low.

Related Use Cases 2. Modify Booking. 3. Cancel Booking.

Flow of Events Basic Flow Step Number Steps

1 The system prompts the user to enter:

 Customer’s phone number.

 Customer’s driving license number.

 Customer’s name.

2 The user enters the required information. 3 The system displays the profile.

 The booking doesn’t exist. 4 The use case ends.

Alternate Flow: A1 (The booking doesn’t exist)

1 The system displays a message that the booking doesn’t exist.

2 The user confirms the message.

(29)

5. Add Customer

Use Case Number 5

Use Case Name Add Customer

Author/Source Abdulaziz Alamoudi

Date of Creation November 10, 2009

Precondition(s) When a customer wants to book a car and he doesn’t have a previous instantiated account, then the receptionist adds a customer.

Successful Post Condition The customer is added to the system. Actors  Receptionist

 Branch Manager

Priority High.

Related Use Cases 1. Book Car.

6. Modify Customer. 7. View Customer. 8. Search Customer.

Flow of Events Basic Flow

Step Number Steps

1 The use case begins when the user clicks “Add Customer”.

2 The system displays the “New Customer” screen and prompts the user to enter the required information:  Name.  National ID.  Driving License.  Offered Discount.  Address.  Occupation (Job).  Company.

3 The user enters the required information. 4 The system displays a confirmation

message to confirm the criteria.

 A1: The user missed a required area.

 A2: The information already exists. 5 The user confirms the message.

6 The use case ends.

Alternate Flow: A1 (The user missed a required area)

1 The system prompts the user that he didn’t enter required information.

2 The user enters the information.

3 The flow returns to the basic flow, step 4.

Alternate Flow: A2 (The information already exists)

(30)

Page 30

information already exists. 2 The user confirms the message. 3 The system displays the duplicated

information.

4 The user might change the information.

 A3: Search Customer.

5 The flow returns to the basic flow, step 2.

Alternate Flow: A3 (Search Customer)

1 The “Search Customer” use case is executed.

(31)

6. Modify Customer

Use Case Number 6

Use Case Name Modify Customer

Author/Source Abdulaziz Alamoudi

Date of Creation November 10, 2009

Precondition(s) When the customer requests to book a car, he might want to change some of the information existing in his file like a mobile phone or an address.

Successful Post Condition The customer file is modified and the old data is updated. Actors  Receptionist

 Branch Manager

Priority Low.

Related Use Cases 1. Book Car

8. Search Customer

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “Modify Customer” and enters the customer’s file number.

 A1: Search Customer.

2 The system displays the customer’s profile. 3 The user changes the required information

and clicks”OK”.

4 The system displays a confirmation message.

5 The user confirms the message. 6 The use case ends.

Alternate Flow: A1 (Search Customer)

1 The “Search Customer” use case is executed.

(32)

Page 32

7. View Customer

Use Case Number 7

Use Case Name View Customer

Author/Source Abdulaziz Alamoudi

Date of Creation November 10, 2009

Precondition(s) When the customer requests to book a car, the user might want to view the customer’s file to validate specific

information.

Successful Post Condition The customer’s file is displayed to the user. Actors Receptionist

Priority Low.

Related Use Cases 1. Book Car

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “View Customer” in the booking screen. 2 The system displays the customer’s file. 3 The user clicks “OK” when he finishes

checking the file. 4 The use case ends.

(33)

8. Search Customer

Use Case Number 8

Use Case Name Search Customer

Author/Source Abdulaziz Alamoudi

Date of Creation 10 November, 2009

Precondition(s) When the customer requests booking a car in the case that the customer forgot his file number the user will search using the customer’s phone number or name.

Successful Post Condition The system displays the customer’s file to the user. Actors  Receptionist

 Branch Manager

Priority High

Related Use Cases 1. Book Car. 5. Add Customer. 6. Modify Customer.

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user selects “Search Customer”.

2 The system displays a search engine screen that contains the fields:

 Name.

 Driving License.

 National ID.

 Phone Number.

2 The user enters the customer’s searching information name and clicks “Search”. 3 The system displays a message that the file

was found.

 A1: The file is not found. 4 The user clicks on the file icon. 5 The system displays the file. 6 The user clicks “OK”.

7 The use case ends.

Alternate Flow: A1 (The file is not found)

1 The system displays a message that the file is not found.

2 The user confirms the message. 3 The flow returns to basic flow, step 2.

(34)

Page 34

9. Receive Payment

Use Case Number 9

Use Case Name Receive Payment

Author/Source Abdulaziz Alamoudi

Date of Creation 17 November, 2009

Precondition(s) The customer pays the accountant the amount of money required.

Successful Post Condition The accountant issues a coupon for the customer and

settles the bill afterwards.

Actors Accountant

Priority High

Related Use Cases 10.Transfer Fund. 11. Settle Bill. 12. Issue Coupon.

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user enters the booking number.

2 The system displays the booking file along with the payment.

 A1: Settle Bill.

 A2: Issue Coupon.

Alternate Flow: A1 (Settle Bill)

1 The “Settle Bill” use case is executed. 2 The use case ends here.

Alternate Flow: A2 (Issue Coupon)

1 The “Issue Coupon” use case is executed. 2 The use case ends here.

(35)

10. Transfer Fund

Use Case Number 10

Use Case Name Transfer Fund

Author/Source Abdulaziz Alamoudi

Date of Creation 10 November, 2009

Precondition(s) The customer might use a credit card for the payment.

Successful Post Condition The funds are transferred to the bank account. Actors Bank Server

Priority Medium

Related Use Cases 9. Receive Payment

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user establishes a connection with the bank server.

 E1: There is no connection. 2 The user enters the account number and

the payment amount.

3 The system validates the information and sends it to the bank server.

 A1: Invalid Account Number. 4 The bank server receives the information. 5 The funds are transferred.

6 The bank server sends a confirmation message.

7 The user confirms the message. 8 The use case ends.

Alternate Flow: A1 (Invalid Account Number)

1 The system displays a message that the account number doesn’t exist.

2 The flow returns to primary flow step 2.

Error Flow: E1 (There is no connection)

1 The system displays a message that there is no connection with the bank server.

2 The user confirms the message. 3 The use case ends in this position.

(36)

Page 36

11. Settle Bill

Use Case Number 11

Use Case Name Settle Bill

Author/Source Abdulaziz Alamoudi

Date of Creation 17 November, 2009

Precondition(s) The customer must pay the remaining payment when returning the car.

Successful Post Condition The bill is settled and the customer’s file is legally cleared

from any additional payment.

Actors Accountant.

Priority High

Related Use Cases 9. Receive Payment 10. Transfer Fund.

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user selects “Settle Bill”.

2 The system prompts the user to enter the booking number.

3 The user enters the booking number. 4 The system displays the remaining

payment.

 A1: There is no additional payment. 5 The user confirms the bill.

6 The bill is printed. 7 The use case ends.

Alternate Flow: A1 (There is no additional payment)

1 The system displays a message that there is no additional payment.

2 Te user confirms the message. 3 The flow goes to basic flow, step 5.

(37)

12. Issue Coupon

Use Case Number 12

Use Case Name Issue Coupon

Author/Source Abdulaziz Alamoudi

Date of Creation November 17, 2009

Precondition(s) The payment of must be received.

Successful Post Condition The coupon is issued. Actors Accountant

Priority High

Related Use Cases 9. Receive Payment

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “Issue Coupon” after receiving the payment.

2 The system displays the coupon containing the information regarding the rental:

 Car rented.  Rent/Return date.  Coupon Number.  Customer Number.  Booking Number.  Payment.

3 The user clicks “Print Coupon”. 4 The coupon is printed.

(38)

Page 38

13. Receive Car

Use Case Number 13

Use Case Name Receive Car

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) Fleet Inspection has approved the car’s usage by customers.

Successful Post Condition The information about the car’s availability is updated. Actors Dispatch Department

Priority Medium

Related Use Cases 15. Update Record 16. Issue Form

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “Receive Car”.

2 The system prompts the user to enter the customer ID and booking number.

3 The user enters the required information.

A1: Information entered is invalid.

A2: Update record for the car

A3: Customer does not exist.

A4: Invalid Booking number.

4 The system displays a confirmation message.

5 The user confirms the message.

- A5: Customer requests for a copy of

the form 6 The use case ends.

Alternate Flow: A1 (Information entered is invalid)

1 The system displays a message that the information entered by the user is not of the same type of information accepted by the info field.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Alternate Flow: A2 (Update Record for the car)

1 The use case 15 Update Record is executed 2 The flow goes back to basic flow, step 4

Alternate Flow: A3 (Customer does not exist)

1 The system displays a message that the customer with the entered ID does not

(39)

2 The user confirms the message. 3 The use case 8 Search Customer is

executed

4 The flow goes back to basic flow, step 2

Alternate Flow: A4 (Invalid Booking number)

1 The system displays a message that the booking number entered is invalid. 2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Alternate Flow: A5 (Customer requests for a copy of the form)

1 The use case 16 Issue Form is executed 2 The use case ends.

(40)

Page 40

14. Dispatch Car

Use Case Number 14

Use Case Name Dispatch Car

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) Fleet Inspection has approved the car’s usage by customers.

Successful Post Condition The car has been handed over to the customer. Actors Dispatch Department

Priority High

Related Use Cases Issue Form

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “Dispatch Car”.

2 The system prompts the user to enter the customer ID and booking number.

3 The user enters the required information.

A1: Information entered is invalid.

4 The system displays a confirmation message for a valid booking.

A2: Customer does not exist.

A3: Invalid Booking number.

5 The user confirms the message.

6 Use case number 16 Issue form is executed. 7 The use case ends.

Alternate Flow: A1 (Information entered is invalid)

1 The system displays a message that the information entered by the user is not of the same type of information accepted by the info field.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Alternate Flow: A2 (Customer does not exist)

1 The system displays a message that the customer with the entered ID does not exist in the system.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Alternate Flow: A3 (Invalid Booking number)

1 The system displays a message that the booking number entered is invalid. 2 The user confirms the message.

(41)

15. Update Record

Use Case Number 15

Use Case Name Update Record

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) The dispatch department has received the car from the fleet inspection department.

Successful Post Condition The availability status of the car has been updated. Actors Dispatch Department

Priority Medium

Related Use Cases 13 Receive Car

Flow of Events Basic Flow Step Number Steps

1 The use case begins after the user clicks “Recieve Car”.

2 The system prompts the user to enter the category of the car and license plate number.

3 The user enters the required information.

A1: Information entered is invalid.

4 The system displays a confirmation message stating that the car exists in the system.

A2: Car not found.

5 The user confirms the message.

6 The system prompts the user to update the car.

7 The user makes changes in the previous data and saves the changes.

8 The use case ends.

Alternate Flow: A1 (Information entered is invalid)

1 The system displays a message that the information entered by the user is not of the same type of information accepted by the info field.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Alternate Flow: A2 (Car not found)

1 The system displays a message that the car with the entered license plates and under the category does not exist.

2 The user confirms the message.

(42)

Page 42

16. Issue Form

Use Case Number 16

Use Case Name Issue Form

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) The dispatch department has verified the user and checked the availability of the car

Successful Post Condition A form has been issued to the customer Actors Dispatch Department

Priority High

Related Use Cases 13 Receive Car 14 Dispatch Car

Flow of Events Basic Flow Step Number Steps

1 The use case begins after the user clicks “Dispatch Car”.

2 The system retrieves all required information from the database that is required to put in the form.

- A1: Information not found in Database

3 The system generates the form and displays it to the user.

4 The user prints the form for the customer for record.

- E1: Printer out of service. 5 The use case ends.

Alternate Flow: A1 (Information not found in Database)

1 The system displays a message that all essential information for the form was not found in the database.

2 The user confirms the message 3 The use case 6. Modify Customer is

executed

4 The flow goes back to basic flow, step 2

Error Flow: E1 (Printer out of service)

1 The system displays a message that the printer is currently out of service. 2 The user confirms the message. 3 The use case ends.

(43)

17. Report Repair

Use Case Number 17

Use Case Name Report Repair

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) The car has been handed over to the fleet inspection by the dispatch department

Successful Post Condition Any repair done to the car is successfully recorded. Actors Fleet Inspection

Priority Medium

Related Use Cases 18 Search Car

20 Update Car Status

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “Report Repair”.

2 The use case 18 Search Car is executed. 3 The system prompts the user to enter the

cost of repair

4 The user enters the cost of repair.

A1. Cost entered is more than

SR10,000

5 The system displays a message that the cost entered has been added to the car’s record.

6 The user confirms the message.

7 The system runs the use case 19 Update Car Status.

8 The use case ends.

Alternate Flow: A1 (Cost entered is more than SR10,000)

1 The system displays a message that the cost entered for repairing is more than SR 10,000 which need special permission from the branch manager.

2 The user confirms the message.

(44)

Page 44

18. Search Car

Use Case Number 18

Use Case Name Search Car

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) The car has been added to the database by the branch manager

Successful Post Condition The actor can view all information related to the car Actors Fleet Inspection

Priority Medium

Related Use Cases None

Flow of Events Basic Flow Step Number Steps

1 The use case begins after the user clicks “Report Repair”

2 The system prompts the user to enter the category of the car and license plate number.

3 The user enters the required information.

A1: Information entered is invalid.

4 The system displays a confirmation message stating that the car exists in the system.

A2: Car not found.

5 The user confirms the message. 6 The use case ends.

Alternate Flow: A1 (Information entered is invalid)

1 The system displays a message that the information entered by the user is not of the same type of information accepted by the info field.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Alternate Flow: A2 (Car not found)

1 The system displays a message that the car with the entered license plates and under the category does not exist.

2 The user confirms the message.

(45)

Use Case Number 19

Use Case Name Update Received Car

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) The car has been handed over to the fleet inspection by the dispatch department

Successful Post Condition The status of the car is changed to under maintenance Actors Fleet Inspection

Priority Medium

Related Use Cases None

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “Update Received Car”.

2 The system prompts the user to enter the category of the car and license plate number.

3 The user enters the required information.

A1: Information entered is invalid.

4 The system displays a confirmation message stating that the car exists in the system.

A2: Car not found.

5 The user confirms the message.

6 The system asks the user to enter a status for the received car.

7 The user selects the status for the car – under maintenance, discarded or available. 8 The system displays a message that the

status of the car has been updated. 9 The user confirms the message. 10 The use case ends.

Alternate Flow: A1 (Information entered is invalid)

1 The system displays a message that the information entered by the user is not of the same type of information accepted by the info field.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Alternate Flow: A2 (Car not found)

1 The system displays a message that the car with the entered license plates and under the category does not exist.

2 The user confirms the message.

(46)

Page 46

20. Update Car Status

Use Case Number 20

Use Case Name Update Car Status

Author Yazeed

Date of Creation 30-Nov-09

Precondition(s) User has login successfully and there is an existed car.

Successful Post Condition. User updates the car status. Related Use Case 17.Report Repair.

Actors Fleet Inspection.

Priority High

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the user choose the option of update car status.

2 System asks the user to enter the file number of the car.

3 The user enters the file number. A1: Invalid File Number.

4 The system prompts the user to change the car status.(Available- not available-

Freezing).

5 The user changes the car status. A2: Invalid status.

6 The system shows a confirmation message to the user.

7 The user confirms the message. 8 The use case ends.

Alternate Flow A1: Invalid file number

1 The system shows a message to the use about the wrong file number.

2 The user confirms the message and the flow returns to step 3.

A2: Invalid Status.

1 The system shows a message to the user about the invalid car status.

2 The user confirms the message and the basic flow returns back to step 5.

(47)

21. Add Account

Use Case Number 21

Use Case Name Add account

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) Administrator must be logged in

Successful Post Condition An account must be created for a system user Actors Administrator

Priority Medium

Related Use Cases None

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “Add Account”.

2 The system prompts the user to enter all the essential information for creating an account like name, employeeID, type of account etc

3 The user enters the required information.

A1: Information entered is invalid.

4 The system displays a confirmation

message stating that the account has been created successfully.

E1: Unable to access database

5 The user confirms the message. 6 The use case ends.

Alternate Flow: A1 (Information entered is invalid)

1 The system displays a message that the information entered by the user is not of the same type of information accepted by the info field.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Error Flow: E1 (Unable to access database)

1 The system displays a message that the system is not able to access the database to make any additions or modifications

2 The user confirms the message. 3 The use case ends

(48)

Page 48

22. Delete Account

Use Case Number 22

Use Case Name Delete account Author/Source Shaeq Khan Date of Creation December 5, 2009

Precondition(s) Administrator must be logged in

Successful Post Condition An account will be deleted from the system

Actors Administrator

Priority Medium

Related Use Cases None

Flow of Events Basic Flow

Step Number Steps

1 The use case begins when the user clicks “Delete Account”.

2 The system prompts the user to enter name, employeeID, and the type of account

3 The user enters the required information.

A1: Information entered is invalid. 4 The system displays a confirmation message

stating that the account exists in the system

A2: Account does not exist 5 The user confirms the message.

6 The system then informs the user that the account is going to be deleted from the system

A3: User cancels the operation 7 The user accepts the message

8 The use case ends.

Alternate Flow: A1 (Information entered is invalid) 1 The system displays a message that the

information entered by the user is not of the same type of information accepted by the info field.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2 Alternate Flow: A2 (Account does not exist)

1 The system displays a message that the system does not contain any account with the entered information.

2 The user confirms the message.

3 The use case 24 Search Account is executed 4 The use case ends

Alternate Flow: A3 (User cancels the operation)

1 The system informs the user that they have canceled the operation

2 The user confirms the message 3 The use case ends

(49)

23. Modify Account

Use Case Number 23

Use Case Name Modify account

Author/Source Shaeq Khan

Date of Creation December 5, 2009

Precondition(s) Administrator must be logged in

Successful Post Condition An account will be modified in the system Actors Administrator

Priority Medium

Related Use Cases None

Flow of Events Basic Flow Step Number Steps

1 The use case begins when the user clicks “Modify Account”.

2 The system prompts the user to enter employeeID, and the type of account 3 The user enters the required information.

A1: Information entered is invalid.

4 The system displays a confirmation message stating that the account exists in the system

A2: Account does not exist

5 The user confirms the message.

6 The use case 24 Search Account is executed 7 The system displays the information of the

employee and asks the user to make changes as required

8 The user makes all the necessary changes. 6 The system then informs the user that the

account is going to be modified in the system

A3: User cancels the operation

7 The user accepts the message 8 The use case ends.

Alternate Flow: A1 (Information entered is invalid)

1 The system displays a message that the information entered by the user is not of the same type of information accepted by the info field.

2 The user confirms the message.

3 The flow goes back to basic flow, step 2

Alternate Flow: A2 (Account does not exist)

1 The system displays a message that the system does not contain any account with the entered information.

(50)

Page 50

2 The user confirms the message. 3 The use case ends

Alternate Flow: A3 (User cancels the operation)

1 The system informs the user that they have canceled the operation

2 The user confirms the message 3 The use case ends

(51)

Use Case Number 24

Use Case Name Search Account

Author Yazeed

Date of Creation 28-Nov-09

Precondition(s) Administrator has login successfully.

Successful Post Condition`

Administrator has found the account that he searched for.

Actors Administrator

Related Use Case - 22.Delete Account. - 23.Modify Account.

Priority medium

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the administrator choose the option search account.

2 System asks the administrator category of the user(accountant, receptionist ,…,etc) to search for it.

3 The administrator chooses the category of the user.

A1: Invalid Category.

4 The system prompts the Administrator to enter ID of the user.

A2: Incorrect ID.

5 The administrator enters the ID.

6 The system shows the account for the user. The use case ends

E1: User not found.

Alternate Flow A1: Invalid Category:

1 The system shows a message to the administrator to re-enter the category 2 The administrator confirms the message 3 The basic flow returns to step 3.

Alternate Flow A1: Incorrect ID.

1 The system displays a message to the administrator to re-enter the ID.

2 The administrator confirms the message. 3 The basic flow returns to step 4.

E1:User not found.

1 The system shows a message that user not found

2 The user confirms the message the use case ends.

(52)

Page 52

25. Backup System

Use Case Number 25

Use Case Name Backup System

Author Yazeed

Date of Creation 28-Nov-09

Precondition(s) Administrator has log in successfully

Successful Post Condition The files have been completely backup and they are in the

required disk.

Actors Administrator

Priority Low .

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the administrator select the option backup system. 2 The System asks the administrator to

choose data that he wants to backup. 3 The administrator chooses the required

files.

4 The system :

- Checks memory size.

- Shows a confirmation message. A1: Insufficient memory.

E1: Backup is not available.

5 The administrator confirms the message 6 The system shows information about the

process and use case ends.

Alternate Flow A1: Insufficient memory size.

1 The system displays the message that asks the administrator to reduce data size. 2 The administrator confirms the message

and the flow returns to step 3.

Error Flow E1: Backup is not available.

1 System shows the message that the backup is not reachable.

2 The administrator confirms the message and the use case ends here

(53)

26. Add Category

Use Case Number 26

Use Case Name Add Category.

Author Yazeed

Date of Creation 29-Nov-09

Precondition(s) Manager has login successfully.

Successful Post Condition The category is added and it is available to be added to cars.

Actors Branch Manager.

Priority Medium.

Flow of Events Basic Flow Step No. Steps

1 The use case begins when the manager selects the option add category.

2 System asks the manager to enter data of the category which includes:

- Name. - Rates.

3 The manager enters the data of the category. A1: incomplete information.

A2:Wrong piece of information.

4 The system shows a confirmation message.

5 The manger confirms the message and the use case ends.

Alternate Flow A1: Incomplete information

1 The system shows a message to the manger to complete the missed data.

2 The manager confirms the message and the flow returns to step 3.

Alternate Flow A2: Wrong piece of information.

1 The system displays the message saying a specific entered information cannot be accepted.

2 User confirms the message and the flow returns back to basic flow step 3.

(54)

Page 54

27. Modify Category

Use Case Number 27

Use Case Name Modify Category

Author Yazeed

Date of Creation 30-Nov-09

Precondition(s) There is an existed category in the system.

Successful Post Condition - The category is modified .

- The modification affects cars which are included in the category.

Actors Branch Manager.

Related Use Case - 28.View Category. - 29.Delete Category.

Priority Medium.

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the user select the option modify category.

2 The system asks the user to enter the name of the category.

3 The user enters the name of the category. A1: Invalid name.

4 The system executes View Category use case. 5 The user changes required fields.

6 The system shows a confirmation message if the modification is done.

7 The user confirm the message and the use case ends.

Alternate Flow A1: Invalid name.

1 The system shows a message to the user to re-enter the name

2 The user confirms the message and the basic flow returns back to step 3.

(55)

28. View category

Use Case Number 28

Use Case Name View Category

Author Yazeed

Date of Creation 30-Nov-09

Precondition(s) There is an existed category in the system.

Successful Post Condition The category is viewed.

Actors Branch Manager.

Related Use Case - 27.Modify Category. - 29.Delete Category.

Priority low.

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the user select the option view category.

2 The system asks the user to enter the name of the category.

3 The user enters the name of the category. A1: Invalid name.

4 The system view the requested category. 5 The use case ends.

Alternate Flow A1: Invalid name.

1 The system shows a message to the user to re-enter the name

2 The user confirms the message and the basic flow returns back to step 3.

(56)

Page 56

29. Delete Category

Use Case Number 29

Use Case Name Delete Category

Author Yazeed

Date of Creation 30-Nov-09

Precondition(s) There is an existed category and the requested category has been viewed.

Successful Post Condition The requested category has been deleted and it cannot be

used to be used by cars.

Actors Branch Manager

Related Use Case - 28.View Category. - 27.Modify Category.

Priority Medium.

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the user select the option delete category.

2 The system asks the user to enter the name of the category.

3 the user enter the name of the category. A1: Invalid name

4 The system execute View Category use case.

5 The user delete this category.

6 The system shows a confirmation message to the user.

7 The user confirms the message and the use case ends.

Alternate Flow A1: Invalid Name

1 The system shows a message to the user to re-enter the name.

2 The user confirms the message and the basic flow returns to step 3.

(57)

30. Generate Report

Use Case Number 30

Use Case Name Generate Reports

Author Yazeed

Date of Creation 30-Nov-09

Precondition(s) User has login successfully .

Successful Post Condition The requested report is generated for the available cars. Actors Branch Manager.

Priority Medium

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the user select the option generate reports.

2 System prompts the user to choose the date of the report that contains the information of the available cars. 3 The user choose the date.

A1: Invalid date.

4 The system generates the report to the user.

5 The use case ends. A1:Invalid Date:

1 The system shows a message to the user to choose another date.

2 The user confirms the message and the basic flow of event returns to step 3.

(58)

Page 58

31. Remove Car

Use Case Number 31

Use Case Name Remove Car

Author Yazeed

Date of Creation 30-Nov-09

Precondition(s) User has login successfully and there is an existed car in the system.

Successful Post Condition The car is removed from the system and cannot be rented. Actors Branch Manager.

Related Use Case - 18.Search Car. - 32.Modify Car.

Priority Medium

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the user select the option remove car.

2 System prompts the user to enter the file number of the car

3 The user enters the file number. A1: Search Car.

A2: Invalid File Number. 4 The system :

- Removes the requested car from the database.

- Shows a confirmation message to the user.

5 The user confirms the message. 6 The use case ends.

Alternate Flow A1: Search Car.

1 The user selects "Search Car".

2 The "Search Car" use case is executed. 3 The flow returns back to basic flow step 4. Alternate Flow A2: Invalid File Number.

1 The system shows a message to the user about the wrong file number.

2 The user confirms the message and the basic flow returns to step 3.

(59)

32. Modify Car

Use Case Number 32

Use Case Name Modify Car

Author Yazeed

Date of Creation 30-Nov-09

Precondition(s) User has login successfully and there is an existed car in the system

Successful Post Condition The requested modification is done . Related Use Case - 18.Search Car.

- 31.Remove car.

Actors Branch Manager.

Priority Medium

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the user select the option Modify car.

2 System prompts the user to the file number of the car

3 The user enters the file number. A1: Search car.

A2:Wrong file number. 4 The system displays the car.

5 The user modifies the required data. 6 The system shows a confirmation message

to the user about the modification.

7 The use confirms the message and the use case ends.

Alternate Flow A1: Search Car.

1 The user selects "Search Car".

2 The "Search Car" use case is executed. 3 The flow returns back to basic flow step 4. Alternate Flow A2: Invalid File Number.

1 The system shows a message to the user about the wrong file number.

2 The user confirms the message and the basic flow returns to step 3.

(60)

Page 60

33. Add Car

Use Case Number 33

Use Case Name Add Car

Author Yazeed

Date of Creation 30-Nov-09

Precondition(s) User has login successfully.

Successful Post Condition The car is entered to the system and available to be rented. Actors Branch Manager.

Priority Medium

Flow of Events Basic Flow Step Number Steps

1 Use case starts when the user select the option add car.

2 System prompts the user to enter the information of the car including:

- Company. - Name. - Model. - Color - File number. - .. etc.

3 The user enters the requested information. A1: Incomplete information.

A2:Wrong piece of information. 4 The system :

- Display a confirmation message. 5 The user confirms the message.

6 The system add the car and the use case ends.

Alternate Flow A1: Incomplete information

1 The system displays a message that tells the user about missed information. 2 The user confirms the message and the

flow returns back to basic flow step 3.

Alternate Flow A2: Wrong piece of information.

1 The system displays the message saying a specific entered information cannot be accepted.

2 User confirms the message and the flow returns back to basic flow step 3.

(61)

34. Delete Customer

Use Case Number 34

Use Case Name Delete Customer Author/Source Abdulaziz Alamoudi Date of Creation November 10, 2009 Precondition(s) The account must exist. Successful Post Condition The file is deleted.

Actors Branch Manager

Priority High

Related Use Cases 8. Search Customer.

Flow of Events Basic Flow

Step Number Steps

1 The use case begins when the user enters the customer’s file number.

 A1: Search Customer. 2 The system displays the file.

 A2: Invalid File Number. 3 The user selects “Delete File”.

4 The system displays a confirmation message. 5 The user confirms the message.

6 The file is deleted. 7 The use case ends. Alternate Flow: A1 (Search Customer)

1 The user selects “Search Customer”

2 The “Search Customer” use case is executed. 3 The flow goes to step 2 of the primary flow. Alternate Flow: A2 (Invalid File Number)

1 The system displays a message that the entered file doesn’t exist.

2 The user confirms the message.

Figure

Updating...

References

Related subjects :