Android application use case diagram, how to make one?

Question

Android

Cutting app. The user selects the part that he wants to cut, enters the number of these parts, selects the width and length of the parts, indicates how many mm to allocate for seams, the type of fabric from which this part will be and the width of this fabric (since the width of the fabric is limited in stores). When you press a button, all the data is generated and the details are laid out on the fabric so that less fabric (which was selected earlier) would be spent.
You need to properly chart your use cases!
It is also correct to make a list of what I want to see in the application ... (the so-called wishlist)