Program Documentation: Key Components and Best Practices

Title and Purpose

1.Title: a paragraph clearlystating title, author, date, file names, and one-line statement of purpose.2.Requirements/Specification: a paragraph giving a brief account of what the program is supposed to do. State any assumptions or conditions on the form of input and expected output.3.User Guide: include clear instructions on how to compile and run the program, and how to use the program during execution.4.Structure/Design/Algorithm: Outline the design of your program (it is here that you will need to justify any extra instance variables and class methods that you have included in Changeclass). Give a written description, use diagrams (UML class diagram and structure chart), and use pseudocode for algorithm.5.Limitations: Describe program shortfalls (if any) e.g.: the features asked for but not implemented the situations it cannot handle, etc.6.Testing: describe your testing strategy (the more systematic, the better) and any errors noticed. Provide a copy of your results of testing in a document saved in Word format. Note that a copy of the sample test data and results from a program run for each program is required (copy from the program output window and paste to a Word file). Your submitted test results should demonstrate a thorough testing of the program.7.Source program listings: save all your Java source code in a document in MS Word format