# data[].attributes.body
▪ Functional Requirements

1.      The system shall apply discounts for new users

2.      The system shall be sent an email whenever an order is placed

3.      The system shall send a notification when the driver has arrived at the pick-up location

4.      Feedback and review of drivers

5.      Payment with bank account, eWallet

6.      Receipt or proof of cash payment

7.      The system should provide many choices for the number and types of drivers and riders

8.      The system should be able for drivers to take multiple riders

9.      Passengers and drivers can schedule their travelling anonymously

10.   Users should be able to cancel the ride within 5 minutes

11.   Drivers should be able to make report on users that cause any violent action on his car.

12.   Users should be able to access on live tracking of driver’s car location after the order has been confirmed.

▪ Non-Functional Requirements

▪ Technical Requirements

1.      A mobile application should be required to use the Android and IOS operating system

2.      The mobile should be able to connect to the internet with a bandwidth of at least 5Mbps

3.      The system should be able to handle a large number of users and transactions, and be able to scale up or down as needed.

4.      The system should be able to handle a large number of users and transactions

5.      The core system should be a minimum of 4GB of RAM

6.      Proper handling of database system to obey data law can be done via cloud technologies such as AWS, Azure and others.

▪ Security Requirements

1.      Driver and co-passengers need to agree with the carpooling

2.      The system should use secure methods of authentication

3.      The system should use secure payment processing methods

4.      The system should have a feature for users to provide emergency contact information for safety purposes

5.      The system should frequently provide update on how the user data is processed.

▪ Interface Requirements

1.      The system should have a simple and easy-to-use interface

2.      Users should be able to create a personal profile

3.      Users should be able to search for carpooling opportunities

4.      Users should be able to create and manage carpooling groups

5.      Should have Google map to check the location and find the destination

6.      The system must provide different types of languages that users can understand.

▪ User Requirements

1.      Driver and co-passengers should sign up using their real name and email

2.      Users should be to customize their profile

3.      Drivers need to state on his car model year, engine condition, number of seats and other perspectives about their cars

▪ Business Requirements

1.      Users should be able to search for carpooling opportunities based on their location and schedule and be matched with other users who have similar travel needs

2.      The system should allow users to create and manage carpooling groups, invite others

3.      Both drivers and passengers should agree with the carpooling price

# data[].attributes.headline
AuroraTech - Shaun Lee Rui Jie (TP066980)

# data[].attributes.subject
AuroraTech - Shaun Lee Rui Jie (TP066980)

# data[].attributes.body
Team members:
1.) Teoh Hong Shen
2.) Leyu Yi Ting
3.) Chan Zhe Yan
4.) Michelle Cheng Jin Ying
5.) (Leader) Shaun Lee Rui Jie

1. Functional requirements:

• Sign Up: Users need to sign up to use the web site or application. The users will need a username and password in order to sign up. They will register the system once the users fill in their name, surname, e-mail, age, job, phone, and gender information.

• Sign Out: The user might need to sign out of the system. They can sign out by clicking the sign out button which will be placed in every page.

• Sign In: The users will need to fill in their username and password in order to sign in to the system.

• Send Message: The users will be able to communicate with each other by sending message.

• Reply Message: The users can read the message once they receive it, they can then reply the message by sending back message if needed.

• Add Transportation Path: The users can add their transportation by indicating the route, time and number of empty seats. There are two ways of selecting the route, the first way is by entering the starting and ending locations, once done the route will be drawn out on the map. The other way is selecting the start and end locations by using the map.

• Search Transportation Path: The users can search for their transportation in order for them to see the suitable routes to their destination by choosing the time and route.

• Delete Transportation Path: The users can delete their transportation route. After deleting the route, other passengers in that transportation will be informed by the system.

• Request Transportation Path: The users can use a transportation by sending a request to the driver of the transportation.

