uu.seUppsala University Publications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Databasdesign: Nulägesanalys av normalisering
Uppsala University, Disciplinary Domain of Humanities and Social Sciences, Faculty of Social Sciences, Department of Informatics and Media.
Uppsala University, Disciplinary Domain of Humanities and Social Sciences, Faculty of Social Sciences, Department of Informatics and Media.
2016 (Swedish)Independent thesis Basic level (degree of Bachelor), 10 credits / 15 HE creditsStudent thesis
Abstract [sv]

År 1970 introducerades normalisering med syfte att organisera data i relationsdatabaser för att undvika redundant data och reducera risker för anomalier. Idag finns indikationer på att en mer nyanserad bild av normalisering behövs då dagens databaser ställs inför nya utmaningar och krav. Det här arbetet utförs i form av en fallstudie där en analys av tre databaser inom olika verksamheter genomförs. Med utgångspunkt i normalformerna genomförs en explorativ analys för att identifiera vilka aspekter som påverkar normalisering i industrin. Slutsatsen av arbetet är att det är svårt för en oberoende part till databasen att avgöra och tolka normalformernas uppfyllnad. Faktorer som påverkar normalisering av databaser är: utvecklarens intuition, användarens påverkan av datakvalitet samt den tekniska skuld som quickfixes orsakar.

Abstract [en]

Normalization was first introduced in 1970 with the purpose to organize data within relational databases in a way to avoid data redundancy and reduce the number of anomalies. As databases are facing new challenges and requirements, indications have been identified which points to a need for a more detailed view of normalization. This work is the outcome of a case study where three databases are analyzed. With the normal forms as starting point, an explorative analysis is made with the goal to identify different aspects that affects the way normalization is conducted within the industry. The conclusion is that it is difficult for an outsider to the database to interpret and determine whether the normal forms are fulfilled or not. Aspects affecting normalization are: the developer's intuition, users' impact on data quality and the technical debt that quickfixes creates.

Place, publisher, year, edition, pages
2016. , 37 p.
Keyword [en]
database design, normalization, normal form, denormalization
Keyword [sv]
databasdesign, normalisering, normalform, denormalisering
National Category
Information Systems, Social aspects
Identifiers
URN: urn:nbn:se:uu:diva-297212OAI: oai:DiVA.org:uu-297212DiVA: diva2:941285
Subject / course
Information Systems
Educational program
Bachelor programme in Information Systems
Supervisors
Examiners
Available from: 2016-06-27 Created: 2016-06-22 Last updated: 2016-06-27Bibliographically approved

Open Access in DiVA

fulltext(3966 kB)136 downloads
File information
File name FULLTEXT01.pdfFile size 3966 kBChecksum SHA-512
38bc70599f0f114920c7a6822b2f7f027fb6812d7d9ec9124afee8a3ad1cf4e02a5a27af51f5e6ace1ed2aa21df22bc8aef614e684d7e91e4b408fbcbf718293
Type fulltextMimetype application/pdf

Search in DiVA

By author/editor
Wesslén Weiler, JohannesÖhrn, Emelie
By organisation
Department of Informatics and Media
Information Systems, Social aspects

Search outside of DiVA

GoogleGoogle Scholar
Total: 136 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 281 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf