Case Study: Greenleaf Community Library
Greenleaf Community Library is a public library in Melbourne that aims to provide residents with access tobooks, digital resources, and educational programs. To enhance member services, the library plans to developa web-based application that tracks book borrowing, reading programs, and member activity.
You have been assigned to design the conceptual data model for the Greenleaf Library web application.The key system features are described below.
Greenleaf Library serves hundreds of members, helping them engage in reading and lifelong learning. Tobecome a library member, individuals must complete a registration process. The system stores memberdetails such as first name, last name, address, date of birth, phone number, and email. Each member isassigned a unique membership ID upon registration.
The library employs a number of staff including librarians and program coordinators. Each staff membersrecord includes name, gender, contact information, professional qualifications, role, and years ofexperience. Each staff member must hold a valid library certification that is uniquely assigned to them.
The library offers a variety of reading programs and events such as Childrens Storytime, Book Club,and Digital Literacy Workshop. Each program has a unique title and a defined objective. A staff memberis responsible for coordinating each program, while one staff member may run multiple programs.
Programs are scheduled across different time periods and may run multiple sessions. Each session has astart and end date, and members can join at any time.
Members may enroll in multiple programs simultaneously, and the system records the date they join eachprogram. Some members may not enroll in any programs.
Each program session may include a set of activities, such as reading challenges, discussion groups, andskill workshops. Each activity has a unique ID, name, description, and type
The system allows members to log in their progress in activities, including a unique log ID, date ofparticipation, start time, end time, and notes on their achievements.
Greenleaf Library also has a referral program that encourages members to invite friends or family to join.Referral relationships are tracked in the system for membership incentives.
Task 1: Entity Relationship Diagram (ERD)
Based on the above requirements, develop an ERD for the Greenleaf Library database.
NOTE: Students must provide any assumptions made which are necessary to support their design.
Steps:
i. Identify the main entities and assign meaningful names to all entities.
ii. Identify and name relationships between entities that you found in step (i).
iii. Assign attributes to each entity and associate attributes with each relationship.
iv. Identify primary keys for each entity.
v. Specify cardinality for each relationship identified in step (ii) using crows-foot notation.
vi. Identify foreign keys in the entities.
vii. Ensure the diagram is consistent, readable, and uses proper notation.
Task 2: Normalization
The following table records member participation in various library programs during August.Each program session has defined start and end dates and may run at multiple skill levels. Members can joinmultiple sessions and may rejoin the same program at different times.
(THE TABLE IS ATTACHED)
Consider Table 1 and answer all the questions given below.
i. Identify the primary key of the table.
ii. Determine the current normal form of the table and justify your answer.
iii. Identify all functional dependencies and classify them as full, partial, or transitive.
iv. Normalize the table to Third Normal Form (3NF), showing all steps clearly.
v. Identify primary and foreign keys for each resulting table.
PLEASE make sure the answer has:
– All entities are correctlyidentified with attributesaligned to the casedescription and allattributes required tostore many-to-manyrelationships areidentified and showncorrectly.
– All keys are correct,clearly defined,complete, andappropriate.
– All relationships,including the unary relationship, have beencorrectly identified andmeaningfully named. Noincorrect relationshipshave been identified,and all relationshipsalign with the givenrequirements.
– All cardinalities havebeen accuratelyidentified and areconsistent with therequirements outlined inthe case description
– All the foreign keys havebeen accuratelyidentified and alignedwith the establishedrelationships andcardinalities in themodel.
– All associative entitieshave been correctlyimplemented to resolvethe many-to-manyrelationship betweenthe two entities, inaccordance with thecase description, with allprimary keys, foreignkeys and attributesproperly defined.
– Fully correct diagram;professional layout;complete, clear, andeasy to interpret.
– Correct primary key andnormal formal with clear and completejustification.
– All functionaldependencies (FDs) arecorrectly identified andwritten using properconventions andnotation, including full,partial, and transitivedependencies whereapplicable.
– Primary key identifiedfor each table in theprocess of normalisationand tables are fullynormalised to 3NF;lossless anddependency-preservingwith a clear, professionalexplanation.
– Tables are fully correct,complete, clear, andprofessionallypresented.Al that PK/ FK have beencorrectly identified.