• Rate User: The users in the same transportation will be able to rate each other on the web site or application after having a transportation. In addition, other users can see the user rates so that they can decide which transportation is better.

• Block User: The users can block any user who sent them any disturbing message.

• Change Language: The users will be able to change the web site or application language by clicking the small flags that is available in all pages. There will be three suitable languages to be chosen, English, Mandarin Chinese and Bahasa Malaysia.

2. Technical requirements:

• The system should be portable. Moving from one MacOS or Windows version to another would not affect or create any problems.

• The system should have a feature that inquire users authentication before using the System.

• The system should be available for users to operate at all times.

• The quality data that is use for operational and decision-making processes should be high.

• The system can detect whether the user has inputted incorrect information

3. Performances requirements:

• Quick response time: User should be able to receive notifications instantly.
• System performance: The system should handle more than 2000 users queries at the same time without any delay.
• The system should send out any requirements from user through system immediately.

4. Usability requirement:

• Language: The system should have three languages, which are Malay, Mandarin and English
• Instructions: The system should have detailed instructions on how to use the functionalities that are available

5. Reliability requirements:

• Time usage: Users should be able to use the system as long as they wish.

• Server capacity:  The system can accommodate up to 500000 user accounts.

• Server reliability: The system’s server should be up at all times.

• Fault detection: The system should be able to detect faults or bugs and notify staff immediately.

6. Security requirements:

• The administrator password must be kept strictly confidential.

• User IDs and user passwords must be kept confidential.

• Users should not disclose their ID to others, as this may lead to misuse of the account.

• The database should be carefully maintained by the administrator, any loss could lead to confusion.

• Prevent fake IDs.

7. Interface requirements:

• The system should have a Google Map API as subsystem which shows all locations and roads in desired area.

• The system should have all the interfaces to fulfil all system functionality such as login, carpooling, searching location and more.

• All functionalities should be highlighted or represented by an icon to get user’s attention.

• System should replace general use words to short descriptions to reduce number of words being sent in notification.

• In the Google Map API should display numbers of car nearby by using icon while user searching for a service.

8. Business requirements:

• The application system should be able to support the business growth for the next following 5 years.

• The system should be able to fulfil the business goals and objectives which are reducing the traffic jam in Malaysia.

• The system should be able to help company earn profits starting the next 6 months.

9. User requirement:

• Users should be able to customize their icon and avatar

• Users should be able to customize the background of the system

• Users should be able to change their password or username of their account

• Users should be able to share their profile to other platforms like WhatsApp, WeChat, Messenger.

• Users should be able to link their profile to Gmail, Facebook, Instagram, and phone number

# data[].attributes.body
Group members 👍:

1. Tan Zhen Ying

2. Ong Cheng Wei

3. Chan Yi Cong

4. Lai Li Syuen

5. Naveen Nagulan

Functional Requirement

- User needs to register as a member before assessing the system.

- User can choose either to car pooling as a driver or a passenger.

- System must send an email when a certain condition happens (e.g:a carpooling success, a     customer sign up, cancel a carpooling, carpooling request accepted, etc).

- Users should be able to edit their profile.

- The passenger and driver can rate each other to gain a reputation

- The driver can create a new trip which includes the destination, origin, number of free space, departure time, and price.

- Passengers can search by using the filter function or search bar to find suitable cars.

- User can share their current location with their friends or family for safety purposes.

- Passenger is able to make payment using cards, online banking, e-wallets, or cash.

- Passenger should be able to cancel the carpooling request one hour before the carpool time.

- The carpool will be automatically canceled if the passenger did not appear for car pooling within 5 minutes. Passenger can discuss with driver to extend the meeting time.

- Driver can delay the time upon passenger request.

- Driver may edit his/her transportation route. After modifying route, other passengers in that

transportation will be informed by the system.

- Driver can update the status when car pooling started and when they arrived at the destination.

- The users can have communicate each other by sending message.

- User can block others who send disturbing message to him/her.

