NATIONAL INSTITUTE OF INDUSTRIAL ENGINEERINGMumbai 400087

MIS ASSIGNMENT

Submitted toProf Hema Date

Submitted by:-

Nikandan Kumar (44)Venkata Narasa Reddy D (70)Anee Varma (71)Rahul Kumar Varma (72)

Samples of Input Forms:Samples of Input Forms:

Company X uses the following for their system. There are two types Company X uses the following for their system. There are two types of manual forms:of manual forms:

First, invoices which used to record daily sales then they are First, invoices which used to record daily sales then they are collected weekly to sum up the sales and the number of sold items tocollected weekly to sum up the sales and the number of sold items to deduct it from inventory. Each invoice form contains:deduct it from inventory. Each invoice form contains:

Unique ID number.Unique ID number. Date of transaction.Date of transaction. Customer name.Customer name. Unit price. Unit price. Number of sold units.Number of sold units. Unit description.Unit description. Total.Total.

Second, inventories check form which used to monitor the number ofSecond, inventories check form which used to monitor the number of items on hand and to know when to order new items. They use one items on hand and to know when to order new items. They use one form each month. These forms consist of six columns:form each month. These forms consist of six columns:

11stst column contains item name. column contains item name. 22ndnd column shows items on hand at the beginning of the month. column shows items on hand at the beginning of the month. 33rd rd – 6– 6thth column shows the quantity on hand weekly after we column shows the quantity on hand weekly after we

deduct the items sold in that week. We can get the number of deduct the items sold in that week. We can get the number of items sold from the invoices.items sold from the invoices.

Entity Relationship Diagram (ERD):Entity Relationship Diagram (ERD):

Business Rules:Business Rules:

Each category has many items. Each item is included in only one category. Therefore, the relationship between Category and Items is 1:M.

The relationship between Invoice and Items is a M:M so, we The relationship between Invoice and Items is a M:M so, we divide this relationship into two 1:M relationships by using a divide this relationship into two 1:M relationships by using a bridge entity called Invoice Details.bridge entity called Invoice Details.

Each invoice has many invoice details, but invoice details is Each invoice has many invoice details, but invoice details is included only in one invoice.included only in one invoice.

So, the relationship between Invoice and Invoice details is 1:M.So, the relationship between Invoice and Invoice details is 1:M. Items can be entered in many Invoice Details, but invoice Items can be entered in many Invoice Details, but invoice

details has only one item.details has only one item. So, the relationship between them is a 1:M.So, the relationship between them is a 1:M.

Each Customer can take many invoices.Each Customer can take many invoices. One invoice is issued only for one customer.One invoice is issued only for one customer. So, the relationship between them is a 1:M.So, the relationship between them is a 1:M.

The relationship between Items and Purchase Order is a M:M The relationship between Items and Purchase Order is a M:M so, we divide this relationship into two 1:M relationships by so, we divide this relationship into two 1:M relationships by using a bridge entity called Purchase Order Details.using a bridge entity called Purchase Order Details.

Each Item is selected by many Purchase Order Details, but Each Item is selected by many Purchase Order Details, but Purchase Order Details has only one Item.Purchase Order Details has only one Item.

So, the relationship between item and Purchase Order Details So, the relationship between item and Purchase Order Details is 1:M.is 1:M.

Purchase order has many Purchase order details, but Purchase order has many Purchase order details, but Purchase order details is included in only one Purchase order.Purchase order details is included in only one Purchase order.

So, the relationship between them is a 1:M.So, the relationship between them is a 1:M.

Supplier can supply many Purchase order.Supplier can supply many Purchase order. A Purchase order is supplied by only one Supplier.A Purchase order is supplied by only one Supplier. So, the relationship between them is a 1:M.So, the relationship between them is a 1:M.

The Data flow Diagram (context diagram):The Data flow Diagram (context diagram):

The context diagram has one process called Ibn Aljawzi System and The context diagram has one process called Ibn Aljawzi System and three entities called Management, Suppliers and Customers. three entities called Management, Suppliers and Customers. Management gives Catalog information, Item information and Management gives Catalog information, Item information and Purchase order information as an input to the system and takes Purchase order information as an input to the system and takes Sales report, Purchase order report and Catalog list from the system Sales report, Purchase order report and Catalog list from the system as an output. The system takes Supplier information as an input fromas an output. The system takes Supplier information as an input from Suppliers and generates purchase order as an output. The system Suppliers and generates purchase order as an output. The system receives customer information from Customers as an input and receives customer information from Customers as an input and generates invoices to Customers as an output. generates invoices to Customers as an output.

Diagram Level O:Diagram Level O:

Diagram Level 0 has 3 entities, 8 processes and also 8 data stores. Diagram Level 0 has 3 entities, 8 processes and also 8 data stores. The flow of information between these components is shown in the The flow of information between these components is shown in the figure above as arrows with explanations on it.figure above as arrows with explanations on it.

Child Diagram for Process 5:Child Diagram for Process 5:

This diagram shows the steps followed in process 5. First, the purchase order ID, that’s come from process 4, is checked by process 5.1. Then, if it is a valid ID it moves to process 5.2 where items ID information is taken from process 2 in diagram 0. After that, process 5.3 calculate the total for the purchased order and generates a report to Management and a purchase order to Supplier.

Child Diagram for Process 8:Child Diagram for Process 8:

This diagram shows the steps followed in process 8. First, the invoice ID, that’s come from process 7, is checked by process 8.1. Then, if it is a valid ID it moves to process 8.2 where items ID information is taken from process 2 in diagram 0. After that, process 8.3 calculate the total for the invoice and generates a report to Management and an invoice to Customer.

Table

Name Filed Name Key Length Required

Item

Item ID Primary Key Number Yes

Item Name Text[100] Yes

Item Description Text[100] NO

Item Category Foreign Key Text[50] Yes

Item Price Currency Yes

Table

Name Filed Name Key Length Required

Suppliers

Supplier ID Primary Key Number Yes

Supplier Name Text[100] Yes

Supplier City Text[50] Yes

Supplier Address Text[100] NO

Supplier Phone Text[15] Yes

Supplier Mobile Text[15] Yes

Employee Job Title Text[50] Yes

Supplier Email Text[100] Yes

Table

Name Filed Name Key Length Required

Customers

Customer ID Primary Key Number Yes

Customer Name Text[100] Yes

Customer City Text[15] Yes

Customer Address Text[15] NO

Customer Email Text[100] NO

Customer Phone Text[15] NO

Customer Mobile Text[15] NO

Table

Name Filed Name Key Length Required

Invoice

Invoice ID Primary Key Number Yes

Customer ID Foreign Key Number Yes

Invoice Date DATE Yes

Invoice Time TIME Yes

Discount Number NO

Table

Name Filed Name Key Length Required

Invoice

Details

Invoice ID Primary Key Number Yes

Item ID Primary Key Number Yes

Quantity Number Yes

Table

Name Filed Name Key Length Required

Purchase

Order

PO ID Primary Key Number Yes

Supplier ID Foreign Key Number Yes

PO Date DATE Yes

PO Time TIME Yes

Table

Name Filed Name Key Length Required

PO

Details

PO ID Primary Key Number Yes

Item ID Primary Key Number Yes

Quantity Number Yes

Table

Name Filed Name Key Length Required

Category Category Primary Key Text[50] Yes