Use the program from Part 2 of Assignment #7 as your starting point! (The details are below for
convenience 1. Design and code a program to create a letter frequency table (you must a 26 entry
integer array) From Assignment #7: Part 2: a. Write a program to aceept a one-line string
(maximum of 100 characters) from the keyboard. b. Edit the string entered in (a) (with code that
you write) to remove all the white space, digits, punctuation, and other special characters, leaving
only the letters. c. Print out the resulting compressed string to the sereen. Example: If the input
string was "If I've told you once, Ive told you 1000 times!!" Then the output string would be
"Iflvetoldyouoncelvetoldyoutimes" that counts how many times each letter is used in your
compressed sentence for Part 1. Count upper case letters as if they were lower case. 2. Print out
the numbers in this table to the sereen starting with the frequency of " a " and continuing to the
frequency of " z ". 3. Format the table output to consist of two horizontal lines with 13 numbers in
each line. Separate the numbers on the line by a single space. The appropriate output here for the
input example from Assignment 7 Part 2, would be Letter Frequency Table 0012410040021
1500013220020 4. Have the program handle multiple data sets and terminate execution when a
null input string is entered. 5. S 6. Your code should be thoroughly commented! Do not define
syntax in your code comments, but rather explain what that line or group of lines is doing to
contribute to the overall goals of the program. a. At the beginning of the program, there should be
a preamble block of comments. At a minimum, this should include your name, class, section,
assignment number, program title, and date. b. There should also be a block of comments at the
beginning of your code that describes your design. Here, define inputs, outputs, assumptions,
constraints, and a high-level overview of processes and the overall functionality of the program. c.
Before major/logical sections of code, use header comments that explain what the section that
follows accomplishes. d. Every line of your code should have a comment. Comments should not
define syntax, but rather should explain the contribution of the line of code to the overall
functionality goals of the program. e. Be sure to use tabs to align your opcodes, operands, and
comments. This allows readability and there will be point deductions if this is not done properly. f.
Your comments should make your code self-documenting, and I should be able to understand the
functionality and purpose of the program by simply reading the comments. Design - 30 Pts /
Functionality - 40 Pts / Comments - 30 Pts.
Use the program from Part 2 of Assignment 7 as your startin.pdf
1. Use the program from Part 2 of Assignment #7 as your starting point! (The details are below for
convenience 1. Design and code a program to create a letter frequency table (you must a 26 entry
integer array) From Assignment #7: Part 2: a. Write a program to aceept a one-line string
(maximum of 100 characters) from the keyboard. b. Edit the string entered in (a) (with code that
you write) to remove all the white space, digits, punctuation, and other special characters, leaving
only the letters. c. Print out the resulting compressed string to the sereen. Example: If the input
string was "If I've told you once, Ive told you 1000 times!!" Then the output string would be
"Iflvetoldyouoncelvetoldyoutimes" that counts how many times each letter is used in your
compressed sentence for Part 1. Count upper case letters as if they were lower case. 2. Print out
the numbers in this table to the sereen starting with the frequency of " a " and continuing to the
frequency of " z ". 3. Format the table output to consist of two horizontal lines with 13 numbers in
each line. Separate the numbers on the line by a single space. The appropriate output here for the
input example from Assignment 7 Part 2, would be Letter Frequency Table 0012410040021
1500013220020 4. Have the program handle multiple data sets and terminate execution when a
null input string is entered. 5. S 6. Your code should be thoroughly commented! Do not define
syntax in your code comments, but rather explain what that line or group of lines is doing to
contribute to the overall goals of the program. a. At the beginning of the program, there should be
a preamble block of comments. At a minimum, this should include your name, class, section,
assignment number, program title, and date. b. There should also be a block of comments at the
beginning of your code that describes your design. Here, define inputs, outputs, assumptions,
constraints, and a high-level overview of processes and the overall functionality of the program. c.
Before major/logical sections of code, use header comments that explain what the section that
follows accomplishes. d. Every line of your code should have a comment. Comments should not
define syntax, but rather should explain the contribution of the line of code to the overall
functionality goals of the program. e. Be sure to use tabs to align your opcodes, operands, and
comments. This allows readability and there will be point deductions if this is not done properly. f.
Your comments should make your code self-documenting, and I should be able to understand the
functionality and purpose of the program by simply reading the comments. Design - 30 Pts /
Functionality - 40 Pts / Comments - 30 Pts
