Accessing Database Quality Essay

ACCESSING DATABASE QUALITY

  1. Introduction

The survey of informations patterning and database design is going more of import in today ‘s universe because logical database design is independent of the system environment and helps the terminal user to see a practical position of how the database will work when it is physically designed. It besides helps to cognize if there will be an mistake in the database when it is designed ( Teorey et al 2009 ) .

Database design is an of import facet of working with a database, besides good quality database that a user is satisfied with “ does non merely go on ” if it ‘s non designed decently and carefully. No affair how good a DBMS is, it will execute severely with a ill designed database ( Rob, Coronel and Crockett 2008 ) .

This study is non traveling to depict the tools and notations used in Database

Design but it ‘s traveling to discourse how these tools help in planing quality database.

  1. Meaning of Quality Databases and Framework for Evaluating Database Quality

In logical database modeling, a batch of factors have to be considered when looking at quality, some of the factors are but non limited to scalability, public presentation, velocity, stop user, cost, ownership and informations unity. These factors help in bring forthing a database of high quality ( Hoxmeier 1997 ) . There are different types of logical informations patterning attacks but I will be concentrating more on Entity Relationship ( ER ) theoretical accounts, Unified Modelling Language ( UML ) theoretical accounts which includes tools like usecase diagram and description and Enhanced Entity-Relationship Modelling ( EER ) in this paper, because of its simpleness and readability they are the most popular modeling attack ( Teorey et al 2009 ) .

Nowadays, an international criterion is in topographic point for measuring the quality of package merchandises but the same ca n’t be said of conceptual theoretical accounts, they are evaluated in pattern in an “ ad hoc ” manner ( merely for a peculiar intent ) . A good quality conceptual theoretical account may take to a good quality database system while a good quality conceptual theoretical account might non be implemented decently besides a hapless quality conceptual theoretical account might be improved upon subsequently in the design stages. This ground makes conceptual theoretical account affect the “ efficiency and rightness ” of a database system because this factors depend on the quality of the conceptual theoretical account, a high quality conceptual theoretical account will take to a high quality database system ( Moody 2005 )

As discussed in ( Batini, Ceri and Navathe 1992 ) logical database theoretical account is made up of a normalized theoretical account of the database set to the 3rd normal signifier, it besides consist of many elements that make up a database but non specific to any database direction system or database execution. At this point the public presentation factors of the database are neither a major consideration nor the applications that will be utilizing the database although this is argued by Hoxmeier ( 1997 ) that public presentation should be considered as an facet of overall database quality. The major ground behind the logical design is to construct a theoretical account of how the database will look like when capturing the informations needed by the users.

It is farther argued in ( Batini, Ceri and Navathe 1992 ) how critical the logical design stage is to database design because the logical design is done by professionals in cooperation with the database users to bring forth a database good quality. Evidence of this is shown in the illustration of planing an thought direction system where some premises where made based on demands given by the client. This was sorted out finally after run intoing the client and demoing them the ER and UML theoretical account because the client was able to understand the theoretical accounts presented to them through ER diagram, usecase diagram etc which are all constituents of logical database design.

Harmonizing to ( Hoxmeier 1997 ) it is stated that rating of overall database quality can be assessed by four major factors which are ;

  1. Database Process Quality:When looking at this factor, we have to first of all expression at the design procedure which is driven by the demands and the major demands of the terminal user of the database. An illustration of this is the “ Courtesy Coach Company ” assignment where we used ER & A ; UML theoretical account to come up with a logical design of the database. Although some of the solutions to the scenario might non be perfectly right but they were of good quality.
  1. Database Data Quality: This factor largely deals with the physical database design or the care of the informations in the database. The age of the information is considered as a metric for measuring informations unity.
  1. Database Semantic Quality:Harmonizing to Hoxmeier ( 1997 ) Storey and Wang presented an extension to the traditional ER theoretical account to add quality demands into conceptual design of database which are database “ quality informations and merchandise quality informations ” but the implicit in statement of this is that there should be a difference between the quality demands and the database belongingss. It is further discussed that it is hard to plan a database with high semantic value without anterior important experience and sphere cognition.
  1. Database Behaviour Quality:This factor deals with the design, building and execution of a solution sphere that provides entire solution to the job sphere as discussed in ( Hoxmeier 1997 ) .

Fig 2.1Problem sphere and solution ( Hoxmeier 1997 )

The image above from ( Hoxmeier 1997 ) shows the job sphere and the different types of solution provided from the likely solution to the optimal or entire solution.

  1. CONTRIBUTION OF “ ENTITY RELATIONSHIP MODEL ” TO QUALITY DATABASE DESIGN

The ER theoretical account is a theoretical account that describes informations in footings of entities, properties and the dealingss between them frequently represented by diagrams called entity relationship diagrams ( Riordan 2005 ) .