Non-Functional Requirement

Performance Requirement

- The landing page supporting 1,000 users per hour must provide 5 seconds or less response time in the mobile app, including the rendering of text and images over an LTE connection.

- The filter results will show within 10 seconds.

- The machine time for specific requirement search will take within 30 seconds. Search action will be declined after 30 seconds if no car is found.

- It should handle errors gracefully and provide clear and actionable feedback to the user .

Technical Requirement

- The mobile application can be used in ios and Android operating system, and consume no more than 40MB of flash memory storage.

- The system can be run in a web browser.

- Networking is needed for all the app users to edit data and process activity, otherwise, all the users should not be able to use the app normally and always see the updated data.

Usability Requirement

- The system is supported with multi language.

- Online helper and documentation

- Voice Support for aged passenger

-The interface should allow for personalization and customization options to suit different users' needs.

-The app should be easy for users to learn , even if they have never use it before .

Interface Requirement

- The system shall consist of user-friendly interfaces which can ease the users to navigate within the application.

- The interfaces on the application and web browser are customised based on the screen size.

- The interface should be intuitive and self-explanatory, with clear labels and instructions.

-The interface should respond quickly to user inputs and provide feedback in a timely manner.

-The interface should adapt to different screen sizes and resolutions, and work seamlessly on different devices and platforms.

- The interface should reflect the branding and style of the company or organization.

- The interface should provide clear and useful feedback to the user, such as error messages and confirmation messages.

-The interface should be tested with a diverse group of users to ensure it meets their needs and is easy to use.

Security Requirement
- Each user password must at least include 1 capital letter and 1 special character

- Users should be required to provide a valid username and password to log in to the platform.

- Users should only be able to access and edit their own information, and not that of other users.
- The origin phone will be notified once the account had login into a new device.

- The payment processing gateway must be PCI DSS compliant.

- Users are allowed to link either to their trustable email or phone number , just in case to retrieve their password if they forget .

User Requirement

- Users should be able to print their receipt from the system.

- User are able to customize the application background (dark mode, light mode, follow the system).

- Should be accessible to users with disabilities, such as providing alternative text for images and high-contrast mode for low-vision users.

-Should be allowed for personalization and customization options to suit different users' needs.

# data[].attributes.body
1. Functional Requirements

Users can sign up for a new account to access full features.

Users can log in to the application with their registered username and password.

Users should be able to schedule rides in advance or on-demand.

Users should be able to create a ride and search for available rides based on their location, destination, and other criteria.

The system should be able to match users with compatible rides based on their preferences and location.

Users should be able to make payments for their rides through Touch N Go, Cash, Credit/Debit Card.

Users should be able to schedule rides in advance or on-demand.

Users should be able to track the location of their ride in real-time.

Users should be able to communicate with other users in the carpool through the system.

Users should be able to rate and provide feedback on other users and rides.

Users should be able to cancel and request refunds for their rides.

2. Non-functional Requirements

Technical Requirements

The core system should have a minimum of 2GB of RAM.

The mobile application will only function well in Operating System (OS) above Android 6.0 or iOS 12.

Performance Requirements

The system should process less than 2 seconds of response time for a new request.

Usability Requirements

Users can easily understand how to perform tasks on the website after following the 1-minute guidance when they login to their account for the first time.

Reliability Requirements

The mobile application is accessible 24 hours a day, seven days a week.

System downtime will only allow during local time 1 am-3 am for not more than one hour twice in half a year.

The mobile application should capable enough to handle 50,000 concurrent users without affecting its performance.

Security Requirements

The system must be at least 98% secured. Database security must meet HIPAA rules.

# data[].attributes.body
Building a car-pooling system requires a comprehensive set of system requirements that must be taken into account to ensure the system is efficient and secure. The requirements can be broken down into 6 main categories: Functional, Non-functional, Security, Interface, User, and Business.

Functional Requirements:

