AEN1: Quality Assurance Quality Assurance Test Plan
D480 Software Design and Quality
Assurance AEN1TASK 1: Quality
Assurance (Quality Assurance Test Plan)
2025 Western Governors University
Quality Assurance Test Plan
A. Overview
1. Software design plan summary
Endothon Finance's new web app for loan applications incorrectly retrieves financial data from the first
five fiscal years of a business instead of the five most recent. This bug impacts how loan profiles are
generated for businesses applying for loans, potentially causing delays or inaccurate loan assessments.
2. Functional requirements objective
The functional objective is to fix the web app logic so that it retrieves financial data from the most recent
five fiscal years, based on the business's establishment date. The logic should also request current and
future forecast data for businesses under five years old.
2a. Functional requirements objective metrics
Metrics for functional requirements include validation of data retrieval for the correct fiscal years,
number of corrected loan profiles generated, and successful loan processing for recent
applications.
3. Non-functional requirements objective
The non-functional objective is to ensure the web app processes financial data efficiently and maintains
performance under load, especially given the business-critical nature of the loan application process.
3a. Non-functional requirements objective metrics
Relevant metrics for non-functional requirements include response time for retrieving financial
data, load testing results for handling multiple loan applications, and system uptime during peak
business hours.
D480 Software Design and Quality
Assurance AEN1TASK 1: Quality
Assurance (Quality Assurance Test Plan)
2025 Western Governors University
Quality Assurance Test Plan
A. Overview
1. Software design plan summary
Endothon Finance's new web app for loan applications incorrectly retrieves financial data from the first
five fiscal years of a business instead of the five most recent. This bug impacts how loan profiles are
generated for businesses applying for loans, potentially causing delays or inaccurate loan assessments.
2. Functional requirements objective
The functional objective is to fix the web app logic so that it retrieves financial data from the most recent
five fiscal years, based on the business's establishment date. The logic should also request current and
future forecast data for businesses under five years old.
2a. Functional requirements objective metrics
Metrics for functional requirements include validation of data retrieval for the correct fiscal years,
number of corrected loan profiles generated, and successful loan processing for recent
applications.
3. Non-functional requirements objective
The non-functional objective is to ensure the web app processes financial data efficiently and maintains
performance under load, especially given the business-critical nature of the loan application process.
3a. Non-functional requirements objective metrics
Relevant metrics for non-functional requirements include response time for retrieving financial
data, load testing results for handling multiple loan applications, and system uptime during peak
business hours.
