Each week, you will submit the following.
- Current IPO chart and pseudocode
- MS Visual Studio Project folder
- Completed Test Plan (Screen shots of working program)
Put the IPO chart, pseudocode, and test plan in the MS Visual Studio project folder, zip up the entire folder, and submit the compressed file.
Week 1: Decide on your project program, and write a brief description of what the program will do. Prepare an IPO chart for your program. Create two or three sample screens (using Word or a drawing program) depicting what your program will look like to the user (remember that these will be console-based programs).
Week 2: Create a flowchart for a simplified version of your program. Create a working version of it based on your flowchart. This should be a working program that accepts user input, does some calculation, and shows the results. It does not have to use conditional expressions, loops, and the like.
Examples: For the programming tutorial, you can describe and demonstrate to the user using screen output, how to declare variables, display information on the screen, get information from the user, and do calculations. You can ask the user for their name and include it in the tutorial output.
For a loan payment calculator, it asks for interest rate, length of loan, amount of loan, and it displays monthly payment. For a DJ manager, it asks for the average song length and the number of songs on a playlist, and it displays the length of the playlist.
Week 3: Add at least one conditional expression to your program.
Examples: In the programming tutorial, you would add a tutorial on conditional expressions. You can then add simple multiple choice questions to test the user’s understanding of the concepts. You might also want to break the tutorial into sections, and use conditional expressions to ask the user which tutorial they wanted to see (i.e., variable declaration, input/output, conditional expressions, etc.).
For the loan calculator, the program might ask the user if he or she wants to solve for monthly payment, loan amount, length of loan, or interest rate. The program would then ask for the required information and solve for the remaining value.
Week 4: Add loops to validate data. Add a menu to your program that allows users to use the various features or exit the program.
Examples: In the programming tutorial, add a tutorial on working with loops. Then use loops to validate user input and display an error message if they enter data outside the valid range. Use a main loop to allow the user to keep selecting different tutorials until they decide to exit the program.
Week 5: Add arrays to your program to handle more data.
Examples: In the programming tutorial, add a tutorial on working with arrays. Then use arrays to store the answers to multiple questions so that you can compute a total score.
In the DJ program, you can add the ability to handle multiple songs and playlists. The electrical program should handle multiple customer scenarios.
Week 6: Create a hierarchy chart showing the logical components of your program. Modularize your code according to your chart using the practices learned this week. Your menu should now call individual modules to do the work of the program.
Examples: In the programming tutorial, add a tutorial on working with modules. Then modularize the code so that each tutorial and quiz is in a module.
Week 7: Add the ability to save data to disk in one or more files. The menu(s) should give the user the option to save or retrieve data.
Examples: In the programming tutorial, add a tutorial on working with files. Then add the ability to save/retrieve user information or quiz results.
Each week needs to be an individual file.