7) Data Design: In a Context Diagram, an external entity is an external person or anything that interacts with an inform

Post by **answerhappygod** » Sun May 15, 2022 12:23 pm

: 7 Data Design In A Context Diagram An External Entity Is An External Person Or Anything That Interacts With An Inform 1 (32.18 KiB) Viewed 66 times

: 7 Data Design In A Context Diagram An External Entity Is An External Person Or Anything That Interacts With An Inform 2 (63.62 KiB) Viewed 66 times

: 7 Data Design In A Context Diagram An External Entity Is An External Person Or Anything That Interacts With An Inform 3 (29.11 KiB) Viewed 66 times

: 7 Data Design In A Context Diagram An External Entity Is An External Person Or Anything That Interacts With An Inform 4 (29.11 KiB) Viewed 66 times

7) Data Design: In a Context Diagram, an external entity is an external person or anything that interacts with an information system. In data design, however, the definition is slightly different. In data design, an "entity' (data entity) is defined as "a person, a place, a thing, or an event for which data is collected and maintained." (Tilley, 2020, p.280). Please design and create the following data design diagrams (see examples on the following page): a) Entity-Relationship Diagram (ERD) of the data entities (at least 8) in your proposed system. Please use Cardinality notation in your diagram. For an example, see Figure 9-16 & Figure 9-19 in Sections 9.5.2 & 9.5.3 of the textbook.

1. Drivers: (a) Attributes: driver ID, name, bank account #, active (Y/N), current location (GPS coordinates), date created; (b) Methods (processes): Driver Maintenance (create/modify/inquire/delete). 2. Customers: (a) Attributes: customer ID name, address (street name & number, city, state, zip code), visa card #, date created; (b) Methods (processes): Customer Maintenance (create/modify/inquire/delete). 3. Maps: (a) Attributes: street name, street number, city, state, zip code, GPS coordinates; (b) Methods (processes): Map Maintenance (create/modify/inquire/delete). 4. Fare Rates: (a) Attributes: time of day, fare$/mile; (b) Methods (processes): Fare Rate Maintenance (create/modify/inquire/delete). 5. Call Estimates: (a) Attributes: customer ID, date, time, from location (GPS coordinates), to location (GPS coordinates), distance, fare$/mile, estimated fare; (b) Methods (processes): Call Estimate Entry (create/delete) 6. Ride Transactions: (a) Attributes: driver ID, customer ID, date, time, from location (GPS coordinates), to location (GPS coordinates), distance, fare$/mile; actual fare; (b) Methods (processes): Ride Transaction Entry (cred/te/modify/inquire/delete). 7. Customer History: (a) Attributes: customer ID, last ride date, last ride time, last ride from location (GPS coordinates), last ride—to location (GPS coordinates), last ride amounts, last ride driver ID, total # of rides taken, total $ paid; (b) Methods (processes): Update Customer History (create/inquire/delete). 8. Driver History: (a) Attributes: driver ID, last ride date, last ride time, last ride from location (GPS coordinates), last ride to location (GPS coordinates), last ride amounts, last ride customer ID, total of rides given, total $ received; (b) Methods (processes): Update Driver History (create/inquire/delete).

Example #1 of Entity-Relationship Diagram (ERD) SALES REP SERVES M CUSTOMER PLACES ORDER WARDOUSE ORDER LINE LISTS STORES associative entity PRODUCT