Create a simple MVC Web App Class is StudentWorkerModel with properties name, id, hourly pay, hours worked, and method weeklySalary(). Make sure your method calculates the weekly salary using the class methods, there is no need to pass any values to the method. Set the values in the code, and on the page, display student name and the weekly salary. Must be a Web Application GUI components: Button Clear User Input for necessary information in your model Model should include input validation and print to GUI when non-numeric input or invalid input is input Documentation Comments Header must include problem description Must include at least 1 class Must include Unit tests with good coverage (include edge cases and use cases) Test your StudentWorkerModel. Business logic: Workers can work 1 to 15 per week and pay rate starts at $7.25 and can be up to $14.75 per hour. If there is an issue, pay should be returned as zero. The administrator will check for zero paychecks to fix errors and re-run payroll for those individuals. NOTE: It is okay but not required to throw expections as long as you handle them and your program does not break. Tests you need to add, selecting appropriate test names:.
Test 1. Invalid hours worked (too low)
Test 2. Invalid hours worked (too high)
Test 3. Invalid hourly salary (too low)
Test 4. Invalid hourly salary (too high)
Test 5. Valid test

My favorite is "be concise."have you ever received an email and had to read a page full of information? by the time you finished reading it, you had to re-read it? i have even hit "reply" so that i could break it down into separate paragraphs and send it back to myself.what is concise? get to the point, fast. when opening an email like this, some will close it or print it to read later.i learned to use the subject line to prepare the reader for content. such as, "need on (blank), " "info only re: (blank)," "request input on (blank)," "read before (blank) meeting." these are just some.if you are asking for something, make that your first sentence. follow this by who, what, when, where, and how. use these, as necessary. example; (1) who (who needs it and or who does it), (2) what (specific description of what is needed), (3) when (specific, i need this by 8: 00 am monday or i need this by 10: 00 am today), (4) where (does it have to be printed and taken to someone, maybe the place of the meeting), (5) how (i need it scanned or faxed back to me at this email address, provide me with a hard copy).do not send yet. re-read it. did some spell check change a word? maybe let someone else read it for understanding. you want to avoid multiple emails asking for clarification. if important, put a read receipt on it. you will know it was opened, not necessarily read.end with a you.

Ithink the answer is both.