For the following $3$ problem descriptions, identify the nouns and verbs $($separately$)$ in each.

Note: You will end up with $6$ separate answers for this section $-$ the nouns & verbs, then the algorithm, for each of the $3$ problems.

Write two separate lists $($with subheadings$)$ for each. If you're writing your answers using Word, you could copy the text and highlight each type of word in different colours or similar.

$($Don$\text{'}$t get hung up on the exact details of the words.$)$

Then go through the set of nouns and verbs and work out which ones are irrelevant or duplicated and remove them from the lists.

See if what's remaining is what you need to know to write an algorithm.

$1.$A doctor needs to be able to calculate the total amount of a drug that has been administered to a patient. The system will get the hourly dosage from the user, as well as the number of hours they have been receiving the medicine. The system will then display the total for the doctor.

$2.$Happy Photos needs a way to calculate the total charge for a customer's booking. The system will use the customer's name and the date of the booking to make a unique booking id$.$ The hourly charge, and number of hours will be entered, and the total charge and id code will be displayed.

$3.$A road trip planning system will ask the user for the distance travelled $($in $km)$ and the travel time in minutes. The user will then be shown the average speed $($in km$/$hour$)$ over the trip.

When you've decomposed these small problems into their parts $($word types$),$ write algorithms for each of them using either pseudocode or flowcharts.

At this stage, we're not worried about getting the details 'perfect', we just want to get used to problem solving processes.

As you do this, think about what assumptions you're making.

Good assumptions are an important part of IT and problem solving.