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 

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

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 

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

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 

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

To enable more people to access the system. 

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 

Reliability Requirements 

Security Requirements 

Interface Requirements 

User Requirements 

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. 

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 

 

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 

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 

 

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. 

 

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. 

 

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. 

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. 

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.

Functional Requirements:

Non-functional Requirements:

Security Requirements:

Interface Requirements:

User Requirements:

Business Requirements:

2. Non-functional Requirements

- 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. 

- 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 . 

- 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.

- 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 . 

- 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 . 

- 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.

▪ 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