Carpooling - Functional and Non-Functional Requirements, Typical Cours - Case Study Example

Table of Contents Table of Contents 1 INTRODUCTION 3 Carpooling is defined as the sharing of cars in order to reduce cost and road congestion. Car pool reservation is a firm based in Perth, Western Australia. It acts as a meeting area for people who wish to share a car to home and from work. Car pool reservation wants to develop an online system that will help people who want to carpool. 3 2.0 GLOSSARY OF TERMS 3 1. Carpool- It is an arrangement where people share cars instead of everyone driving his/hers from home to work. 3 2. RFID- Radio frequency identification this is the transfer of data using electromagnetic fields. It mainly involves tracking. 3 3.0 PROJECT SCOPE 3 CPR system will be developed to facilitate carpooling within Perth in Western Australia, and also extend to cover other cities. For example, Melbourne and Brisbane. It will be able to store information about members and register new members into the system. The system will also be collaborating with insurance companies in order to provide insurance policies to its members. Members of CPR will have their vehicles installed with RFID chips, which will help them in the identification of vehicles hence get a discount on toll payment. 3 3.1 FUNCTIONAL REQUIREMENTS 3 3.1.1 Availing quotes on car insurances. 3 3.1.2 Allowing members to pay invoices. 4 3.1.3 Allowing authenticated staff to generate reports of franchise performance that is new registrations. 4 3.1.4 Holding information about members of the carpool reservations (CPR). 4 3.1.4 Recording the details of potential car shares and allow a member to have more than one vehicle. 4 3.1.5 Recording details of sharing arrangements. 4 3.1.6 Matching members and share a car based on their location, geographical locations and travel times. 4 3.1.7 Allowing potential members to look for services that are available. 4 3.1.8 It should be able to produce reports for the services provided and being paid for. 4 3.2 NON-FUNCTIONAL REQUIREMENTS 4 . 4 Scalability: Capable of future expansion to incorporate information about toll schemes and equipment sold. 4 Security: this is by ensuring that only authenticated staff to generate reports of franchise performance. Also, a credit card details must be protected by a 128-bit SSL certificate. 4 Usability: This is by allowing potential members to look for the services very quickly. 4 Robustness: the ability of a system to withstand any error or rather maintain consistent functionality. 4 Operability: able to provide all the functions that are supposed to provide 4 Availability: the system must be available all the time. 5 3.3 OUT OF SCOPE ITEMS 5 The system does not show the number of vehicles that a member has. It does not show if a member have ever claimed from the insurance. 5 4.0 ASSUMPTIONS 5 4.1 That all potential members have smartphones of their own, and they can download and install the application 5 4.2 operating system that the application developed will operate on all phones/tablets platform and work without bugs. 5 4.3 potential members are divided into two, user and car owner. 5 5.0 Use Cases 6 5.2 ELABORATION OF USE CASE 8 5.3 ELABORATION OF USE CASE 9 7.0 DATA DICTIONARIES 9 7.1 ELEMENTARY DATA DICTIONARY 9 8.0 BUSINESS RULES DIAGRAMS 10 8.1 BRD OF 10 8.2 EVENT SPECIFICATION TABLE OF 11 8.3 BRD OF 11 8.5 BRD OF 12 9.0 REFERENCES 13 Booch, G., Rumbaugh, J., & --, I. J. (2005). The Unified Modeling Language User Guide (Second Edition) (2nd ed.). United States: Addison-Wesley Educational Publishers. 13 10.0 LOGICAL RELATIONAL DATA MODEL 14 INTRODUCTION Carpooling is defined as the sharing of cars in order to reduce cost and road congestion. Car pool reservation is a firm based in Perth, Western Australia. It acts as a meeting area for people who wish to share a car to home and from work. Car pool reservation wants to develop an online system that will help people who want to carpool. 2.0 GLOSSARY OF TERMS 1. Carpool- It is an arrangement where people share cars instead of everyone driving his/hers from home to work. 2. RFID- Radio frequency identification this is the transfer of data using electromagnetic fields. It mainly involves tracking. 3.0 PROJECT SCOPE CPR system will be developed to facilitate carpooling within Perth in Western Australia, and also extend to cover other cities. For example, Melbourne and Brisbane. It will be able to store information about members and register new members into the system. The system will also be collaborating with insurance companies in order to provide insurance policies to its members. Members of CPR will have their vehicles installed with RFID chips, which will help them in the identification of vehicles hence get a discount on toll payment. 3.1 FUNCTIONAL REQUIREMENTS 3.1.1 Availing quotes on car insurances. 3.1.2 Allowing members to pay invoices. 3.1.3 Allowing authenticated staff to generate reports of franchise performance that is new registrations. 3.1.4 Holding information about members of the carpool reservations (CPR). 3.1.4 Recording the details of potential car shares and allow a member to have more than one vehicle. 3.1.5 Recording details of sharing arrangements. 3.1.6 Matching members and share a car based on their location, geographical locations and travel times. 3.1.7 Allowing potential members to look for services that are available. 3.1.8 It should be able to produce reports for the services provided and being paid for. 3.2 NON-FUNCTIONAL REQUIREMENTS . Scalability: Capable of future expansion to incorporate information about toll schemes and equipment sold. Security: this is by ensuring that only authenticated staff to generate reports of franchise performance. Also, a credit card details must be protected by a 128-bit SSL certificate. Usability: This is by allowing potential members to look for the services very quickly. Robustness: the ability of a system to withstand any error or rather maintain consistent functionality. Operability: able to provide all the functions that are supposed to provide Availability: the system must be available all the time. 3.3 OUT OF SCOPE ITEMS The system does not show the number of vehicles that a member has. It does not show if a member have ever claimed from the insurance. 4.0 ASSUMPTIONS 4.1 That all potential members have smartphones of their own, and they can download and install the application 4.2 operating system that the application developed will operate on all phones/tablets platform and work without bugs. 4.3 potential members are divided into two, user and car owner. 5.0 Use Cases Figure 1 use case 5.1 ELABORATION OF USE CASE Use case: Actor(s): Purpose: Overview: user can check for available rides,pay invoice Preconditions: Postconditions: Typical Course of Events Actor Action System Response 1. Open application 2. The system opens the log in window 2. Enters log in details 2. If correct, it logs into the system Alternative Courses Step 2: . Related Use Cases Extensions 5.2 ELABORATION OF USE CASE Use case: < looking for available services > Actor(s): < potential member> Purpose: Overview: he can be able to check for services being offered and get quotes on insurance Preconditions: Postconditions: Typical Course of Events Actor Action System Response 1. Open application 1. The application opens 2. Searches for available services 2. Displays available services 3. Closes the system 3. Application closes Alternative Courses Step 3: . Step 2: Related Use Cases Inclusions Extensions 5.3 ELABORATION OF USE CASE Use case: Actor(s): Purpose: Overview: generate a report Preconditions: Postconditions: < the staff are authenticated> Typical Course of Events Actor Action System Response 1. Open application 2. The system opens the log in window 2. Enters log in details 2. Logs into the system 3. Generate a report 3. Display a report 4. Clerk logs out 4. Closes the application Alternative Courses Step 2: 7.0 DATA DICTIONARIES 7.1 ELEMENTARY DATA DICTIONARY . Name Type Width (Size) Format Constraint Member Id 10 A Not null Email address 15 A @ and . address 9 X Not null First name 8 A Not null Second name 8 A Not null Car id 5 X Not null Vehicle capacity 5 N Not null Engine number 10 N Not null Location 10 A Not null Insurance Policy 10 X Not null Payment mode 8 X Not null Legend: A Alphabetic N Numeric 9 Any digit X Any character D Date format (dd/mm/yyyy) $ Leading spaces Z Leading blank or any digit 8.0 BUSINESS RULES DIAGRAMS 8.1 BRD OF The ffige below is shows log in case No yes 8.2 EVENT SPECIFICATION TABLE OF 8.3 BRD OF No YES 8.5 BRD OF 9.0 REFERENCES Booch, G., Rumbaugh, J., & --, I. J. (2005). The Unified Modeling Language User Guide (Second Edition) (2nd ed.). United States: Addison-Wesley Educational Publishers. 10.0 LOGICAL RELATIONAL DATA MODEL One diagram, one A4 page. Use Microsoft Visio to draw the diagram.The diagram below shows data relational model for the cpr Read More