User registration and login: Users must be able to create an account and log in to the platform in order to use the car-pooling service. This includes providing personal information such as name, email, and phone number.

Search and match: Users should be able to search for available car-pooling options based on their starting and ending points, as well as the desired time of travel. The system should then match users with compatible car-pooling options and display the results to the user.

Booking and payment: Once a user has found a car-pooling option that they are interested in, they should be able to book the ride and make payment through the platform.

Ride scheduling and tracking: Users should be able to view and edit their upcoming car-pooling rides, as well as track the location of their ride in real-time.

Feedback and rating: Users should be able to provide feedback and rate their car-pooling experience, which can be used to improve the service and ensure a high level of customer satisfaction.

Non-functional Requirements:

Performance: The system should be able to handle a large number of concurrent users and perform searches and matches quickly.

Scalability: The system should be able to handle an increase in the number of users and car-pooling options without experiencing significant performance degradation.

Reliability: The system should have a high level of uptime and be able to handle errors and unexpected situations without crashing or losing data.

Usability: The system should be easy to use and understand for users, with a clear and intuitive interface.

Compatibility: The system should be compatible with a wide range of devices and web browsers, to ensure that as many users as possible can access the platform.

Security Requirements:

Data encryption: Personal information such as names, emails, and phone numbers should be encrypted to protect the privacy of users.

Payment security: Payment information should be securely stored and transmitted to prevent unauthorized access or fraud.

Authentication: Users should be required to provide a valid username and password to log in to the platform.

Access control: Users should only be able to access and edit their own information, and not that of other users.

Interface Requirements:

User-friendly interface: The interface should be easy to navigate and understand for users, with clear and intuitive buttons and labels.

Responsive design: The interface should be optimized for different screen sizes and devices, to ensure that it is easy to use on both desktop and mobile devices.

Accessibility: The interface should be accessible to users with disabilities, with features such as large text and high contrast modes.

User Requirements:

Personalization: Users should be able to personalize their experience by selecting their preferred language and other settings.

Notifications: Users should be able to receive notifications about upcoming car-pooling rides, as well as any changes or updates to their rides.

Help and support: Users should be able to easily access help and support resources, such as FAQs and contact information.

Business Requirements:

Revenue generation: The platform should be able to generate revenue through various means, such as commission on bookings and ride fees.

Cost management: The platform should be able to manage costs effectively, such as server hosting and customer support.

Marketing and promotion: The platform should have a strategy for marketing and promoting the service to potential users, such as social media advertising and partnerships with other companies.

Data analysis: The platform should have the ability to collect and analyze data on usage patterns, user feedback, and other metrics, in order to improve the service.

# data[].attributes.body
Functional requirements:

Ride matching: The carpooling system should be able to match riders with compatible and convenient carpools based on factors such as location, route, and schedule.

Payment processing: The system should have the capability to process payments between carpool members for shared travel expenses. This could include integration with popular payment methods such as online banking, credit/debit cards, cash and etc.

Communication and scheduling: The system should allow carpool members to coordinate details such as pick-up and drop-off times and locations, and send notifications to other members of any updates or changes.

Vehicle tracking: The system should have the capability to monitor the location and status of carpool vehicles in real-time, so that riders can track the progress of their carpool and be alerted of any delays.

Rating and feedback system: The system should allow users to rate and review their carpool experiences, to provide valuable feedback to other users and improve the overall quality of the service.

Dashboard:
A web portal will be provided so that car passengers can view and manage drivers, vehicles, car models, car routes and so on.

Location tracking.
The system makes use of a location tracker to detect the location of a passenger and determine any nearby available cars.

Confirmation email.
After placing an order, that is requesting for a ride, a confirmation email will be sent to the user. Also, if the payment has been settled already, a payment receipt will be forwarded via email to thd customer.

Security requirements:

Data encryption: The carpooling system should protect sensitive user information such as personal details and payment information by encrypting data in transit and at rest.

