response needed d2- current and emerging

needresponsesQ-D2.docx

Home >Computer Science homework help >response needed d2- current and emerging

Article 1:

Discussion question:

We all had the unfortunate experience of seeing how computers can, at times, make life's journey abit more difficult. This is especially true in knowledge centric workplaces. Describe an example of a very poorly implemented database that you've encountered (or read about) that illustrates the potential for really messing things up. Include, in your description, an analysis of what might have caused the problems and potential solutions to them. Be sure to provide supporting evidence, with citations from the literature.

An Example of a Poorly Designed Database

Database implementation is defined as the installation of the Database Management System (DBMS), its configuration, customization, testing and running, and integration it with other applications, as well as the training of users. The various processes and stages of database implementation include database project scope definition, database project organization, the DBMS products selection, creation of the initial implementation schedule and plan, database design, database project training, database testing, and performance review and periodic review (Coronel & Morris, 2016).

One example of a poorly implemented database is the Easy Digital Downloads database. The relationship between the data stored by the plugin was poorly done, and thus the implementers depended on data structures given by WordPress. The e-commerce data such as order items, clients, payment records, and order metadata amongst others were stored in the wp_postmeta and wp_posts table. The implementers failed to see how cumbersomeness the e-commerce data stored in the core posts table would be as the number of websites and users processing the same information increased. The company had bad data schemas. For this case, the cause for the problem is a poorly designed database schema. The effect of poor designs is that the database limits the users and also poses serious scaling issues; bad data schema designs leads to performance issues. Additionally, a poor API design may limit the extent to which other developers may extend or use the project (The monster that is a poor database schema. 2016).

The poor implementation of Easy Digital Downloads database can be addressed by rebuilding the data schema. However, the backward compatibility should be given a priority; if ignored, migration to the improved or new scheme will be poor, making future users and developers to stop relying on the project. Also, the changes can break many websites because of the changes being implemented, leading to a support nightmare. The developer should ensure that the abstraction layer (the API for database interaction) for the database is kept or provided (Dillon, 2015). For Easy Digital Downloads database, the developers built an abstraction layer(s) for products, payments, and clients. Furthermore, the wp_posts table abstraction layers us the WP_Query which gives the ways of querying data from the posts DBMS without writing an actual SQL.

References

Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management. Cengage Learning.

Dillon, D. M. (2015). U.S. Patent No. 9,009,195. Washington, DC: U.S. Patent and Trademark Office

The monster that is a poor database schema. (2016, May 16). Retrieved January 13, 2019, from Pippins Plugins: https://pippinsplugins.com/resolving-poor-data-schema-designs/

Article 2:

Discussion question:

An inadequately represented Database makes a broad extent of issues the end clients. On the off chance that the database doesn't work appropriately at an endless then it can make hurt its most uncommon degree. Here, in this talk, I should need to examine an occasion where an insufficiently made database makes a broad extent of issue the Virginia State FBI. Thirty Years back, FBI had pushed a Database called ViCAP (Violent Criminal Apprehension Program) to get the guilty parties by separating and unsolved terrible practices. This database was plot so it sees criminal in context of the activity or terrible conduct performed at any rate not on hereditary decorating specialists. It derives that if a man utilizes a bleeding edge in a terrible conduct and he finished another awful conduct without utilizing a sharp edge then database didn't see the individual. This kind of ineffectively finished database made blameworthy gatherings suitably escape from encroachment. Information Mining was uncommonly prevalent at the time of Creation of ViCAP and Computing Power was comparatively shameful and quickly accessible. As indicated by a Survey, just 1400 out of 18000 police working environments were adjusted ViCAP. Besides, this database used to report the central 1percent of awful practices displayed every year.

Canadian Officials has adjusted the ViCAP structure to perceive the terrible conduct points of reference and affiliation encroachment. This elucidation was ended up being gainful at seeing Sexual Assault Crimes. In any case, there was still some lack of protection existed with the program in light of which an immense measure of execution masters talked about ViCAP. In a 82 billion dollar spending plan, ViCAP had gotten just 800,000 dollars reliably. There were just 12 individuals dealing with this program and ViCAP was working dreadful and In a year ViCAP had organized just 220 encroachment. Lawbreakers and Rapists were in the meantime making tracks in a contrary course from the encroachment.

References:

1) By T Christian Miller (JULY 30, 2015): Why Can’t the FBI Identify the Serial Rapist.

2) Fundamentals of database systems. London: Pearson.