D480 Software Design and Quality Assurance QA Test Plan Task 2 Software Design Overview & Functional

D480 Software Design and Quality Assurance QA Test Plan Task 2: Software Design Overview & Functional Requirements Test Plan 2025-2026 Western Governors University

Quality Assurance Test Plan – Task 2 A. Overview of Software Design Plan A1. Summary of the Software Design Plan The software design addresses a logic error in the Endothon Finance loan application web app, where the system currently requests the first five fiscal years of financial data rather than the most recently completed five years. The design introduces a year calculation module, conditional logic for younger businesses, validation checks, and forecast year handling. These updates ensure that the system correctly identifies the required financial years based on the business’s age and the current year.

A2. Functional Requirement Objective Objective: To ensure the web app correctly identifies and requests the five most recently completed fiscal years, and if needed, includes forecast years for younger businesses.

A2a. Functional Quality Metrics

- Accuracy of year calculation - Validation success rate - Forecast logic engagement Relevance: These metrics ensure the loan profiles contain relevant financial data, improving accuracy for vendor evaluation and meeting core business logic.

A3. Non-Functional Requirement Objective Objective: To ensure the updated web app logic is maintainable and performs efficiently within the user's session experience.

A3a. Non-Functional Quality Metrics - Execution time (<1 second) - Code modularity - Logging effectiveness Relevance: These ensure system responsiveness, easy future updates, and traceable behavior for debugging or audits.

B. Project Scope B1. In-Scope Functional Requirements for QA - FR1: System selects and displays the five most recent completed fiscal years.

- FR2: Forecast fields appear only when the business age is <5 years.

B2. In-Scope Non-Functional Requirements for QA - NFR1: System performs year selection logic in under 1 second.

- NFR2: Logging module correctly records each financial data request attempt.

B3. Out-of-Scope Functionalities 1. UI Redesign of Application Form - Alignment: Better UI could improve clarity, aligning with usability goals.

- Out of Scope: The current ticket focuses on fixing logic, not visual elements.

2. Enhancement of Lender Matching Algorithm - Alignment: More accurate data could improve vendor matching.

- Out of Scope: Matching logic is outside the year selection module’s scope.

C. Testing Strategy C1. Test Case Table Test Type Description of Test

Objective

Test Owner

Environment

Unit Test

Input a business creation date of 2000, system year is 2023.

Expected output: 2018– 2022.

Validate correct year range (FR1)

Developer

Local dev environment with Jest or Mocha

Unit Test

Input business creation year 2021 with current year 2023.

Expected: 2021, 2022, 2023 (actual) and 2024, 2025 (forecast).

Ensure correct forecast logic (FR2)

Developer

Node.js/React app environment

System Test

Time the year selection logic after user inputs creation date. Must

Meet performance expectation (NFR1)

QA Tester

Web staging server

complete in <1 second.

Integration Test

Submit application and review logs.

Verify that selected year ranges and timestamps are recorded.

Ensure proper logging (NFR2)

QA Tester

Dev server + logging viewer tool

C2. Logical Sequence of Testing 1. Unit Tests for Year Logic and Forecasting - Expected Result: Each logic function (e.g., year selection, forecast handling) produces correct output with a variety of inputs.

- Justification: Ensure foundation is solid before testing integrated components.

2. Integration Test for Logging Accuracy - Expected Result: Logs include correct year data and timestamps when an application is submitted.

- Justification: Must validate internal recording mechanisms before performance testing.

3. System Performance Test - Expected Result: Web app performs the full year calculation in <1 second.

- Justification: Verifies speed does not degrade with real-world conditions.