Authentication and access control: The system should have robust authentication mechanisms in place to verify the identity of users and control access to sensitive information.

Network security: The system should have appropriate network security measures in place to protect against hacking and other cyber threats.

Compliance: The system should comply with relevant laws and regulations related to data protection and user privacy.

Regular security updates: The system should be regularly updated to address new security vulnerabilities and to ensure the system remains secure.

Business requirements:

The system should be able to help users easily find and organize carpools with others. It should be delivered within a set timeframe and within a budget, and it should be able to be expanded for future use. The system should be open and transparent so that the business can represent itself in a positive light.

User requirements:

To use the carpool service, users need to upload a picture of themselves and choose a profile design that they prefer. The driver will need to provide information about their car, the number of seats available, and images of the car. The riders will be able to view all the information about the cars and drivers, including the status of the ride and the location of the car. Finally, users will be able to choose their payment options and contact other riders to organize a carpool session.

Interface requirement:

The interface is easy to use and understand, with labels and instructions that are clear and concise. It adjusts to different screen sizes and devices, so that everyone can use it no matter what their device is. The interface is customizable, so that users can change what they see and how they see it. The interface also has search and filter functionality so that riders can find the ride they're looking for, and drivers can find rides that are available soon. Finally, the interface has payment and billing capabilities, so that drivers and riders can track their money and communication.

# data[].attributes.body
1. Functional Requirements
- User can book a seat in advance with the driver.
- User can make payment via e-Wallet, Online Transfer, or with cash.
- System will send receipt via e-mail after payment has been made for confirmation.

Non-functional requirements

2.Technical Requirements
- The mobile application can support Android versions 9.0 and iOS versions 11.0 and above.
- The core system should have at least 8GB of RAM.

3.Security Requirements
- User login process should include Two-Factor authentication.
- Password at least 12 characters long but 14 or more is better. A combination of uppercase letters, lowercase letters, numbers, and symbols.
- Password will be protected by encryption.

4.Interface Requirements
- The mobile and site interface should have a more user-friendly design as to attract less tech-savvy people.
- The various functions within the car-pooling application should be displayed clearly in categories to the users.
- The system's interface design should feature heavier use of icons and symbol to make the application easier to understand overall.

5.User Requirements
- Users can adjust which type of notifications that the car-pooling app will show them.
- Users can view their history of car-pools, showing the details of the car-pool such as the driver, time, price and etc..
- Users can choose to save an address, which can be used in future car-pools without the need to retype.
- Users can select their desired language for the mobile app and the website from the default English if the language is supported.

6.Business Requirements
- The car-pooling system should support and maintain business growth for the next 6 years.
- The system should be flexible enough to be incorporated with another system within the next 5 years.

# data[].attributes.body
Functional Requirements

1. Users have the choice to use ewallet and online banking instead of just cash to pay.

2. The app must have strong gps feature to detect nearby drivers

3. A search bar for pick-up and drop-off locations

4. A map where users can view their location

5. Users must sign up for an account and log in to use the app.

Non-Functional Requirements

1. Technical Requirements

System should have a mechanism to gather feedback on quality of routes and riders for example, in the app. There should also be an added choice to the number and types of riders and drivers. Only then will drivers be able to drill down to more specific requests — things like a quieter car, a limited number of pickups, the ability to participate in conference calls during the ride and smoking and eating options. To monitor and analyze system performance/user behavior, tools such as Google Analytics, Grafana, or New Relic can be installed. In case of failure/unexpected events, a backup and disaster recovery plan should also be installed to ensure the availability of the system and data integrity

1. Security Requirements

For security purposes the system could link Facebook and LinkedIn profiles to the profiles of the users in their system, so people on the “other end of the app” are known entities up front. If a user has no profile attached to a request, drivers or riders can choose to reject the request. Both drivers and riders should also have the ability to rate each other and block future contact if things don’t go well. Security measures such as SSL/TLS encryption, OAuth authentication, and firewalls to protect user data and prevent unauthorized access could also be implemented. A firewall is also important to block unauthorized access and protect the system from external threats.

