Structured entity relationship model

The SERM (structured entity relationship model) is an amplification of the ERM which is commonly used for data modeling. It was first proposed from Prof. Dr. Elmar J. Sinz in 1988. The SERM is commonly used in the SAP-world for the data modeling.[1]

Aims
  1. structuring of large schemes
  2. visualization of existence dependency
  3. avoidance of inconsistencies
  4. avoidance of unnecessary relationshiptypes

SERM symbols

SERM example

  • Customer and article are independent entities
  • Every order is referred to one customer. Orders without customers are illegal (order is an ER type). Customers without any orders are legal because they are independent Entities.
  • To every order there is belonging at least one order item.
  • Every order item is related to exactly one order.
  • Every invoice is referred to one customer, as well. Invoices without customers are illegal. Customers without any invoice are legal.
  • To every invoice there is belonging at least one invoice line item.
  • Every invoice line item is related to exactly order item. An order item could be calculated or not.
  • SERM is already in the third normal form
gollark: But concurrency will improve potatOS's speed *and* make it 4050‰ harder to reason about!
gollark: With use of concurrency it may become as much as potato % faster.
gollark: PotatOS Tetrahedron is coming soon and will streamline the potatOS code to make it easier and cooler.
gollark: DacDJ is an alternate installer for potatOS which plays music.
gollark: Solarflame is coming. Hide!

References
  1. Michael Röthlin (2010). Management of Data Quality in Enterprise Resource Planning Systems. BoD – Books on Demand. pp. 118–. ISBN 978-3-89936-963-2.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.