A.Using the "Quality Assurance Test Plan" supporting document, provide an overview by doing the following:

1.Summarize the proposed software design plan from Task 1, including identification of the problem statement being addressed from the attached "Background Information" (i.e., scenario, ticket).

2.Identify the overall objective of the functional requirements to be tested during the quality assurance process, aligning the objective with the summarized software design plan in part A1.

a.Summarize the quality metrics associated with the overall objective of the functional requirements, including an explanation of why the identified metrics are relevant to the software design solution.

3. Identify the overall objective of the non-functional requirements to be tested during the quality assurance process, aligning the objective with the summarized software design plan in part A1.

a. Summarize the quality metrics associated with the overall objective of the non-functional requirements, including an explanation of why the identified metrics are relevant to the software design solution.

B. Using the "Quality Assurance Test Plan" supporting document, identify the project scope by doing the following:

1.Identifytwo in-scope requirements to be tested within the quality assurance process that are aligned with the overall objective of the functional requirements identified in part A2.

2.Identify two in-scope requirements to be tested within the quality assurance process that are aligned with the overall objective of the non-functional requirements identified in part A3.

3.Identifytwo out-of-scope functionalities that will not be tested within the quality assurance process.

a.For each identified functionality, explain the following points:

how the functionality aligns with the business requirement identified in part A1

why the functionality should be labeled as out of scope

C. Using the "Quality Assurance Test Plan" supporting document, outline the testing strategy by doing the following:

1.Provide an overview of the testing process foreach in-scope requirement identified in parts B1 and B2 by filling out the "Test Case Table" with the following information:

Test Type: categorize by test type (e.g., unit, integration, system, end-to-end)

Description of Test: summarize the testing technique(s) used to validate the in-scope requirement, including sample inputs and expected results

Objective: restate the associated overall objective, identified in part A2 or A3, met by the in-scope requirement

Test Owner: identify which stakeholder role will perform the test

Environment: identify the testing environment or tools required for the test

2. Define a logical sequence of testing for the testing process for each in-scope requirement provided in part C1, including the justification of the planned sequence of testing.

D. Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized.

E. Demonstrate professional communication in the content and presentation of your submission.

Attached is the proposed software design plan from Task 1:

. A. Business Case: Problem statement: Endothon Finance needs to launch a new web app to streamline the loan application process for small businesses. The web app should collect financial data for the previous five years of the business, excluding the current year. If a business is less than ve years old, the web app should collect the most current years of financial data and a forecast for the remaining years. Business requirements: a. The web app should collect the correct financial data for each business, based on its age and industry. b. The web app should provide a streamlined loan application process customized to each business. ln-scope action items: a. Develop logic for the web app to collect the correct financial data for each business based on its age and industry. b. Customize the loan application process for each business based on its details and financial data. Out-of-scope action items: a. Developing a machine learning algorithm to predict a business's creditworthiness based on its nancial data, as it is not currently a requirement. b. Integrating with third-party accounting software, as it is not part of the current project scope. B. Rguirements: Functional requirements: a. The web app should collect financial data for the previous five years of the business, excluding the current year. b. The web app should collect the most current years of nancial data and a forecast for the remaining years for businesses less than five years old. Non-functional requirements: a. The web app should be easy to use and navigate for businesses of different industries and ages. b. The web app should be secure to protect sensitive financial data. AENI: Software Design Software Design Plan 0. Software Design: Categories of inputs or events: a. Business details, including age, industry, and the number of employees. Intended web app response: Determine the nancial data collection requirements for the business and customize the loan application process accordingly. Associated constraints: None b. Financial data for the previous five years, excluding the current year. Intended web app response: Collect and store the financial data for each business. Associated constraints: None The intended design approach will segment the development and functionality of the web app elements into functions and classes to ensure modularity and ease of maintenance. D. Develo ment roach: Planned deliverables: a. User interface for the web app Steps: Conduct user research, create wireframes and mockups, design Ul elements, and implement the UI using HTML/CSS. b. Backend logic for financial data collection and loan application customization Steps: Develop algorithms to determine nancial data collection requirements and customize loan applications, and implement the backend logic using a programming language like Python. The planned sequence of deliverables will start with the UI design and implementation, followed by the backend logic implementation. This sequence is justified as it allows for user testing and feedback on the UI design before the backend logic is implemented. Development environment elements: a. Python programming language for the backend logic implementation. b. HTMUCSS for the UI design and implementation. c. MySQL database to store financial data. Expected software development approach: Agile methodology will be used to ensure flexibility and adaptability to changing requirements. This methodology was chosen over the waterfall methodology to allow for continuous feedback and iteration during development. E. Sources: None used. F. Professional communication: The response is written clearly and concisely with proper grammar and punctuation. Explanation: Approach to solving the question: AENI: Software Design Software Design Plan To approach this question, I would start by thoroughly reading and understanding the provided scenario and background information. I would then review the provided supporting document, "Software Design Plan," to get a sense of the structure and expectations for the response. Next, I would address each section of the prompt in order, making sure to fully answer each question and provide detailed explanations and justifications as necessary. I would also ensure that my response demonstrates professional communication and is well- organized and easy to follow. Throughout my response, I would cite any sources used in-text and provide a reference list at the end of my submission