Your task is to design an information model in the ORM modelling language that suggests an effective and efficient way for storing SoftMarts data. Complete the drawing of the ORM conceptual schema proposed below for the universe of discourse specified in the scenario by performing steps 1-5 of the Conceptual Schema Design Procedure. Use only those entity types and value types proposed below (do NOT introduce any new entity/value types). You may realign or rearrange the entity and values types to suit the layout of your model.

Step 1: Transform familiar examples into elementary facts and apply quality checks List the significant deep structure sentences that can be identified from the scenario description. For

example: The Invoice with InvoiceNr 0501 was issued to the Customer with CustomerNr 001.

It is not necessary to list several fact type instances that describe the same fact type.

Step 2: Draw the fact types and apply a population check Draw a fact type, including a sample fact table, for each of the deep structure sentences identified in Step 1.

For example, consider the only binary fact type shown in the diagram above. Note that this fact type is introduced based on the example deep structure sentence proposed in the description of Step 1. Perform a population check by populating identified fact types with the fact instances from the scenario. This can be accomplished by drawing fact tables.

For all the identified fact types discuss/demonstrate that they are indeed elementary by performing all the necessary split and join operations on sample populations. Finally, combine all of the identified fact types into a single ORM model.

Step 3: Check for entity types to be combined and note any arithmetic derivations Discuss (in text) whether it makes sense to combine any of the entity types proposed in the diagram. If so, describe the combination; if not, explain why not. In this discussion do not exceed the word limit of 300 words. Introduce TWO arithmetically derivable fact types in your ORM model. You can use mathematical notation or a textual description to specify derivation rules.

Step 4: Add uniqueness constraints and check the arity (length) of fact types Introduce all necessary uniqueness constraints into your ORM model based on the scenario. For each introduced uniqueness constraint, briefly explain the rationale behind your decision to include it in the model.

Step 5: Add mandatory role constraints Introduce all necessary mandatory role constraints into your ORM model based on the scenario. For each introduced mandatory role constraint, briefly explain the rationale behind your decision to include it in the model.

CustomerName Address PhoneNr i was issued to Customer Invoice Date (.DMY) (.Nr) Lineltem Quantity UnitPrice (AUD:) ItemTitle ListPrice (AUD:) Item (.Code) Code) CustomerName Address PhoneNr i was issued to Customer Invoice Date (.DMY) (.Nr) Lineltem Quantity UnitPrice (AUD:) ItemTitle ListPrice (AUD:) Item (.Code) Code)