# Authenticity, and Approval Framework for Bus Transportation Based on Blockchain 2.0 Technology
## 6 Methodology
\begin{table}
\begin{tabular}{c c c c c c c c c} \hline  & **F1** & **F2** & **F3** & **F4** & **F5** & **F6** & **F7** & **F8** & **F9** \\ \hline F1 & 1.245993 & 0.559616 & 0.464675 & 0.515511 & 0.343057 & 0.322686 & 0.447715 & 0



* They can also communicate with the users and coordinator entities through the system. * 3. Coordinator Entities:
* They act as intermediaries between the users and administrative entities. * They facilitate the submission and processing of transport requests. * They maintain the integrity and transparency of the BC-BAS. **Testing Objectives**: The primary objectives for testing the BC-BAS application are as follows:

1. Functionality: * Validate that users can successfully submit transport approval requests. * Verify that administrative entities can review and approve/reject transport requests. * Ensure coordinator entities can effectively manage the communication between users and administrative entities. * Confirm that the system accurately reflects the status of requests and provides appropriate notifications. 2. Security: * Assess the system's resilience against potential security threats, such as unauthorized access and data tampering. * Validate the encryption mechanisms used to protect sensitive data. * Verify that access controls are properly implemented and enforced for each actor. 3. Reliability: * Evaluate the system's ability to handle a high volume of transport approval requests simultaneously. * Verify that the system remains responsive and available during peak usage times. * Perform stress testing to identify any performance bottlenecks and ensure the system can scale effectively. **Testing Approach**: To achieve the testing objectives, the following testing approach is proposed:

1. Test Case Development: * Develop comprehensive test cases covering all functional requirements. * Include test cases for both positive and negative scenarios, to ensure robustness. * Design test cases, to validate security controls and access restrictions. 2. Functional Testing: * Conduct end-to-end testing, to validate the entire transport approval process. * Test user registration, request submission, approval/rejection processes, and notifications. * Perform boundary testing, input validation, and error handling verification. 3. Security Testing: * Perform vulnerability assessment and penetration testing, to identify any security weaknesses. * Test data encryption, access controls, and authentication mechanisms. * Validate the system against common security threats, including SQL injection, cross-site scripting, and session hijacking. 4. Performance Testing: * Conduct load testing, to assess the system's performance under normal and peak load conditions. * Identify and address any performance bottlenecks or scalability issues. * Measure the response time and throughput of the system. Table 18 outlines various scenarios for approving or rejecting transport data applications, considering both physical condition and documentation. 1. Defective bus data are rejected but can be updated and re-sent if rejected by the coordinator. 2. Physically repairable but unreceived bus data are placed on hold, pending coordinator approval. 3. Buses with missing or invalid certificates are conditionally approved, but applicants must complete and re-send the required certificates. The administration does not provide final approval in these cases. 4. Buses with valid certificates are approved and require clearance from both the coordinator and the administrator. 5. Buses without completed physical tests are initially approved but put on hold until the necessary tests are conducted. 6. Buses with sound physical condition and valid certificates are approved, but company clearance is needed within a specified time frame. 7. Older model buses with valid certificates are rejected, requiring replacement with newer ones. The administration does not grant approval in such cases. 8. Bus data with lost approval documents are rejected but can be resubmitted, with no further processing if rejected by the coordinator. 9.