Creating an ERD and Data Dictionary for the presented Use Case.

I lea Pace_calo of ttame weine Doint of Calee Suetem General Requirements You will create an Entity-Relationship Diagram based on a provided use case. The Use Case You will use the use case we created in class for checking out a customer at one of the little "shops" on campus. The use case has been slightly expanded and clarified, but is essentially the one you were asked to submit as an in-class exercise. A copy of the use case is attached to this assignment. The Entity-Relationship Diagram (ERD) Create an entity-relationship diagram (ERD) based on the provided use case. I recommend creating at least a rough draft of a context diagram for the (theoretical) Point of Sale system of which the provided use case is a part. I would further recommend creating a rough draft of (at minimum) a Level 0 Data Flow Diagram (DFD) for the use case. These analysis work products will help you ensure that your ERD is complete and "makes sense" within the context of the system (Point of Sale) under consideration. Notation Style You are welcome to use any notation style you prefer. The "crow's feet" style described in the text, a style closer to the one used within Access, or some other style of your choice. Regardless of notation style, your ERD must meet the following requirements: 1. Directionality of the relationship must be clear. That is, it should be clear which entity is the "parent" in a relationship and which is the "child". 2. Cardinality of the relationship must be clearly indicated. 3. Modality of the relationship must be annotated in some (clear) fashion. Are both entities in a relationship required to participate? 4. Any dependent entity(ies) must be clearly indicated. Whether or not you have one or more dependent entities will be determined by your design. You may hand-draw your ERD if you wish - please keep in mind that it will be submitted electronically through Blackboard (no other submission channel is allowed). You may use Excel or PowerPoint, if you wish. You are welcome to use Access (it should be available in the computers in the Student Computing Center and the JPL Commons), although doing so may require more work on your part. You are also welcome to use a free charting/diagramming site such as Lucidchart. Most of these free tools will include at least one notation style specifically intended for ERD work. Data Dictionary Please also include metadata in your submission. The type of metadata I am expected includes: - Name of the field or attribute - A short description of the field/attribute - Expected data type of field/attribute (in general terms, NOT language-specific) - Notation designating which field/attribute is a primary key (if used) - Notation designating which field/attribute serves as a foreign key (if used) You are welcome to use a second document for your data dictionary or to include it as part of your ERD document. I recommend Excel as a tool to collect and organize your metadata. You may submit an Excel workbook as your data dictionary submission