Write the Java code (IntelliJ) to produce the following :
Requirements: The user wants a program to track how much medicine is in a patients body. Concentration is typically an amount in units per liter. The formula to use is the total amount of medicine left from each dose at a given time.
Setup: they use it expects to initially set three parameters. The parameters are the name of the medicine, the Tmax, and the half life.
*BASIC FEATURE:* The user wants to enter information about doses. The input is in two forms. The first is just the amount of medicine. The second is the amount and the time the patient takes it. If the input is in the first form, just the amount, the software must assume that the patient is taking the medicine now. The dose time is this the current time. But if the input is in the second form, including both amount and time, the software must use the inputted time, not the current time.
CONTEXT: A dose is when the patient takes the medicine and the size. Each time the patient takes a dose the medicine follows a concentration formula. The first part is the rise after the patient takes the medicine the second part is the fall, how the amount of medicine decreases in the body. For each does the amount of medicine rises in a linear fashion, starting at zero. It peaks at Tmax. Once at Tmax it begins to fall. The half-life is the amount of time the concentration needs to decrease by half.
ltWare solution. yu This projct tesls The most number of points for this exercise is as follows Parts and grading 230. Each part is worth a predetermined number of points. It is part un tesse 1. 100 points-testing The software is useless to the client if testing doesn't cover the enti boundary conditions and exceptions receive more points. Tests tha exceptions drastically decrease the amount of points under this part. Every public method Every class must have a test class. All logic needs a test. All input needs a test. All ou Remember that tests are specific. They test a specific expectation of the code. Tests that cover t do not cover boundary conditions and must have a test. tput needs a test. roject, I will not hold back trying to find a way to break your program.IfI brealk your program and you at least have a test that covered the area, but did so unsatisfactorily, thus to break your program, I will not deduct as many points. We're human. It's therefore difficult to reco every possibility. But not testing an area at allis 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 skimpn allowing me 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 proj commits you make, the better. The more descriptive the comm ect. How well you use it affects the points under this part. The more its you make, the better. Page 1 of 3 exopt: Mou ltWare solution. yu This projct tesls The most number of points for this exercise is as follows Parts and grading 230. Each part is worth a predetermined number of points. It is part un tesse 1. 100 points-testing The software is useless to the client if testing doesn't cover the enti boundary conditions and exceptions receive more points. Tests tha exceptions drastically decrease the amount of points under this part. Every public method Every class must have a test class. All logic needs a test. All input needs a test. All ou Remember that tests are specific. They test a specific expectation of the code. Tests that cover t do not cover boundary conditions and must have a test. tput needs a test. roject, I will not hold back trying to find a way to break your program.IfI brealk your program and you at least have a test that covered the area, but did so unsatisfactorily, thus to break your program, I will not deduct as many points. We're human. It's therefore difficult to reco every possibility. But not testing an area at allis 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 skimpn allowing me 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 proj commits you make, the better. The more descriptive the comm ect. How well you use it affects the points under this part. The more its you make, the better. Page 1 of 3 exopt: Mou
