There is a katakana restaurant, ABCD restaurant, has a problem to maintain continuity raw materials, ingredients needed in the kitchen, with orders that come. The obstacle that faced are:

a. Frequent occurrence of spoilage/damaged materials, resulting in wasted raw materials, wrong prediction.

b. Or often the order is not served, because there is no raw material inventory (or unfit for use, because it is rotten), the age of the raw materials, is not considered, or there is a periodic checking.

c. Goal: with a system that can support operations, completeness of materials default, there are several possibilities:

• There are sufficient raw materials, and not excess. Able to predict better.

• When the raw material is on the verge of running out, you can control check and order to supplier, time to market, always fresh.

• When there are too many raw materials, and they are about to expire, it can trigger a menu promo certain. Create discount opportunities.

From the description above, make:

a. Define the problem at hand, and specify the expected inputs and outputs as purpose, and can define some menus, and some raw materials required, and the control limits for which the solution is intended.

b. Use case diagrams (there are at least 5 use cases), to answer the expected goals.

c. Class diagram complete with attributes and methods as well as relationships between classes.

d. Make 3 interaction diagrams.

You can add “Assumptions”, if necessary. However, make sure that there are proper explanations and reasons to support your "Assumptions"