Initially the most hard portion faced by interior decorators and terminal users when planing databases is that they tend to see informations and its usage in different ways. This is the ground why most of the designs produced does non run into the user ‘s demands, the ER theoretical account is a design tool that has the reply to this because it communicates the design to the user in a clear and non-technical manner ( Connoly and Begg 2010 )

As discussed in ( Kesh 1995 ) organisations depend critically on their informations thereby doing the demand of high quality database of import. It is further discussed that since ER theoretical accounts stand at the nucleus of database design today, the quality of a database can merely be met merely if the ER theoretical account is of high quality every bit good. In account, this writer is seeking to state that a good database has to be of high quality and the criterion of the quality has to be shown on the logical design of the database utilizing ER theoretical accounts. An illustration of this is the “ Courtesy Coach Company ” assignment where we came up with a logical design of the client ‘s database but the nucleus of this design was the ER theoretical account even though there were other theoretical accounts like the UML, this supports Kesh ‘s statement of ER theoretical account standing at the nucleus of database design.

It was further discussed in ( Kesh 1995 ) that we can specify the quality of a database relevant to aim because ER theoretical accounts are used to plan a database to be used by an organisation, any choice step should see the ends of the organisation. This theoretical account should besides be apprehensible to the user groups involved and besides supply a technically sound platform that can be used to make a complete and consistent database.

Finally, the ER theoretical account can non bring forth really high quality of a database design because it does non to the full back up the representation demands of much more complex database applications like Computer Aided package Engineering ( CASE ) and Computer Aided Design ( CAD ) hence the demand for an advanced modeling called Enhanced Entity-Relationship Modelling ( Connolly and Begg ) .

Fig 3.1Example of an ER diagram from the assignment.

The diagram above shows the ER theoretical account of a manager company that need to better their information system. It shows the primary keys and foreign keys to assist heighten informations quality, cardinalities to assist acquire better apprehension of the relationship between entities in the same way. These are the tools that are used in ER modeling to assist plan a quality database as discussed in Connolly and Begg ( 2010 ) .

  1. CONTRIBUTION OF “ ENHANCED ENTITY-RELATIONSHIP MODEL ” TO QUALITY DATABASE DESIGN

The EER theoretical account combines the patterning constructs of the ER theoretical account and UML theoretical account to convey out a design of higher quality because a database design of high quality should be flexible plenty to accommodate to the demands of information demands and alteration in informations ( Rob, Coronel and Crockett 2008 ) . There are three major grounds for the usage of EER harmonizing to Houldcroft ( 2011 ) and they are:

  1. Integrity, Consistency, Correctness
  2. a different manner of looking at the existent universe to assist us understand it
  3. may assist to avoid traps e.g Fan Traps, Chasm Traps

Looking at the above grounds, one of the major grounds behind the EER theoretical account is the ability of it to assist avoid traps for illustration the fan trap which is a state of affairs where “ two or more 1: many relationships fan out from the same entity ” ( Connolly and Begg 2010 ) .

The basic constructs used by the EER theoretical account are specialization/generalization, entities collection, and composing. Along with the three major grounds for the usage of EER theoretical account it is besides used to plan a database utilizing object-oriented construct like heritage, abstraction, collection and coherence ( either high or low ) which are all used in system design ( Kendall and Kendall 2011 )

Fig 4.1:Example of an EER diagram ( LDD Group Assignment Submission )

The above diagram shows the construct of EER discussed earlier. An illustration of this construct is the heritage relationship show where the local and abroad categories are inherited from the trip category. This diagram has been able to farther heighten the quality of our database design from merely the ER diagram.

  1. CONTRIBUTION OF “ UML and USE-CASE MODEL ” TO QUALITY DATABASE DESIGN

Having looked at ER theoretical account, another theoretical account used for database design is the UML. This theoretical account is besides in common usage today chiefly because it puts the user of the database in the Centre of its design utilizing graphical linguistic communication. Most of the design system in topographic point today focus largely on the hardware and package, this is where UML comes in because it uses a design scheme whereby the system is built around the people you have in head to utilize the database ( Naiburg and Maksimchuk 2001 ) . The account is justified in Hoxmeier ( 1997 ) which says meeting the outlook of the terminal user is one facet of the overall quality of a good database even though this is non the lone 1.

Use-case is one of the tools used in UML and it is used in giving a contemplation of how the system will work when implemented ( Muller 1999 ) . A usage instance theoretical account besides has four major effects on planing database of high quality harmonizing to Muller ( 1999 ) and they are:

  1. It helps to stand for an atomic dealing through the systems and this dealing helps in planing logical database and besides the architecture used in dealing processing demands of the system.
  2. It helps in demoing how the database will utilize informations elements.
  3. It besides provides an substructure for mensurating database merchandise
  4. Finally it helps to supply the footing for formalizing database merchandise. This is one of the most of import consequence of usecase because as the physical design of the database is traveling on you can formalize the work done by associating it back to the usecase, finally this helps in coming up with a database that meets the user ‘s demand which in bend contributes to the quality of a database.

( Muller 1999 ) .

