ScreenScraping a website and generating an ouput
Budget: $250 – $750 AUD
Introduction
This document articulates the functional requirements for a screen scraping project aimed at gathering biller code, Biller Short, and Biller Long Name data from https://bpay.com.au/look-up-biller-code-financial-institution.
Scope
The primary purpose of this project is to automate the process of searching and extracting data from a predefined list of biller codes. The output should be a comprehensive, well-structured spreadsheet containing the biller code, Biller Short, and Biller Long Name associated with each biller code in the list.
Requirements
1. Input List
1.1 The system must accept an input list containing multiple biller codes.
2. Web Interaction
2.1 The system must navigate to the specified website: https://bpay.com.au/look-up-biller-code-financial-institution.
2.2 The system should be able to handle any network or loading issues encountered while accessing the website.
3. Search Functionality
3.1 The system must sequentially search each biller code from the list in the website's search functionality.
3.2 If a particular biller code does not return any result, the system should log it for review.
4. Data Scraping
4.1 Upon successful search, the system should scrape the following details:
Biller code
Biller Short Name
Biller Long Name
4.2 The system should ensure the accuracy of the scraped data.
5. Data Storage
5.1 The system should store the scraped data in a structured format such as a CSV or Excel file.
5.2 The output file should contain separate columns for Biller Code, Biller Short Name, and Biller Long Name.
5.3 The system should validate the accuracy of the saved data in comparison to the scraped data.
5.4 If the system fails to save any scraped data correctly, it should log an error and continue with the next biller code.
Non-Functional Requirements
Acceptance Criteria
The project will be considered successful when:
The system can accurately and reliably scrape data for biller codes from the specified website.
The system can handle large lists of biller codes and provide a structured and accurate output file.
The system gracefully handles errors and edge cases.
The system complies with all stated non-functional requirements.
The end-users express satisfaction with the system's ease of use, reliability, and performance.
This will ONLY be a one off exercise
This document articulates the functional requirements for a screen scraping project aimed at gathering biller code, Biller Short, and Biller Long Name data from https://bpay.com.au/look-up-biller-code-financial-institution.
Scope
The primary purpose of this project is to automate the process of searching and extracting data from a predefined list of biller codes. The output should be a comprehensive, well-structured spreadsheet containing the biller code, Biller Short, and Biller Long Name associated with each biller code in the list.
Requirements
1. Input List
1.1 The system must accept an input list containing multiple biller codes.
2. Web Interaction
2.1 The system must navigate to the specified website: https://bpay.com.au/look-up-biller-code-financial-institution.
2.2 The system should be able to handle any network or loading issues encountered while accessing the website.
3. Search Functionality
3.1 The system must sequentially search each biller code from the list in the website's search functionality.
3.2 If a particular biller code does not return any result, the system should log it for review.
4. Data Scraping
4.1 Upon successful search, the system should scrape the following details:
Biller code
Biller Short Name
Biller Long Name
4.2 The system should ensure the accuracy of the scraped data.
5. Data Storage
5.1 The system should store the scraped data in a structured format such as a CSV or Excel file.
5.2 The output file should contain separate columns for Biller Code, Biller Short Name, and Biller Long Name.
5.3 The system should validate the accuracy of the saved data in comparison to the scraped data.
5.4 If the system fails to save any scraped data correctly, it should log an error and continue with the next biller code.
Non-Functional Requirements
Acceptance Criteria
The project will be considered successful when:
The system can accurately and reliably scrape data for biller codes from the specified website.
The system can handle large lists of biller codes and provide a structured and accurate output file.
The system gracefully handles errors and edge cases.
The system complies with all stated non-functional requirements.
The end-users express satisfaction with the system's ease of use, reliability, and performance.
This will ONLY be a one off exercise