1. Interface Requirements

User-friendly interface: An interface that is easy to navigate and understand, with clear and concise instructions and labels.

Responsive design: An interface that adjusts to different screen sizes and devices, such as desktop computers, laptops, tablets, and smartphones.

Customizable settings: An interface that allows users to customize their settings and preferences, such as notifications and ride reminders.

Search and filter functionality: An interface that allows users to search and filter available rides based on location, date, and number of seats.

Payment and billing: An interface for processing and tracking payments and billing between riders and drivers.

Ride scheduling and management: An interface for scheduling and managing rides, including the ability to cancel or reschedule rides.

Communication and messaging: An interface for facilitating communication and messaging between riders and drivers.

Rating and reviews: An interface for collecting and displaying ratings and reviews from riders and drivers.

GPS and mapping: An interface for displaying and tracking the location of vehicles in real-time.

Admin dashboard: An interface for managing and monitoring the carpooling system, including the ability to view ride statistics and user data.

Mobile optimization: An interface that is optimized for mobile devices, with a touch-friendly design and easy-to-use controls.

Multi-language support: An interface that supports multiple languages to cater to a diverse user base.

Accessibility: An interface that is compliant with accessibility guidelines and standards, such as WCAG 2.0, for users with disabilities.

1. User Requirements

All users must be able to upload their picture onto their profile.

All users shall customize their application interface to suit their taste.

The driver user must be able to upload his type of car, the number of seats available, and images of their car.

The driver user must be able to view the profile of the riders before accepting them to ensure comfortability.

The riders must be able to view all the cars and drivers’ profile.

The riders must be able to view the status of the ride and the location of the car in real time.

The riders must be able to choose their payment options before applying for a carpool.

The users should be able to message other users to help in organizing a carpool session.

1. Business Requirements

The system should be able to solve the issue for users in making and organizing a carpool session with relative ease.

The system must be delivered within an accepted time constraint of 6 months.

The system should be developed within the budget constraint of RM 100,000.

The system should be able to be supported and open to growth for the next 5 years.

The system must be able to represent the business in an open and transparent manner.

# data[].attributes.body
Functional Requirements:

Location sharing

Users should be able to update their current location so that driver or passenger users can take note of where to meet up with other users

Registration method
The user's national ID must be verified by the system permit them to use this service.

Payment Method
Users can pay either through cash, or bank transfer. E-wallets can also be used but the driver must notify the system first. The system will also have an option to have its own dedicated wallet. Users should be able to choose the payment option via credit/debit card, online banking, or e-wallet.

User profile update
Users should be able to modify their user profile so that they can indicate if they own a vehicle and how many people are able to fit into the current carpooling group.

Price listing

Passenger should be able to view the price of the trip before confirming the pickup.

Menu for specifying trips.

Users may add transportation by specifying a route / time / period and number of empty seats. The user can select the route in two different ways. The first way is entering start and end locations. Thus, the route is drawn on the map. The other way is selecting start and end locations on the map. Also, he / she can select at most 3 waypoints.

Non-Functional Requirements:

Technical Requirements

The system should be a web application.

So that it can be accessed by both computer users and mobile phone users.

The system can support Android, IOS, and Windows OS

To enable more people to access the system.

Internet connection is required.

So that any updates by the users can be uploaded and viewed by other users instantly.

Performance Requirements

-Must have a standard availability of 99.999% in a year

-Must have a cloud-based back-up system in case of a downtime or    maintenance (Preferably AWS or Microsoft azure)

- The system must undergo a through maintenance every 12 months

- A response time of at most 1 second

Usability Requirements

A FAQ or forum section should be available for users to look for help about problems related to the system functionalities.

