**question/assignment is after the attachement**

**

The point of this assignment is to show that you are thinking broadly about Project 1. Take an hour or so and just think about what it will do. Generalize the information that'll be brought in. Think about boundaries that might apply. How will the user interact with the program? What will he type in or click? Submit your answer as text. Example: "I think three classes will be used. One class will be the date and times; one class ... "The first class will use the cycle through method in the second class. ... "The user will input "banana time amount" and "amount" will show ..."

Project 1 Objective This project tests your ability to organize code coherently and to produce a valuable software solution Parts and grading The most number of points for this exercise is 230. Each part is worth a predetermined number of points. It is as follows: 1. 100 points-testing The software is useless to the client if testing doesn't cover the entirety of the code. Tests that cover boundary conditions and exceptions receive more points. Tests that do not cover boundary conditions and exceptions drastically decrease the amount of points under this part. Every public method must have a test. Every class must have a test class. All logic needs a test. All input needs a test. All output needs a test. Remember that tests are specific. They test a specific expectation Hint: While I'm grading the project, I will not hold back trying to find a way to break your program. If I break your program and you at least have a test that covered the area, but did so unsatisfactorily, thus allowing me to break your program, I will not deduct as many points. We're human. It's therefore difficult to recognize every possibility. But not testing an area at all is avoidable. If I break your program because of a method and the method had no test at all, I will deduct a lot of points. It's better to have more tests than to skimp on tests 2. 60 points- implementation Organization of code, use of interfaces, good separation of concerns, minimizing dependencies, effective use of objects, and thorough commenting and descriptive naming make up the metric under this part. Keep these ideas in mind: Interfaces guide implementation; Objects depend more on interfaces than other objects to minimize dependencies; Simple code is better code 3. 40 points-documentation Use whichever documentation framework or program you want to use. You must explain to me every part of the program through documentation. The document must be user-friendly. It must have an index and thorough descriptions of classes, fields, methods, interfaces, enumerations, and resources. It is not necessary to include test classes, fixtures, or their contents in documentation. If you do include them, it should be in a separate file. Documentation must be in PDF format. 4. 30 points -git You'll have to use git for this project. How well you use it affects the points under this part. The more commits you make, the better. The more descriptive the commits you make, the better