submit completed EER (or UML) and DFD diagrams for Kim’s Flowers?
Kim Burke is the owner and operator of a small flower shop called Kim's Flowers (KF). She has decided to develop a database system to track her purchases, floral inventory, cash payments, and so forth. However, she does not have the time or expertise to handle the development process. Therefore, she has hired you to design and implement the system for her. She describes the requirements of her system as follows:
Whenever flowers are needed, a purchasing agent enters a purchase order directly into the computer system. To accommodate all of her floral needs on a given occasion, the purchasing agent may have to prepare multiple purchase orders because KF orders flowers from many different vendors. The purchasing agent may order several types of flowers from a single vendor on one order. Kim approves and prints all purchase orders and sends them to the vendors. There is a time lag of at least one day between the issuance of a purchase order for flowers and receipt of flowers from a vendor. A floral designer records the receipt of flowers on a special screen in her accounting system. At the end of each month, an accounts payable clerk creates checks to pay for all amounts charged through the end of the month. Once the checks are created, Kim authorizes the checks, prints them, and mails them to vendors. Kim also uses special screens in the computer system to perform maintenance for inventory items (addition, modification and deletion of items from the file), and to record disposal of old or damaged flowers.
Attributes to Consider (these attributes do not have to appear on your EER (or UML) diagram. However, they should assist in data model formulation, and they will be used when you construct your relational tables in part two of the project):
vendorNumber quantityOnHand shipper itemNumber
disposalNumber bank PONumber condition
address unitPrice description dateStarted
balance receiptNumber name qtyDisposed
date accountNumber employeeNumber accountType
quantity reasonForDisposal paymentNumber amount
• Based upon all the above information, prepare an EER (or UML) diagram describing Kim's database. You may draw a table (file or class) more than once for an individual entity, if desired, to make your drawing more legible. The system you conceptualize should be planned to always store information about the employee associated with transactions, whether that employee enters data, performs a task (such as receiving flowers or approving a transaction). Hints: (1) Each item on a floral receipt may be from a different purchase order. (2) Different items on a single purchase order may be received at different times using different receipts. (3) Each check may pay for several receipts. However, a single receipt will always be paid for using the same check. (4) Multiple floral items may be disposed of using a single disposal form. (5) Unless logic dictates otherwise, you may assume that agents can be instantiated in the database without having yet participated in any events.
• Prepare the context diagram and the level 0 DFD.
• Once again, your responses (description of steps, EER or UML diagram, context diagram, and level 0 DFD) must be generated using appropriate software. In addition, submit your solution files via the appropriate drop box provided on Blackboard before the beginning of class on March 22nd , 2012, and submit a hardcopy version of your solutions to the instructor at the beginning of class on 3/22/12.
Any brief idea will be helpful.
- Anonymous8 years agoFavorite Answer
Sure! *Submits completed EER and DFD diagrams for