Reliability Requirements

Customer service must consist of Chatbot (to cover the hours that a human response is absent and to answer general questions)

Emergency service panel, for the customer to contact the authorities in case of accident or crime being committed.

Security Requirements

2 step verification is used whenever a person makes payment via a wallet in the system.

All the data provided by users should be kept confidential.

A user must provide a password with a minimum of 8 digits, including at least one upper case, one lower case, and one special symbol.

Interface Requirements

The user can change the website language by clicking small flags that is available in all pages.

User Requirements

Visited places.

Users can save their most visited places in the system, so that they do not have to search the locations every time they want to go there.

Rating system

After having a transportation, the users in the same transportation can rate each other on the website. Thus, other users can see the user rates and they can decide which transportation is better

# data[].attributes.body
1. Non - Functional Requirement

Security: The system must ensure that personal and payment information is kept secure and protected from unauthorized access. This may include compliance with data protection regulations such as GDPR.

Scalability: The system must be able to handle a large number of users and requests, and be able to handle sudden spikes in usage.

Performance: The system should have a fast response time and minimal downtime to ensure a good user experience.

Reliability: The system should be designed to minimize the risk of errors or failures, and should be able to continue operating in case of failures.

2. Functional Requirements
• User can create a new user (either provider or consumer)
• Users are able to log into their respective user accounts
• Providers can update their vehicle (car plate number & vehicle model) and destination details
• Consumer are able to input their destination details
• Providers are able to see consumers’ destination details
• Providers can accept consumers’ request
• Providers and consumers can communicate using the app via text/voice chat or call
• Providers can see the route for consumers’ destinations to decide which consumers’ destination is on the route of the providers’ destination
• Consumers are able to see nearby active providers
• Consumers can pay the providers via e-wallet, bank transfer or cash

3.  Interface requirement

1. User interface: The carpooling system must have a user-friendly interface that allows users to easily search for carpools, create carpools, and view information about carpools and their participants.

2. Database interface: The carpooling system must have an interface to a database that stores information about users, carpools, and payments.

3. Payment processing interface: The carpooling system must have an interface to a payment processing system that allows users to make payments for carpools.

4. Location tracking interface: The carpooling system must have an interface to a location tracking system that allows users to view the real-time location of carpools and their participants.

5. Navigation interface: The carpooling system must have an interface to a navigation system that allows users to get directions to carpool locations.

4. Technical Requirements
• The System should run on Windows 10 or macOS 10 and above.
• The core system should have a minimum size of 2GB RAM and above.
• As for the mobile application, it is required a minimum of IOS 15 and Android 10 for its operating system, and not less than 2GB of RAM.
• The system will have an average page load time of fewer than 5 seconds.
• The system interface will not allow system developers to share or distribute customers’ vital information such as name, address, number, gender and so on.
• In case of any human error, the system will detect and will pop out a warning screen to inform consumers on how to solve the error such as wrong user id, password, or mis-input of address.
• In case of any system error, the system error will result in an error code which will be communicated with the consumers, and these codes will be sent over to the development team to rectify the error.
• Consumers' data will be encrypted and only visible and accessible to consumers and the system development team only.
• Consumers' data will be stored securely in the cloud storage with proper security to ensure no data breach occurs.
• The Consumers have full rights to how they would like to have their system's graphical user interface, where they can permanently turn off certain features as their preference in the preferences menu.

