Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

marksl Describe attribute conflict in view integration. How is l0.5 marks List a

ID: 3581012 • Letter: M

Question

marksl Describe attribute conflict in view integration. How is l0.5 marks List and describe three logical level implementation compromises marks] Adentify the resources and agents associatod with each of the folowing events in the conversion Materials Requisition (Commitment Decrement Materials lssuance (Economic Decrement) Labor Operation (Economic Decrement Machine Operation (Economic Decrement) Production Order Commitment Mo increment) Production Run (Economic increment 4.10.5 mark] Explain the most key points of integration between the acquisitonpaymentgoe and the conversion cycle business process level models 5. (05 marksl Consider the database tables in Exhibit 11.15 Describe the necessary procedures to construct one r more queries to determine what quantity (and unit of measure) of eoch ingredient Lucy requisitioned. 6. [2 marksl Applied question] uandrax Computer sisa store that buys computer components for low prices assembles the components into computers, is assigned a unique identicationnumber, and computers and then sells the computers athigh prices. Each computer that have common configurations are categorized into types leg. is alaptop that is easily networked and is for businesses, Element intended for home and smal businesses Categories desktop that is entered into the database before any computers in the categories are actually assembled. The computer components purchased from wholesalers. One of Quandraxs purchasing agents submits an order to the wholesaler that has listed a given component for sale. If the order is accepted, one of Quandra's inventory cerks receives the items. Multiple orders accepted by the same supplier may be consolidated into one purchase. Orders are accepted in their entirety or not at all. Nearly allof Quandraa's orders are accepted. Sometimes the incorrect components are delivered to Quandrax and Quandrax has to return them to the appropriate supplier. Sometimes Quandrax Nturns component o suppliers for other reasons, such as the result of a change in planned production of a certain category of computers. Only about 10 percent of Quandra's purchased components are returned to supplers and any return would result from only one purchase. When payment is due for a purchase, one of Quandrax's cashiers issues one check for payment in full for the items. on that purchase. Sometimes multiple purchases have been made from the same supplier within a short time, Quandra pays for those purchases ith just one check. One of Quandra'smanagers isrequired to not only authoriar purchase orders greater than $5.000 but also to siem all checks including checks written forexpenditures other than purchases of computer componentsl Quandrax needs to keep track of the managers participation in these events as wel as the participation of other employees in these events. physically implementing the conceptual modelinto the database tables. Quandrax wants to combine all employee types into just one table.This means Quandra would keep he separate employee entities on the ER diagram,but make just one employee table torepresental of the employee entities, then post keys or make relationship tables as necessary to implement al to the relevant events.

Explanation / Answer

If same attribute is used to identify or describes the same entity in various views then an attribute conflicts occurs. This includes all attributes needed for all transaction cycles as attributes for the entity in the integrated model.

Attribute conflict is resolved by performing a set union of the attributes needed for different cycles.

2. List and describe three conceptual level implementation compromises

Conceptual Level Compromises:

a. Materialization of tasks as entities. Done when tasks are deemed sufficiently important to track separately from the events they comprise; not recommended, as it increases model complexity and results in a database design that must be changed if task workflow changes.

E.g. Request for Quote, Receive Bids

Use “what is needed to plan, control, execute, and evaluate” criteria to determine when to separately model “steps needed to achieve an event”

If attributes are needed for decision-making purposes and they can’t be stored within the existing event entities, often the tasks will need to be materialized as entities.

             b. Exclusion of an entity (usually a resource) because of inadequate measurement tools or because no decision need exists for that data.

          E.g. labor and use of fixed assets, supplies, and services in non-conversion processes

    c. Consolidation of conceptually congruent entities. If two entities always occur in combination with each other, so that they are virtually indistinguishable, they may be combined into a single entity.

E.g. events that always happen simultaneously

3.

Event

Resources

Agents

Materials requisition

Materials inventory type

Production supervisor,
Warehouse personnel

Materials issuance

Materials inventory type

Production supervisor,
Warehouse personnel

Labor operation

Labor type

Production supervisor,
Production employee

Machine operation

Machinery or equipment

Production supervisor,
Production employee

Production order

Finished goods inventory

Production supervisor,
Production employee

Production run

Finished goods inventory

Production supervisor,
Production employee

4. The most likely points of integration between acquisition/payment and conversion are the raw materials and machinery and equipment resources. Those are the resources that are made available by the acquisition/payment process and are used up in the conversion process.

6.Convert the conceptual model into a logical set of relational database tables

cash:

Acct#

Ca-Loc

AcctBal

Cash Disbursement

CD#

Date

CdAmt

Csr-EmpID*

Mgr-EmpID*

Cash-Acct#*

CashReceipt

CR-ID

Cr-Date

Cr-amt

Cr-Chk#

Cust-ID*

EmpID*

Cash-Acct#*

Component Inventory

Compo-ID

Description

Std Cost

Computer category

Cat-ID

Cat-desc

List-price

Customer

Cust-ID

Cust-name

Cust-ship

Employee

EmpID

Emp-name

Emp-ty

Proposition

SC-ID

Cat-ID

Prop-sp

Reservation

SO-ID

Cat-ID

Order-sp

Reservation2

PO-ID

Compo-ID

Ord-unit-cost

Qty-ord

Fulfillment1

SC-ID

SO-ID

Fulfillment2

SO-ID

Ship-ID

Assignment

Emp-ID

Cust-ID

Stockflow3

RR#

Compo-ID

Item-unit-cost

Qty-rec

stockflow5

PR-ID

Compo-ID

Participate10

PO-ID

Mgr-ID

Participate14

CD#

Sup-ID

Finished Computer

CompuID

Assemb-date

Act-sp

Cat-ID*

Ship-ID*

Purchase

RR#

Date

IC-EmpID*

SupID*

CD#*

Purchase Order

PO-ID

Date

PA-EmpID*

Sup-ID*

RR#*

Purchase Return

PR-ID

Date

IC-Emp#*

RR#*

SupID*

Sale/Shipment

ShipID

Sale-amt

Sale-date

EmpID*

CustID*

CR-ID*

Sales Call

SC-ID

SC-date

EmpID*

Cust-ID*

Sale Order

SO-ID

SO-date

EmpID*

CustID*

wholesaler

Sup-ID

Name

Type

Event

Resources

Agents

Materials requisition

Materials inventory type

Production supervisor,
Warehouse personnel

Materials issuance

Materials inventory type

Production supervisor,
Warehouse personnel

Labor operation

Labor type

Production supervisor,
Production employee

Machine operation

Machinery or equipment

Production supervisor,
Production employee

Production order

Finished goods inventory

Production supervisor,
Production employee

Production run

Finished goods inventory

Production supervisor,
Production employee