JIM Music System Proposal

This document presents a comprehensive analysis of a proposed music booking system for JIM Music. It details the system's requirements, outlining functionalities such as student registration, teacher profiles, music style management, booking processes, and performance scheduling. A conceptual database design is presented using Entity Relationship Diagrams (ERDs), illustrating data structures and relationships. The analysis also explores the benefits and limitations of implementing this system, considering factors like cost efficiency, employee training, and potential job displacement. Finally, recommendations are provided to guide JIM Music in adopting this new system effectively.

ENTERPRISE INFORMATION SYSTEM
MANAGER:
ADDRESS:
MY COMPANY NAME: Deakin Innovative Solutions Pty Ltd,
DATE

Table of Contents
Executive Summary...............................................................................................................................3
1.0 Introduction................................................................................................................................3
2.0 Company Profile.........................................................................................................................3
3.0 Entity Relational Diagram..........................................................................................................4
4.0 Justification................................................................................................................................5
5.0 Benefits and Limitations...................................................................................................................8
6.0 Recommendations............................................................................................................................8
References..............................................................................................................................................9

Executive Summary
The report is based on a company that have been doing manually using ledger books in recording all
the events in their calendar. The goal of this organisation is to come with an enterprise information
system that reduces all the works in the ledgers as booking of musicians, events and venues will be
easily recorded and easy to retrieve when need arise (Kahate, 2011). Considering Jim Music company
is growing rapidly there arose the need to migrate from paper work to a system that can interact and in
a faster way hence spending less effort, time and making more profit. As a business analyst I have
come up with data model in form of entity relational diagram and some of the recommendations that
need to be considered in putting up the proposed model considering all the specifications and
requirements of Jim Music Company.
1.0 Introduction
The project was commissioned by the manager Jim Music company to Deakin Innovative Solutions
Pty Ltd, where I work as a business analyst. The commissioning of this project was to advise them on
how they can migrate from paper based works to an interactive system that is effective and very
efficient.
For the project three individuals were assigned different tasks that is: A database administrator who
had to do the survey and come up with a model using ERD (Ramakrishnan, 2009), secondly is an
architecture who had to draw the whole scenario in way it can be understood and lastly the analyst
who had to give the whole analysis of all what is expected by Jim Music company.
This project covers entity relational diagram that need to be implemented showing its results through
use of sql statements that are a result of database manipulation. It also shows justifications of our
findings and the recommendations that need to be put in place with the benefits and the limitations
they accrue.
2.0 Company Profile
Jim’s Music is a small, but rapidly growing business operating out of Burwood. The business began
as a means for Jim to book his band into venues for live performances. Live music is not a very
profitable occupation, so Jim also started to teach music. Within a year of beginning his operation Jim
was approached by other musicians for help in getting bookings at live music venues. At the same
time, some music venues were also asking him for help in getting bands for them. While his musician
are mostly from Victoria, the venues he deals with all Australian states and territories. Three years

later, Jim finds he has become an agent, the 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.
Jim’s Music is now acting on behalf of musicians to arrange bookings, venues to book musicians also,
booking students with musicians for lessons and Booking musicians to teach students
3.0 Entity Relational Diagram
According to the scenario given in the exercise
the I came up with the above entity relational
diagram(ERD) (Vaswaw, 2015) .
Jim Music denoted as JM in the ERD acts as
the Employer who hires many agents to help in
booking musicians, registering students and
musicians, arranging venues and events in
different time zones (Karthik.P.R, 2012) .
At first an agent books a musician in a certain
event and the venue is arranged. The same
agent is the who books the students who needs
some teaching from the musicians.
The musician teaches students.
The following are some of the properties and
concepts of database that made the ERD
diagram above in details:

ENTITIES ATTRIBUTES
Agent AgentID, AgentName, AgentLocation
Venue VenueId, VenueName, VenueLocation
Event EventID, EventName, EventType, EventDate
Musician MusicID, MusicStyle, MusicCode, MusicianName
Students StudentID, StudentName,
Some of the relationships are such us Books, Arranges and “Teaches “which is a weak relationship
between the musician and the students.
One agent may book more than one musician, hence creating a one or many to many relationships.
One musician may teach more than one student hence one-to-many relationships
A venue can be booked by one or more than one agent for a certain event at different times, hence
many to many relationships.
Assumptions.
 Musicians who are not potential are not booked, i.e., Booking of Musicians is only done when
