COMP1430 Systems Design and Development Exam
Question 1
A). From the Above scenario the Entities are written below,
The entities are
- Property
- Utility bills
- Property types
- Owner
- Tenants
All the above written entities have different types of attributes. The attributes are,
- Property bills- For the following entities the property bills have some attributes which are property name, property ID, property details and also the property name.
- Utility Bills- For the following entities there are basically some attributes which are Electricity, gas, water and also the heating.
- Property types- The following Entities attributes are the flats,house,single rooms and also there studio apartments (Gimadiev et al.., 2021).
- Owner- the owner has the details of Owner ID, name, Date of birth,bank ID,phone number.
- Tenants- the tenants have some following attributes. Which are, name, id, phone number.
- Customer- this entity has some attributes which are ID date of birth and also bank ID and name.
b) ERD Diagram
Figure 1: ERD diagram (Source: Self created on Draw.IO)
C) The phrase “referential integrity” relates to a size of information that says that most of its references are valid. Any row in a data structure that’s also declared a foreign key could only hold missing value or data from the parent seat’s main key or even a candidacy value for referential to hold in a database system. from the above case scenario the referral integrity is the property ID which can also be called as the foreign key.
D)To guarantee sure information in a specific column is consistent, the primary key is used. A foreign key is a field or similar arrangement in a table in a database that is obtained from two columns to be joined. It refers to a database field. It is also the primary key of this other table. From the above scenario the one primary key is taken in the customer table the customer ID is the primary key. Primary key is one kind of key which identifies one row particularly with unique values. And the foreign key can be the property ID. The two tables can be connected easily with the help of these two keys.
Question 2:
- Relational database Weakness
- Mismatching the impedance between the relational world and the object oriented.
- The relational database model isn’t appropriate for all domains.
- Due to a lack of horizontal scalability, there is a lack of dispersed unavailability.
- Execution hit because of joins, ACID exchanges and severe consistency requirements (particularly in appropriated conditions)
Two Bank Account articles and two Address objects are referred to by Customer Karl. Each class (Customers, Addresses, and Bank Accounts) has three tables in the composition, each populated with the proper information. Also, the records for addresses and ledgers incorporate an unfamiliar key that focuses on the Customer table thing (Ataei et al.2021). The course of causality in the social information model is the reverse of the first one, which is remarkable. To that end I allude to the connection model as “unnatural” for object-situated developers. Besides, when delegate tables are required, the information circulation across various tables turns out to be significantly more difficult.
b. Relational database strength
To sum up the advantages of utilizing a social data set past some other type of data set, a social data set guides in keeping information uprightness, information exactness, decreasing repetitive data to an insignificant or nothing, information versatility, information adaptability, and simplifying security procedures to apply.
Flat files weakness
b) the methodology used to model the database is query optimization Method. Another of the best ways to optimize speed inside a system is to construct it right the first time! Making design and architecture rational decisions and industry standards can enable you lower tech debt as well as the number of additional repairs. There are many methods to expedite the process by modifying searches, indices, and server settings, there are limits to whatever we can do in a fee and reasonable fashion. The data structure and software architecture set such limitations. This may seem that emphasizing excellent upfront might cost more than just the capability to roll up activity in response, but the cost of hasty or inadequate choices will be more in the lengthy period (Wang et al.2018).
c) Query optimization Techniques
- First, explain the business requirements.
2. Rather than using SELECT *, use Designate fields.
3. Avoid using With DISTINCT.
4. Use INNER JOIN other than Where when create joins.
5. Create filters with And where so rather than Had.
d.
Reference List
Journals
Ataei, P.S., 2021. Theory and Implementation of a Variational Database Management System.
Gimadiev, T., Nugmanov, R., Batyrshin, D., Madzhidov, T., Maeda, S., Sidorov, P. and Varnek, A., 2021. Combined graph/relational database management system for calculated chemical reaction pathway data. Journal of Chemical Information and Modeling, 61(2), pp.554-559.
Gimadiev, T., Nugmanov, R., Batyrshin, D., Madzhidov, T., Maeda, S., Sidorov, P. and Varnek, A., 2021. Combined graph/relational database management system for calculated chemical reaction pathway data. Journal of Chemical Information and Modeling, 61(2), pp.554-559.
Jiang, B., Zhao, Y., Yi, H., Huo, Y., Wu, H., Ren, J., Ge, J., Zhao, J. and Wang, F., 2020. PIDS: A user-friendly plant DNA fingerprint Database management system. Genes, 11(4), p.373.]
Puttinaovarat, S. and Horkaew, P., 2021. A geospatial database management system for the collection of medicinal plants. Geospatial Health, 16(2).]
Puttinaovarat, S. and Horkaew, P., 2021. A geospatial database management system for the collection of medicinal plants. Geospatial Health, 16(2).
Setyawati, E., Wijoyo, H. and Soeharmoko, N., 2020. Relational Database Management System (RDBMS).
Wan, C., Li, W., Ding, W., Zhang, Z., Lu, Q., Qian, L., Xu, J., Lu, J., Cao, R., Ye, B. and Lu, S., 2021. Multi-task sequence learning for performance prediction and KPI mining in database management system. Information Sciences, 568, pp.1-12.
Wang, Y., Liu, J., He, X. and Wang, B., 2018. Design and realization of rock salt gas storage database management system based on SQL Server. Petroleum, 4(4), pp.466-472.
Widianto, S.R., Sudiro, S.Y., Suwandi, I. and Leiliawati, L., 2020. Database Management System on Raw Material Transaction System Case Study: Sabana Fried Chicken. Jurnal Mantik, 4(3), pp.1722-1727.
Know more about UniqueSubmission’s other writing services:
