Task 2: EER Model Business brief Kevin's Music is a small but rapidly growing business operating out of Burwood. The business began as a means for Kevin to book his band Into venues for live performances. Live music is not a very profitable occupation, so Kevin also started teaching music one-on-one to students living nearby. within a year of beginning his operation Kevin was approached by other musicians for help with getting bookings at live music venues. At the same time, some music venues were also asking him for help with getting bands to perform at their venues. While the musicians are mostly from Victoria, the venues he deals with include all Australian states and territories. Three years later, Kevin finds he has become an agent, a go-between for over 50 musicians or bands and over 100 venues, and is making a reasonable income from his fees. The music school side of the business has also expanded and he has 20 musicians who are doing the teaching, and the demand is still increasing Kevin's Music is now: • Acting on behalf of musicians to arrange venue bookings Acting on behalf of venues to book musicians Booking students with musicians for lessons • Booking musicians to teach students So far his business has been operating with notes scribbled on notebooks, messaging apps on his mobile phone and a series of disorganised spreadsheets. But these tools are becoming inefficient and increasingly inapt at managing the growing demands of the business. A transition to an information system is urgently needed. You are employed as a business analyst at Deakin Innovative Solutions Ltd, a business-consulting firm. You task is to investigate and develop an EER model for the newly proposed system, produce a business report addressing the business owner and make recommendations. Note: The design of any payments system is outside the scope of this project. one phone and a series of disorganised spreadsheets. But these tools are becoming inercient and Increasingly Inapt at managing the growing demands of the business. A transition to an information system is urgently needed. You are employed as a business analyst at Deakin Innovative Solutions Ltd, a business-consulting firm. You task is to investigate and develop an EER model for the newly proposed system, produce a business report addressing the business owner and make recommendations. Note: The design of any payments system is outside the scope of this project. EER Diagram EER diagram should contain the following components: Entities, named relationships, attributes (keys identified) and the cardinality for all relationships. A faster way of doing the EER diagram is to sketch it up on a blackboard/paper, take a digital photograph and paste it into your report. Alternatively, you may use any software tools at your disposal to sketch the EER diagram. If hand-drawn make sure your EER diagram is legible. Page 2 of 6 ENTITIES Entities are objects or concepts that represent important data. They are typically nouns, e.g. customer, supervisor, location, or promotion • Strong entities exist Independently from other entity types. They always possess one or more attributes that uniquely distinguish each occurrence of the entity. Weak entities depend on some other entity type. They don't possess unique attributes (also known as a primary key) and have no meaning in the diagram without depending on another entity. This other entity is known as the owner. Associative entities are entities that associate the instances of one or more entity types. They also contain attributes that are unique to the relationship between those entity instances. (we'll cover this in week 3) Associative Entity Weak Entity Enuty RELATIONSHIPS Relationships are meaningful associations between or among entities. They are usually verbs, e.g. assign, associate, or track. A relationship provides useful information that could not be discerned with just the entity types. Weak relationships, or identifying relationships, are connections that exist between a weak entity type and its owner. Relationship Weak Relationship ATTRIBUTES Attributes are characteristics of either an entity, a many-to-many relationship, or a one- to-one relationship. Multivalued attributes are those that are capable of taking on more than one value. Derived attributes are attributes whose value can be calculated from related attribute values. Attribute Multivalued Attribute Derived Attribute Crows-foot Notation Cardinality (limits of participation or sometimes called multiplicity) refer to the maximum number of times an instance in one entity can be associated with instances in the related entity, and the minimum number of times an instance in one entity can be associated with an instance in the related entity. Cardinality represented by the styling of a line and its endpoint, as denoted by the chosen notation style. One Many ingpdf maximum number of times an Instance in one entity can be associated with instances in the related entity, and the minimum number of times an Instance in one entity can be associated with an instance in the related entity. Cardinality represented by the styling of a line and its endpoint, as denoted by the chosen notation style. One I Many One (and only one) È Zero or one ¢ One or many Zero or many Ý Page 6 of 6