5. Security Requirement
The system must encrypt sensitive data transmitted over the Internet between the server and the browser.
 The application will have a password protected with * shapes when typing and attempting to copy
 When generating a new password the system will prompt for a question that only the user know
 When login in the car pooling system from a different country the system will prompt for a question that only the user know
 After 3 number of failed login attempts the system will lock the account rendering it unable to be logged into until the admin is contacted to unlock it
 When viewing personalized information on the profile the system will prompt users to enter their password before allowing access
 The server will have multi-layered fire walls with different anti-virus defending in between each of the layers of firewalls to prevent data breach
 After 60 days of inactivity the system will lock the users account until reactivation  The password must have numeric character, uppercase alphabets, lowercase alphabets and special character (EG !,@,#,etc)
 All interactions with the server will use secure HTTP for communication among client and server nodes

# data[].attributes.body
1. Functional
- Users need to log in to the system before starting a carpool.
- The system should provide another option where rides are only for women.
- The system should be able to let users select their pickup location, destination, and vehicle type.
- The system shall accept a few payment methods which are online banking, e-wallets, and credit card.
- The system should send a notification to the users whenever a condition is met such as when the ride is accepted, the driver has arrived and etc.
- Drivers should be able to accept or decline the rides.
- Users should be able to accept or reject the drivers assigned to them.
- The system should display the driver's and car's details to the users once the driver is assigned to the users.
- The system should share the user's live location with the driver.

2. Technical
- System should run a Windows Server or macOS Server on a computer.
- System should run an Android or iOS System on a mobile phone.
- The core system should have a minimum of 4GB of RAM.

3. Performance
-  The application has to provide a quick response time of at least 1 second and at most 30 seconds.
- The application has to propagate the responses between drivers and passengers instantly.
- The application can handle at least 2000 users at the same time.

4. Usability
- The application can support the three main languages in Malaysia which are Malay, Chinese and English.
- The application will compulsory force users to run through the tutorial on how to use the app when used for the first time.
- The error rate of users submitting their payment details at the checkout page (by e-wallet payment/ bank payment) mustn’t exceed 10 percent.

5. Reliability
- The system must perform without failure in 95 percent of use cases during a month.
- The system should not down or lag for more than 5 seconds.
- The system should not use more than 500MB of storage unless added new packages or updates.

6. Security
- The system may refuse access until the user generates a strong password. A strong password, for example, can have a particular amount of characters and a capital letter.
- The security system will ask questions to which only the user is accessible.
- A security system may lock an account after a specified number of login attempts to safeguard a user's information from possible hackers. User may often unlock their account by calling the firm to verify their identity and create a new password.

7. Interface
- A logged-in user can view the available carpooling at their location.
- The system must be linked to an emergency protocol that is linked to a hospital and police.
- The driver can upload their current trip to their own social media.

8. User
• Users should be able to change the theme of the interface. For example, clear blue, light indigo, and neutral.
• Users should be able to change the font style of the interface. For instance, Calibri Light and Times New Roman. • User should be able to change the Menu UI to display in Cards or Lists.
• The carpooling time could be displayed as 12 hours or 24 hours.

9. Business
• The carpooling system should provide at least 10 completed carpool services per day to maintain business growth for the next 5 years.
• The system should have at least 5 new users per week to reach the business goals.
• The system vision of targeting 10,000 carpool services should be accomplished within 5 years from the year 2023 onwards.

# data[].attributes.body
FUNCTIONAL REQUIREMENT
- Users can make payments via cash and tng eWallet.
- user can set their schedule
-User can find nearby drivers with the GPS features
-User can choose the number of passengers joining the carpool when booking
-Users can comment on the carpool services.
-User can cancel the trip within 5 minutes after the booking is made by giving reasonable reason.

NON-FUNCTIONAL REQUIREMENT
SECURITY REQUIREMENT
- User sign-in password must use a strong password with the following pattern: At least 12 characters long, Has a combination of upper and lowercase letters, numbers, punctuation, and special symbols, and Random and unique.

TECHNICAL REQUIREMENT
-System should be accessible through websites and mobile applications.

PERFORMANCE REQUIREMENT
-The system should process less than 30 seconds to search for a car for the user.

USABILITY REQUIREMENT
-The user can easily navigate to the page they want with the built-in button functions

RELIABILITY REQUIREMENT
-The system must perform without failure in 95 percent of use cases during a month.