they request the agent from JIM MUSIC. (Therefore this make the minimum cardinality from
Musician to the agent to be one. This assumption means that we really can book a musician at
the same time we are recording the details of the Musician.
 It is possible that there are musicians booked but they don’t perform at any specific time.
Therefore, the minimum cardinality from Musician to performing is zero.
 Assumptions made are that attributes which are completed are used to differentiate the one
which are performed.
4.0 Justification
Teacher
TeacherID TeacherName DateJoined TeacherField
F407 mercy 25/12/2015 biology
G402 grace 17/11/2015 chemistry
F289 purity 17/12/2015 maths
F232 martha 04/12/2015 music
Solution
SELECT * FROM Teacher
WHERE date > ‘1/12/2015’ and ORDER BY DateJoined;

The above command is supposed to output the following results.
TeacherID TeacherName DateJoined TeacherField
F232 martha 04/12/2015 music
F289 purity 17/12/2015 maths
F407 mercy 25/12/2015 biology
5.0 Student
Fname LName StudentID Gender age
Justus Koskey 2015M412 M 21
Miriam hellen 2015F328 F 22
jane Rose 2015F734 F 19
humphrey miano 2015M213 F 23
Solution
SELECT *
FROM Student
WHERE Gender=’F’ and ORDER BY Age, LName;
The above command is supposed to output the following results.
Fname LName StudentID Gender age
jane Rose 2015F734 F 19
Miriam wesky 2015F328 F 22
6.0 Venue_Table
VenueId VenueName VenueLocation Postcode
00847 Wellington cafe Sydney V212
00541 Melbourne restaurant Sydney V199
00789 South Melbourne cafe kangaroo V247
00623 White oak Westeros V235
Solution
SELECT COUNT Postcode

FROM Venue;
The results displayed will be
Count = 4
7.0 Student
Fname LName StudentID Gender age
Justus Koskey 2015M412 M 21
Miriam hellen 2015F328 F 22
jane Rose 2015F734 F 19
humphrey miano 2015M213 F 23
Music
MusicID MusicCode MusicName MusicStyle
R40077 001 One love Reggae
RR4123 002 You ma heart Rock
B40745 003 Many reasons Blues
S34566 004 Girlfriend Soul
Teacher
TeacherID TeacherName DateJoined TeacherField
F407 mercy 25/12/2015 biology
G402 grace 17/11/2015 chemistry
F289 purity 17/12/2015 maths
F232 martha 04/12/2015 music
Solution
SELECT S. StudentID, M. MusicStyle, T. TeacherID
FROM Student.Student AS S
INNER JOIN
Student.Music AS SM
ON S.StudentID= SM.MusicID
INNER JOIN

Student.Teacher AS ST
ON SM.MusicID = ST.TeacherID
Where Students>1 and date between 2015/01/12 and 2015/01/31
The above command is supposed to output the following results.
StudentID MusicStyle TeacherID Date
2015M412 Reggae G402 17/11/2015
2015F328 Rock F232 04/12/2015
2015F734 Blues F289 17/12/2015
2015M213 Soul F407 25/12/2015
The above solutions show how the stated sql commands will display results in the system in queried.
This is enough justification showing clearly the need for the system. It justifies that the requirements
of JIM Music are meant and according to their specifications.
5.0 Benefits and Limitations
Migrating from an inefficient system to a new effective system comes with new merits as well as
demerits of the new system. Some of the new benefits accrued in are such us. There will be less paper
work as most data will now be stored on a database (NJ, ©2014) that the new Enterprise information
management system will apply. Second is that less effort will be needed. This will save cost of
employing people working in the organization as only few employees who are experts with the system
will be needed. The business will expand globally as now there will be more interaction hence
increasing live performances as they will now be digital like other organisations. Another benefit to be
enjoyed is less competition for companies who are still manual paper work in bookings scenarios.
A new system comes with its own limitations. One of the limitation is the cost of implementing it to
fully functional is very high. Secondly is the training cost of the current employees as they have to be
trained on how the system works. Another limitation is that the system will lead to some employees
lose their job as the job they used to do will be now be done by the system deployed.
6.0 Recommendations
As a business analyst contracted by JIM MUSIC company I would recommend them to implement the
system as it will bring in new methods that will attract many musicians to have bookings with them as
it will become reliable and available everywhere at any time.

Another recommendation is the company as it migrates from the old system to new system to consider
the welfare of its employees.
References
ERDPLUS. (2017, may 11). ERDPLUS. Retrieved from ENTITY RELATIONSHIP DIAGRAMS
UNDERSTANDING: https://erdplus.com/#/
Kahate. (2011). Introduction to Database Management.
Karthik.P.R. (2012). The High performance mysql by Percona is good.
NJ, U. ( ©2014). Database Concepts 7th Prentice Hall Press . Upper Saddle River,.
Ramakrishnan, R. (2009). Database System Concepts.
SMART DRAW. (2017, aug 20). Retrieved from Entity relationship diagram:
https://www.smartdraw.com/entity-relationship-diagram/
Vaswaw, V. (2015). learning SQL statements .