OverviewYou are a senior software developer on a team of software developers who are responsible for a large banking application. Your manager has learned that the code used for addition and subtraction over a series of steps will sometimes calculate incorrect results. The other developers have spent a lot of time tracing down the issue, and they narrowed it down to two functions: add_numbers() and subtract_numbers(). Following some guidance from an older testing guide, they isolated those functions in a standalone set of test cases. Doing this allows them to reliably show how to trigger an underflow or overflow. However, they don’t know what to do to prevent it from occurring in the future. They came to you for help.You will learn to do the following:Detect when a numeric overflow or underflow is about to happenWrite code to prevent the numeric overflow or underflow from happeningProtect your code from underflow and overflow in any of the standard C/C++ data typesPromptThis assignment presents code that is designed to show the two functions operating with and without overflow or underflows. Using the existing source code, you will add logic to the add_numbers() and subtract_numbers() functions to detect, prevent, and notify the caller of a numeric overflow. You will also modify the calling test_overflow and test_underflow functions to be notified of success or failure of the add or subtract functions they call, and to modify them, the functions write to the console with overflow status (true or false) and the numeric result of the function.The following are a few key notes:The source code has been commented with TODOs to explain the detailed rules you must follow.There are comments that mark code that must be changed.There may be more than one way to solve this problem, so be sure to demonstrate that you can detect an underflow or overflow, prevent it, and communicate it back to the calling function.Remember to leverage capabilities provided by the standard C++ library to help you achieve success.Please comment on any changes you make in the code to explain the logic, formulas, or data types you are adding. You will also create a brief written summary of the approach taken. It should explain how this approach is designed to stop the overflow or underflow, any issues you encountered, and how you resolved those issues.Specifically, you will prepare the following:Numeric overflow and underflow secure codingC/C++ program functionality and best practicesA summary of your process in a Word document that contains a screenshot of the application console outputTo complete this assignment, download the Numeric Overflow source code to use as guidance as you move through the activity. You will use your development environment to complete this activity.Guidelines for SubmissionSubmit the modified source code as a ZIP file. Also include a Word document that contains a complete screenshot of the application console output and a brief summary of your process.

Critical Thinking/Analysis How does risk impact testing? Why should risk be considered when testing? Analysis should be at least 350 and less than 450 words. Defect/Incident Reporting Exercise Assignment Description: Review the test findings from Week 8 based on testing the parking lot calculation application located at http://adam.goucher.ca/parkcalc/ Re-test the application if needed. Formally document any defects or failures you found in an incident report. Include at least 5 defects in your incident report. At minimum, include the following information within your report for each defect or failure. Defect summary Incident description (expected results, actual results, what you entered, date/time) Priority or severity Steps followed to create/recreate issue Include error descriptions/messages, if appropriate Provide screen prints as needed Calculate and report basic testing metrics to help provide a feel for the status of your testing efforts, health of the software being tested, and effectiveness of your testing efforts. At minimum, include: Total Defects (overall measure of software quality) Test case testing ratio (indication of testing status) è Test cases tested / total test cases Failure Rate è # failures per unit of time (usually # failures per hour) Defect Density (measure of software quality) è total # defects / # test cases completed Critical Bug Detection Rate (measures testing effectiveness; testing resources should be focused on finding the highest risk defects) è# high priority bugs / # total bugs * 100% Weekly Discussion Forum Posts Post an original thread of 300 to 450 words in response to the following topic in this week’s discussion forum. (20 points) Discussion Forum Topic: Why are incident reporting and metrics important to testing? What does this information help to communicate?

For Milestone One, you will submit a written report in which you analyze the communication environment that exists within BOLDFlash and discuss the particular areas of concern. Specifically the following critical elements must be addressed:  Background and Area of Focus: Analyze the communication environment that exists within BOLDFlash, and discuss the particular areas of concern.  Define the area that you feel should be your focus to start. Specifically, describe which area (internal business processes, product documentation, or technical service communication) you feel is the most important to fix first, and describe why. Provide your reasoning.  Key Stakeholders: Discuss your framework for planning and communicating with the stakeholders in your chosen area. Determine who the stakeholders are, why they are stakeholders in your chosen area, and how your communications will affect them.  Established Practices: Identify established communication practices that would benefit your approach to communicating with the stakeholders that you have identified. Provide evidence to support your conclusions.  Framework for Communication: Construct a framework for continued communication, both technical and nontechnical, with the identified stakeholders. This framework will be the one to which the Mobile Division management team will refer when tasked with special projects. Guidelines for Submission: This submission should be 4–6 pages long (not including cover page and resources if applicable) and must follow these formatting guidelines: double spacing, 12-point Times New Roman font, one-inch margins, and APA-style citations.