Database Design and Development

Question: Discuss about the Database Design and Development. Answer: Entity Relationship Diagram of CQ-Council information system Figure 1: Entity relations Diagram (Source: Created by author) Business rules and assumption Presently in this circumstance, the suburban zone is under the CQ-Council, they need to partition every zone according to the solicitation of their applicants. They need to develop an information system to store the record of each activity of this suburban area. Here the developer assumed the following business rules to develop their information system. They additionally have some review officers these officers examine the issues in this rural zone and resolve their issues. The CQ-Council need to store these subtle elements on this information system. These substances contain some more critical business rules, where they can confirm each issue by going to the candidate's place. However, when their complaints are valid, then CQ-Council will take it as a valid application, which must follow the council policy. Any application, which does not follow the council policy mark as an unsuccessful application. Here the candidates send their application just for the residential and commercial zone. This information system likewise keeps tracking the data that is related to the lots if anything else it will consequently reject such applications. Here if anybody needs to separate their part into two plots, they have sent the application to the committee. This board additionally give four kinds of administrations, for example, a subdivision of a considerable plot or merge of plots, tree evaluation, development of new building or decimation of an existing building and augmentation of any building. 3NF Relations The relations showing in the above figure (1) are normalized in 3NF. Here these relations are showing underneath in required format. Lotowner (lotownercode, lwname, lwcontactno, lwaccountinfo, lwotherdetails) Buildercategory (bccode, bcname, bctype) Inspectorofficer (serialcode, name, address, contact) Plotcollectionaggreement (pcacode, pcaname, pcaadditionalinfo) Clearancechecking (ccid, ecid, iocode, checkingrequireservice, statement, assesmentid) Foreign key (assesmentid) references assesment (assesmentid) Entryclerance (ecid, ecname, ecarea, eclanddesc, ecstatus) Builderinformation (bcode, buildername, bccode, builderplotcode, workstatuscode) Foreign key (bccode) references buildercategory (bccode) Foreign key (builderplotcode) references buildingspecification (bscode) Foreign key (workstatuscode) references builderworkstatus (workstatuscode) Landlotdetails (lldcode, placename, pincode, areapincode, volumeinsqurefeet, lotownercode, plottype, pcacode) Foreign key (areapincode) references objectionforplot (areapincode) Foreign key (lotownercode) references lotowner (lotownercode) Foreign key (pcacode) references plotcollectionaggreement (pcacode) Assesment (assesmentid, assesmentname, result, avalability) Region (regionid, areaofregion, superviseid, regiondetails, volumn, regiontype, atcode, areapincode) Foreign key (superviseid) references councilsupervisor (cscode) Foreign key (regiontype) references typeofregion (regiontypecode) Foreign key (atcode) references advertisetype (atcode) Foreign key (areapincode) references objectionforplot (areapincode) Objectionforplot (areapincode, areaname, details) Buildingspecification (bscode, bsname, bsdetails, processpolicycode) Builderworkstatus (workstatuscode, reputrationstatus, builderratingpoint) Objectionapplications (oaid, applicantname, oatype, contact) Advertise (adcode, adname, addatetime, addesc, atcode) Foreign key (atcode) references advertisetype (atcode) Advertisetype (atcode, atypedetails, atyperating) Typeofregion (regiontypecode, regiontyname, details) Areaobstruct (aobscode, arealoc, areavolumn, areapincode) Foreign key (areapincode) references objectionforplot (areapincode) Objection (ocode, date, issuesinplotarea, oaid, reportpersoncode, plotobjectiontypecode) Foreign key (oaid) references objectionapplications (oaid) Foreign key (reportpersoncode) references lotowner (lotownercode) Foreign key (plotobjectiontypecode) references objectiontype (potcode) Objectiontype (potcode, type, subject, objectionautority) Noobjection (nob_id, applicantname, certifyauthority, detailscertification, ocode) Councilsupervisor (cscode, cs_name, contactnumber, departmentid) Foreign key (departmentid) references councildepartment (departmentid) Councildepartment (departmentid, name, role, type) Bibliography Coronel, C. and Morris, S., 2016. Database systems: design, implementation, management. Cengage Learning. du Plessis, H. and Van Niekerk, A., 2014. A new GISc framework and competency set for curricula development at South African universities. South African Journal of Geomatics, 3(1), pp.1-12. Harris, R.B., Harris, K. and Eplion, D., 2013. A Database Design and Development Case. Information Systems Education Journal, 11(5), p.4. Larman, C., 2012. Applying UML and Patterns: An Introduction to Object Oriented Analysis and Design and Interative Development. Pearson Education India. Lee, J.K., Lee, J., Jeong, Y.S., Sheward, H., Sanguinetti, P., Abdelmohsen, S. and Eastman, C.M., 2012. Development of space database for automated building design review systems. Automation in Construction, 24, pp.203-212. Mitrovic, A. and Suraweera, P., 2016. Teaching Database Design with Constraint-Based Tutors. International Journal of Artificial Intelligence in Education, 26(1), pp.448-456. Parks, R.F. and Hall, C., 2016. Front-End and Back-End Database Design and Development: Scholars Academy Case Study. Information Systems Education Journal, 14(2), p.58. Tomi, J., Bogojevi, N., Tati, B. and oki, Z., 2012, October. Design And Implementation Of On Line Database Of Noise Sources. In Proceedings of 23rd national and 4th international conference Noise and Vibration, Ni (pp. 17-19).