Answer

Building a Database for your Favorite Local Land

The formation of different designs typically characterizes the process of data management in an organization.  On the other hand, Database design describes the organization of information in a model with specifications on stored data together with elements considerations according to organizational activities. In this brief, building a database for a local favorite band will be provided. Consequently, the paper will outline different database design functions that support these functions and recommend system architecture that identifies software and hardware parts together with their interaction. Security concerns will also be analyzed, followed by the provision of three ideal measurable criteria to determine the completed software quality.

Explanation of Functions

There are four functions for considerations, from the concerns of the bandleader’s love-hate relationship to the database system. First, data dictionary management offers data component structure and connection to the target listeners of music. The second function is data storage management that provides definitions, validations, and rules that will be applied according to customer requests collected from the field. The third function for consideration is data transmission and presentation. The presentation function will offer variation between physical and logical formats to provide a presentation platform under this function.

Logical Data Design

The data model offers accuracy in the data presented and the definition of rational tables. The logical data design is presented by Entity-Relationship (E-R) model and Unified Modeling Language (UML) (Kavanagh et al., 2020). The E-R model offers a description of a database using a diagrammatic presentation. Figure 1 below illustrates a simple ER diagram that can be used by the band.

Diagram 1.1

Unified modeling language defines customized ways to visualize database system. Under this system, the primary key will be offered to present how language can be applied in the model. The following table shows a sample construction of UML primary keys access.

Table 1.1

Recommended Architecture

Database designs can be constructed based on centralization, decentralization, and hierarchical considerations. Under this system’s function and band leader concerns, the most recommended architecture for this system is the Three Level ANSI-SPARC Architecture. Under this system, the band will be presented to external, conceptual, and internal levels that allow collecting public views and organizing the collected information at internal organizational functions. The following diagram illustrates the architectural design. 

Diagram 1.2

Security Concerns

Although database design has the advantages of enhancing the band activities during the performance, there are underlying risks that need to be considered. The management of risks in a database will entail considerations to security management functions. Security can be provided by defining authorized system users who are virtually issued with user names and passwords through biometric authentication of fingerprints or eye scans (Nuccetelli et al., 2020). Since the security function is expensive, there will be a need to reduce the number of individuals authorized to access the system. Additional considerations for security management in the database will be to prepare for data restrains in the system during its operations.

Measurable Criteria

Having constructed a database from the above recommendation, measurable criteria for the database’s efficiency will evaluate three aspects. The first aspect is on reliability to analyze system stability to meet user needs. This will be tested by meeting user preferences and the accessibility of essential files when there is a need. The second measurement is on system performance. The performance brings into consideration the loading, stress, and soaking tests. Lastly, the security aspect will evaluate available system vulnerability, resolution time, and the possibility to deploy security aspects. In conclusion, the above description outlines how the band can successfully use the database while addressing the band leader’s concerns.