The diagram on the following page shows an illustration of how a typical use-case digraph looks. It shows the histrions and the actions they are making. There are besides use-case descriptions that help to break simplify the design and an illustration from the assignment is shown below:

Usecase: Position Vehicle Details

Actors

  1. Administrator
  2. Staff
  3. Client

Pre-condition

  • User has entree to system

Stairss

  1. User chinks on vehicle
  2. User selects the vehicle the wish to see information about

Post-condition

  • User views the selected vehicle information

Fig 5.1: An illustration of Use-Case diagram ( LDD Group Assignment )

  1. Correctness and Quality in Database Design

The issue of rightness and quality is a controversial issue in the designing of database in the universe today. In this subdivision I will take a expression at what academic documents have said about this issue.

When looking at quality of a database design, we besides have to look at informations quality and information quality has four major dimensions which are but non limited to: completeness, deficiency of ambiguity, meaningfulness and rightness. Besides data quality means different thing to different users ( Storey and Wang 1997 ) .As discussed further in Storey and Wang ( 1997 ) “ rightness ” is merely one of the dimensions when looking at informations quality so we ca n’t merely establish the quality of a database design on its rightness but it has to be considered before we can state a database is of high quality.

Besides ( Olson 2003 ) said “ a right database has the capableness of run intoing all the demands, better informations quality as discussed above, better informations unity and extinguish informations redundancy but it is non sufficient entirely for planing a database of high quality.

  1. Decision

Finally, a high quality database design is a database design that has to the full met the user demands and is scalable plenty to suit betterments as clip goes on, the four suggested standards for mensurating it are database procedure quality, database informations quality, database informations quality and database behaviour quality. Database design rightness on the other manus is a design that has the necessary informations theoretical account to back up user demands, better informations quality and better informations unity.

Besides the usage of ER, EER, Use-Case helps in capturing the concern demands which in bend brings client satisfaction which is one end of quality database design.

Mentions

BATINI, C. , CERI, S. and NAVATHE, Sham ( 1992 ) .Conceptual database design: An entity-relationship attack.California, Benjamin/Cummings.

CONNOLLY, Thomas M. and BEGG, Carolyn E. ( 2010 ) .Database systems: A practical attack to plan, execution, and direction. California, Addison-Wisely.

HOULDCROFT, Alan ( 2013 ) . Notes from Logical Database Development. Sheffield Sheffield Hallam University.

HOXMEIER, John A. ( 1997 ) . A model for accessing database quality. [ on-line ] . Last accessed on 17 January 2014 at: hypertext transfer protocol: //osm7.cs.byu.edu/ER97/workshop4/jh.html

KENDALL, Kenneth E. and KENDALL, Julie E. ( 2011 ) .Systems analysis and design.United Kingdom, Pearson.

KESH, Someswar ( 1995 ) . Measuring the quality of entity relationship theoretical accounts. [ on-line ] .Information and package engineering,37( 12 ) , 681-689. Article from Science Direct last accessed on 15 January 2014 at: hypertext transfer protocol: //www.sciencedirect.com.lcproxy.shu.ac.uk/science/article/pii/0950584996817459

MOODY, Daniel L. ( 2005 ) . Theoretical and practical issues in measuring the quality of conceptual theoretical accounts: Current province and future waies. [ on-line ] .Data & A ; cognition technology,55( 3 ) , 243-276. Article from Science Direct last accessed on 15 January 2014 at: hypertext transfer protocol: //www.sciencedirect.com.lcproxy.shu.ac.uk/science/article/pii/S0169023X04002307

MORSHEED, Shawon, et Al ( 2013 ) Logical Database Assignment Submission. Sheffield, Sheffield Hallam University.

MULLER, R. J. ( 1999 ) .Database design for smarties: Using UML for informations mold.[ online ] . California, Morgan.

NAIBURG, E. J. and MAKSIMCHUCK, R. A. ( 2001 ) .UML for database design.Boston, Addison-Wesley Professional.

OLSON, Jack E. ( 2003 ) . Data Quality: The truth dimension. [ on-line ] . United province of America, Morgan Kaufman. Book from Google eBook last accessed 17 january 2014 at: hypertext transfer protocol: //books.google.co.uk/books? id=x8ahL57VOtcC & A ; printsec=frontcover # v=onepage & A ; q & A ; f=false

RIORDAN, M. Rebecca ( 2005 ) . Planing effectual database systems. Massachusetts, Pearson.

ROB, Peter and CORONEL, Carlos ( 2008 ) .Database systems: Design, execution and direction. Hampshire, Cengage Learning.

STOREY, Veda C. and WANG, Richard Y. ( 1997 ) . Modeling quality demands in conceptual database design. [ on-line ] . Last accessed on 16 January 2014 at: hypertext transfer protocol: //web.mit.edu/tdqm/www/tdqmpub/QEROct98.pdf

TEOREY Toby J. , et Al. ( 2009 ) .Database design know it all.United States of America, Morgan Kaufmann.