Database Design
Musical artist managers sometimes find it hard to organize shows for their artists. Having taken a look at some of these issues there is a proposal to use certain applications developed by companies to help manage artists in a much easier way. here I propose the use of the back on-stage database.
This helps artist managers in various ways. being an application, the information that will be required is for the manager to sign up with the app then fill in the detail about the company and the artist. It helps in booking gigs for the clients, has inquiry follow-ups this includes keeping invoices with inline payments (Zhou, 2019). This is meant for the managers and their staff members who are taking part in preparing events for the artists. the back on stage needs information in the artist this includes the name and the type of music they produce, the targeted crowd to help during finding gigs for the artists, amount paid in the events, and number of the artist
The system should be able to capture the marketing of the artist should be sure to reach the targeted audience for the artist. should be reliable where the event should certain returns in terms of cash flow and music sales and promotions (Zhou, 2019). the database should cover artist performance schedules, venues, communication between the manager artists and the audience. payouts this is in terms of promotions, such as t-shirts caps, and hoods it also builds hype during artist performance. the database will store music released, schedule performance and tours. the best database should store information conceding the manager’s duties and the client’s needs (Zhou, 2019). The database should help the manager plan and reduce the expenditure in paying event managers and people to help put up or book events. Computer Science homework help
References
Zhou, N. (2019). Database design of regional music characteristic culture resources based on improved neural network in data mining. Personal and Ubiquitous Computing, 24(1), 103–114. https://doi.org/10.1007/s00779-019-01335-9
develop an Entity Relationship Diagram (ERD) for the database that models your chosen domain. This assignment consists of three steps that should be completed by Sunday of Week 2 at 11:59 p.m., CT:
- Identify entities;
- find relationships; and
- Draw the ERD blueprint.
ORDER A PLAGIARISM FREE PAPER NOW
Step 1: Identify Entities
Identify the entities. These are typically the nouns and noun-phrases in the descriptive data produced in your analysis. Do not include entities that are irrelevant to your domain.
For example, in a college database project, the entity candidates are departments, chair, professor, course, and course section. Since there is only one instance of the university, we exclude it from our consideration for now.
Step 2: Find Relationships
Discover the semantic relationships between entities. In English, the verbs connect the nouns. Not all relationships are this blatant; you may have to discover some on your own. The easiest way to see all the possible relationships is to build a table with the entities across the columns, and down the rows. Then, fill in cells to indicate where relationships exist between the entities. Computer Science homework help
| Departments | Chair | Professor | |
| Departments | |||
| Chair |
Step 3: Draw the ERD Blueprint
Draw the entities and relationships you have discovered. View the example of a college database project ERD blueprint. To create your ERD, the domain (or subset of a domain) that you chose for your project should include the following characteristics:
- Size. An appropriately sized domain results in a database with about a dozen entries (more or less).
- Relationship. The entities comprising your domain should be interrelated.
- Functionality. The scope of the diagram shows the operations or functions that the database project addresses. It also identifies the functions that fall outside of the application.
- Description. Define the data requirement of your entities. For example: Computer Science homework help
- Student Entity: Members of the public who register and pay for courses are considered students. The data stored on each student includes student number, name, address, email address, previous classes, and experience. Also stored is the date for registration and the classes they are registered in. The student number is unique for each student.
- Course Entity: The school offers a variety of Online design courses through its website (these are considered course, not the on-location seminars). The data stored on each course includes the course number, the name of the course, the course description, and prerequisites (if any). The course number is unique, etc.
