Browse Prior Art Database

Data Model Notation Collapsing - Business System Development Method/Entity Relationships

IP.com Disclosure Number: IPCOM000106779D
Original Publication Date: 1993-Dec-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 4 page(s) / 110K

Publishing Venue

IBM

Related People

English, M: AUTHOR [+2]

Abstract

Disclosed is a solution to the problem of converting (collapsing) a Business System Development Method (BSDM) Data Model to an Entity-Related (E-R) Data Model while maintaining integrity of the data and data relationships. The method also introduces a check for the completeness of the conversion.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Data Model Notation Collapsing - Business System Development Method/Entity Relationships

      Disclosed is a solution to the problem of converting
(collapsing) a Business System Development Method (BSDM) Data Model
to an Entity-Related (E-R) Data Model while maintaining integrity of
the data and data relationships.  The method also introduces a check
for the completeness of the conversion.

      Data Modelling in BSDM allows for the data and the
relationships between the data to be shown on the same diagram.  It
enables the users to easily understand the data model and use the
diagram when explaining requirements and check that the requirements
are both understood and included in the data model.  This notation
also allows the modellers to explain the model and the business
requirements the model represents to people new to the business.

      Entity-Relationship data model notation is a more useful
notation for Data Base designers as the E-R entities more closely
match the tables that will result.  The entities in a BSDM Data Model
will not necessarily result in a Data Base Table but may only signify
a relationship between entities.  It is therefore useful to be able
to develop a Data Model with users in BSDM notation and then collapse
the data model to E-R notation for Database Analysts at a later stage
of the development process avoiding redesign of the data model using
a different notation.  The method for this conversion is exemplified
below.

      Figs. 1 and 2 show the same data structure in both BSDM and E/R
notations as an example representing the way some of the data is
structured in a banking organization.

      A BRANCH must have one and only one address.  An ACCOUNT must
have one and only one ACCOUNT HOLDER.  An ACCOUNT must be related to
at least one BRANCH.  There is an additional business rule,
incorporated in the processing logic, that an ACCOUNT can be related
to only one BRANCH at any one time.  Attributes of the entity A/C AT
BRANCH, defining the start and finish dates of the relationship will
support this processing.  A CUSTOMER must be of only one CUSTOMER
TYPE, must have only one ADDRESS and may hold one or more ACCOUNTs,
or may hold no ACCOUNT.  There may be zero, one or many CUSTOMERs of
any one CUSTOMER TYPE.  There may be zero, one or many BRANCHes at
any one ADDRESS.  There may be zero, one or many CUSTOMERs at any one
ADDRESS.  The BSDM diagram contains a number of ASSOCIATIVE ENTITIES,
these represent th...