The problem here is that Assignments and assessments are normally
designed to teach you certain skills ... skills that are essential in
/your/ development as a programmer. If someone else where to do the
majority of /your/ code, then they have learned the lesson and /you/
have learned nothing.

The formula for both examples is given to you, but not in a clear cut
Formula a = x+y^2 kind of way. You have to pull apart the formula from
the specs ...

As for the code, assuming that it is all from the command line, or your
school uses some sort of GUI helper for the GUI ... it really isn't that
advanced.

After a very brief overview of the two problems  all you really need to
do use if/else blocks, loops and read  in and write  out the System.in and
System.out. It won't be pretty, but it will work.

What I would do if I where you, is to identify each of the tasks on a
sheet of paper (like, Task 1: A user must be able to enter  their wage
(That isn’t written in your problem, but I assume that the user enters
in their wage)). Continue pulling out all of the Tasks until you don’t
think there are any left, don’t try and force a task out of it though,
at least not yet.

After you have done that, look though your tasks. Identify which task
simply has to be done first (probably getting the wage in), then try and
find what you think the next most important task is going to be
(probably finding out how many dependants they have) and so on until you
think you have identified which order you should do everything.

Now load up your .java editor of choice and build up your class file.
Write your program  to satisfy the first task and no more. Write some
sort of test to make sure that it got in somewhere (putting it to
System.out is always an easy way of doing that). Once that is working,
put that task down, and move to the next task and so on.

If you look at an entire problem, it is easy to get overwhelmed, if you
break it up into simple chunks it gets much easier.