Identify the steps in the software development process in the correct order with the description for each step.

Step Descriptions

Understand the problem. Work with your client or customer to define and understand precisely what the problem is and why a solution is needed. You will ask many questions of your client or customer. You will then review the information you received with your client or customer. You need to ensure that you answer the what, where, why, and when questions as thoroughly as possible during this review. The more information that you gather to understand the problem, the more requirements that you will obtain before moving on to the next step.

$[$ Select $]$

Plan and design the logic. Once you understand the problem, you will use the information gathered to plan the logic to your solution. During this planning, the design of your solution will take shape. Sometimes, during the planning process, you determine that you need more information. It is okay to go back to the first step in the process to gather more information in order to understand the problem. Usually, the planning involves a three$-$step process: identify the input, identify the processes, and identify the outputs. The input is what the program will receive while it executes or runs. The processes are the calculations. The outputs are the results sent to the customer or user of the program.

$[$ Select $]$

Develop the logical solution. After you understand the problem and plan and design the logic, you are ready to develop the logical solution to the original problem. The logical solution is determined by using design tools, such as pseudocode and flowcharts, to develop documentation to be passed to the programmers for coding. Pseudocode designs are English$-$like statements that can easily be translated to actual programming code. Flowcharts are a visual representation of the flow or process of the solution. During the design, you will determine the data variables necessary to store the data and the step$-$by$-$step algorithm for the solution.

$[$ Select $]$

Desk$-$check the design. During this step, you will complete a desk$-$check of your logic. You will develop some sample test data to test your logic and ensure that the solution will work. You will look for logic mistakes $($errors$).$ Remember, your solution needs to produce the correct results. If your solution gives you the wrong answer, then your solution is not valid. Think of it this way. You deposited $$50$ into your checking account using your ATM. Your previous balance was $$100.$ You expect your new checking account balance to be $$150.$ Your deposit receipt says that your checking account balance is $$50,$ not $$150.$ You are not happy. The solution was incorrect. The program deducted the deposit amount instead of adding it to your balance. By completing a test with sample test data, you will be able to resolve many mistakes $($errors$)$ well before the customer or user sees it live. Complete a walk$-$through of the logic.

$[$ Select $]$

Translate the design into code. Translating the design into code means completing the program in the selected programming language $($C#$,$ C$++,$ python, etc.$),$ which is comprised of human$-$readable instructions that represent the program design. However, in order to execute on a computer, the human readable programming language code must be either compiled or interpreted into machine language in order for the computer to understand the program, and this compilation is part of the programming process.

$[$ Select $]$

Deploy the solution. When everything is completed, the final step is to put your solution live. You will deploy, or put, your solution into production. The customers will begin using your solution. How exciting is that? Your solution may now be used by thousands upon thousands of customers, maybe from even around the world.

$[$ Select $]$

Documentation: The two types of documentation, internal and external, are useful when changes or troubleshooting are necessary. Examples of internal documentation would be comments after lines of code that explain what it does. External documentation can consist of hierarchy charts and desk$-$checking tools in order to validate the program's requirements and make adjustments if necessary.