Create a UML diagram which would be suitable for a pillow fight database. The design can utilise inheritance and weak entities. Multiplicities must be listed for associations. Details: The pillow fights we hold come in two categories; planned sleep overs and spontaneous pillow beatings. Planned sleep over fights are most common and only involve other club members. Spontaneous pillow beatings are loads of fun and involve going out and feather bashing the public. The database needs to help us keep track of members so that we can quickly mount a last minute flash mob pillow assault on the public. We would need to record contact information so as to spread the word as quickly as possible. The planned pillow fights are a little different from public gatherings and often involve a sleepover at either a member's home address or some other location. Due to several complaints about member freeloading, we also want to keep a record of who brought food (and what they brought - yoyos and other cheap as biscuits are frowned upon in this club!). It may be handy to have some basic food rating system- perhaps a food field and a simple 1-5 food rating. If a member brings something ordinary to one of these events too often, then they may as well have brought nothing and their record gets marked as a freeloader. For sleepovers we record multiple pillow fight rounds and who participated. This also involves recording the winner of each round. Because these rounds are so important to a members status (and we want to be fair and everything), we also need to record info about the types of pillows used by each member during the round (feather, foam, synthetic, memory foam/rubber, bricks, sand etc). On completion of a members only fight, we need to record the 1stprize winner and runner up for that sleep over/pillow fight weekend. These fight rounds can be categorised as normal or "slow-mo" (as in slow motion).
Get Free Quote!
278 Experts Online