|
|
|
The exercises in the textbook don't quite fit our needs, so I will adapt them a little bit. Also, for fairness I will assign equivalent tasks to all groups. 1) Prepare a simple ERD for your team's new system. Figuring out the entities needed can be hard, so below are some possibilities to get you started. Odd Number Groups: Providers, Appointments, Patients, Insurance Firms, Insurance Policies, Treatments. (Where a "treatment" is defined as a particular service administered during an appointment, such as an injection, test or examination). Even Number Groups: Members, Gyms, Visits, Classes, Lessons (each lesson being one meeting of a specific class), Instructors. 2) For each of the entities in the ERD, specify a set of data dictionary entries along the lines discussed on page 168 and 169. For each of these entities, draw a table. Each row in this table will represent a single data element stored for the entity. The columns of the table are name, type, length, source, and range of acceptable values. Try to define an average of eight fields per entity. In real life they would have many more, but this is enough to see the idea. Note: this is not quite the format discussed in the textbook, but is basically a more compact way of representing the same information. Example entry for an entity defining "employee" in the SoftWare, Limited case study.
|
|
|