Professional Documents
Culture Documents
Car Rental Management System System Architecture Document
Car Rental Management System System Architecture Document
Version:
1.0
Date: 11-04-2016
Revision History
Date
11-04-2016
Confidential
Version
1.0
Description
Initial design details
Author
N. Ravindu Hasantha
Page 2 of 18
CRMS
Software Architecture Document
Version:
1.0
Date: 11-04-2016
Table of Contents
1.
Introduction
1.1
1.2
1.3
1.4
1.5
4
4
4
4
4
Purpose
Scope
Definitions, Acronyms, and Abbreviations
References
Overview
2.
Architectural Representation
3.
4.
Use-Case View
4.1
4.2
6
6
5.
6.
Use case diagram
Use-Case Realizations
Logical View
12
5.1
12
Process View
13
6.1
Activity diagrams
6.1.1 Create customer account
6.1.2 Reserve vehicle
6.1.3 Update vehicle details
6.2
Sequence diagrams
6.2.1 Update vehicle details
6.2.2 Reserve vehicle
6.2.3 Search for vehicle
13
7.
Data View
18
8.
Quality
18
Confidential
13
14
15
16
16
17
17
Page 3 of 18
CRMS
Software Architecture Document
Version:
1.0
Date: 11-04-2016
Introduction
1.1
Purpose
This document provides a comprehensive architectural overview of the system, using
a number of different
architectural views to depict different aspects of the system. It is intended to
capture and convey the
significant architectural decisions which have been made on the system.
1.2
Scope
The system is divided into two subparts according to the users of the system:
Customer subsystem – System consist of all the functionalities related to
customers.
Business subsystem – System consist of all the functionalities related to business
end. (Company staff)
This document covers entire system and all its subparts. The functionalities of the
system are also clearly
divided into the above mentioned subparts and explained in simple and
understandable way.
1.3
1.4
References
1.5
Overview
The following is discussed in this document:
Architectural representation in the next section.
Architectural goals and constraints.
Design model diagrams:
2.
Usecase diagram
Class diagram
Activity diagram
Sequence diagram
ER diagram
Architectural Representation
Confidential
Page 4 of 18
CRMS
Software Architecture Document
Version:
1.0
Date: 11-04-2016
3.
4.
Use-Case View
Confidential
Page 5 of 18
CRMS
Software Architecture Document
4.1
Version:
1.0
Date: 11-04-2016
4.2
Use-Case Realizations
1.
Actor
customer
Description
preconditions
Main flow
Page 6 of 18
CRMS
Software Architecture Document
Version:
1.0
Date: 11-04-2016
Extensions
2.
Actor
Customer
Description
preconditions
Username, password
Main flow
Extensions
N/A
3.
Actor
Customer
Description
preconditions
Main flow
N/A
Extensions
N/A
4.
Actor
Customer
Description
preconditions
Main flow
Confidential
Page 7 of 18
CRMS
Software Architecture Document
Extensions
Version:
1.0
Date: 11-04-2016
In the case of contact number not available, the
customer will be asked to provide an contact
number
5.
Actor
Customer
Description
preconditions
Main flow
Extensions
6.
Actor
Customer
Description
preconditions
Main flow
Extensions
Confidential
Page 8 of 18
CRMS
Software Architecture Document
Version:
1.0
Date: 11-04-2016
7.
Actor
Customer
Description
preconditions
Main flow
N/A
Extensions
Actor
Admin
Description
preconditions
Main flow
Extensions
N/A
Confidential
Page 9 of 18
CRMS
Software Architecture Document
Version:
1.0
Date: 11-04-2016
9.
Actor
Admin
Description
preconditions
Main flow
Extensions
N/A
10. Change vehicle status
admin
Description
preconditions
Select vehicle
Change status using dispatch or return function
Failed notification
Extensions
N/A
11. Change cost details
Admin
Description
preconditions
Main flow
Extensions
N/A
Confidential
Page 10 of 18
CRMS
Software Architecture Document
Version:
1.0
Date: 11-04-2016
Admin
Description
preconditions
Main flow
Requested report
Extensions
N/A
13. Send availability details via text message
System
Description
preconditions
Main flow
Generate text message
Send out the text message using text message API
Extensions
N/A
Confidential
Page 11 of 18
CRMS
Software Architecture Document
Version:
1.0
Date: 11-04-2016
5.
Logical View
5.1
Confidential
Page 12 of 18
CRMS
Software Architecture Document
6.
Process View
6.1
Activity diagrams
6.1.1
Confidential
Version:
1.0
Date: 11-04-2016
Page 13 of 18
CRMS
Software Architecture Document
6.1.2
Version:
1.0
Date: 11-04-2016
Reserve vehicle
Confidential
Page 14 of 18
CRMS
Software Architecture Document
6.1.3
Version:
1.0
Date: 11-04-2016
Confidential
Page 15 of 18
CRMS
Software Architecture Document
6.2
Version:
1.0
Date: 11-04-2016
Sequence diagrams
6.2.1
Confidential
Page 16 of 18
CRMS
Software Architecture Document
6.2.2
Reserve vehicle
6.2.3
Confidential
Version:
1.0
Date: 11-04-2016
Page 17 of 18
CRMS
Software Architecture Document
7.
Version:
1.0
Date: 11-04-2016
Data View
8.
Quality
The system architecture will enforce all the capabilities of the system such as
extensibility, reliability,
portability.
Confidential
Page 18 of 18