The Traditional 3-Way Matching Process

The purchasing department of Company X completes a paper purchase order and sends it to Supplier A via fax, with a copy going to the accounts payable department of X. Supplier A ships the goods and they arrive at company X's receiving dock. A clerk at X's receiving dock completes a paper receiving document describing the goods and sends it to X's accounts payable department. Supplier A meanwhile sends a paper invoice to X's accounts payable department. A clerk in X's accounts payable department would match three documents: the original purchase order, the receiving document, and the invoice. If all three documents match, an accounts payable clerk issues a paper check to supplier A. If they don't match, an accounts payable clerk calls supplier A by phone to reconcile any shipment errors.

PART I: Function Modeling (5 points)

5 pts 3pts 0pts

Develop afunctional decomposition modelbased on the 3-Way Matching Process described above. Note that a business function concerns what is being done and not concerned about the who, how, when and where aspects of the activities. Decompose starting with the topline function (1stlevel) and endingup tothe 3rdlevel.

Instructions:

Follow the convention of Function Modeling in Chan (2013).

Read the case provided and identify business functions. Remember that a function is what is being

done and not how it is done. For example, the requirement of "Receive customer order by Sales via

Fax" can be stated as a function "Receive customer order".

List all the functions in the case.

Group them at the proper levels.

At every step checkaccuracyandcompleteness. For example, in the decomposition of the function

1 into 1.1, 1.2, 1.3, ask the questions:

Are 1.1, 1.2, 1.3 accurate statements of subfunctions of 1?

Are they complete, i.e., if one completes 1.1, 1.2, 1.3, is function 1 satisfied?

Decompose starting with the topline function (1stlevel) and endingup tothe 3rdlevel.

Diagram is accurate and complete with explanatory text

Diagram captures most part, but missing either in accuracy or completeness

Diagram does not match the functional requirements

PART II: Data Modeling (5 points)

5 pts 3pts 0pts

Develop anEntity-Relationship modelto satisfy all the following requirements described below. Note that you must combine the individual ER models below intoonemodel.

The purchasing department of a company issues purchase orders (PO) to its suppliers.

A purchasing department may buy from multiple suppliers; a supplier may supply products for

multiple purchasing departments.

Each purchasing department may issue multiple POs.

Each PO comes from one purchasing department and is for one supplier.

A supplier may process POs from different purchasing departments.

Each PO may reference multiple products; a product may be referenced in multiple POs (through Line Items)

Each PO has one or more line-items (PO LINE-ITEM).

Each line item belongs to one PO.

Each line item is for one product from a supplier.

A supplier may supply one or more products, a product is supplied by one supplier.

The status of a PO is tracked at the line item level.

A line item can have multiple statuses. Example of statuses are "line item shipped", "line item received", "line item rejected", "line item paid", etc.

A status can be applicable to multiple line items

Instructions

Follow the convention of Entity Relationship Modeling in Chan (2013).

Read the requirements provided and identify data entities. Remember, an entity is a thing of

significance for which information needs to be managed. A good place to start is to identify nouns

and determine if they are entities or not.

List all entities as specified in the requirements.

For each of the requirement described, construct the corresponding ER model.

Develop a consolidated model by combining the models developed in Step 4.

At every step check accuracy and completeness.

Are entities and relationships defined represent the requirement accurately?

Are they complete, i.e., are there missing data entities, are there missing relationships?

Submit your work in a MS Word document. Use the formats introduced in Chan (2013) for all your models.

Submit your work in MS Word. If you are using other diagrammatic tools, you may paste diagrams in the Word file. Use the modeling conventions described in the Chan references.

Work that is submitted for another class cannot be used for this project.

Diagram represents the stated requirements; correct entities and relationships

Diagram captures most but no all requirements; missing or incorrect entities and relationships

Diagram does not match the stated requirements

References:

Chan, J.O. (2021) - Data Modeling Supplementary Notes Chan, J.O. (2013): Process Modeling, Function Modeling, Data Modeling & Model Cross Check Chan, J.O. (2004): Techniques in Enterprise Modeling Paul et al. 3rdEd, Chapters 11,12 BABOK Chapter 9