LESSON-13 INSTRUMENTAL MODELING OF BUSINESS RULES REFLEXIONS (Cont’d; Ashraf, Khan, and Mir)
LESSON-13 INSTRUMENTAL MODELING OF BUSINESS RULES REFLEXIONS (Cont’d; Ashraf, Khan, and Mir)
13.1 Introduction
This is an attempt to simplify variant business rules embedded in the textual version of business description. These are designed to prorogate impetus of data modeling of rules (as reflexions) excavation and engineering straight away their binary relationships (associations) to document their data models and their constraints, if any.
The business rules analysis ultimately boils down on variety of binary relationships (associations) of entity(s), these variant cases are described in moderate details one by one by illustrations of logical data model reflexions underneath.
13.2 (1 to 1) ASSOCIATIONS: (Mandatory to Optional)
Business Rule: Occurrence of A (parent) is mandatory and occurrence of B (child) is optional (at the most one) associating with single occurrence of A.
Elucidation: Occurrence of entity A (parent) is mandatory, associating with occurrence of entity B (child) as optional with cardinality at-the-most one or zero, occurrence in B associates with one and only one occurrence in A.
13.4 (1 to 1) ASSOCIATIONS: (Optional to Mandatory) & (Optional to Optional)
Crucial Note: These genres neither, portray the relational events, nor, conform to the prescribed relational instincts on the footings of parent-child relationship. Pragmatically, the parent must exist prior to a child entry. The violation would jeopardize the standard SQL enforcement on the database due to missing linking pin FKs.
Note: Certain applications of legacy systems need imperatively the indicated genres for custom oriented perceptions of parent-child relationship.
This e-monograph covers on the surface the indicated reflexions, for completeness beyond relational technology.
13.5 (1 to m) ASSOCIATIONS: (Mandatory to Optional)
13.7 (1 to m) Associations: (Optional to Mandatory) & (Optional to Optional)
13.8 (m to m) ASSOCIATIONS: (Mandatory to Optional)
Business Rule: Many occurrences of entities A and B (parents’ distinct pairs) are related to child in A_B as parent-child. Child (optional) occurrences in A_B may have many distinct parents’ pairs; cardinality m is predefined may be fixed or variant.
Elucidation: Parent’s distinct pairs rest in entities A and in B, while occurrences of child relationship of distinct parent’s pairs rest in a new entity A_B. Thus the child relationship has a variant tone of child occurrence in A_B. The mandatory cardinality m of parents distinct pairs in A & B and optional cardinality m of child A_B may invoke occurrence(s) in A_B.
13.9 (m to m) ASSOCIATIONS: (Mandatory to Mandatory)
Business Rule: Many occurrences of entities A and B (parents’ distinct pairs) are related to child in A_B as parent-child.
Child (mandatory) occurrences in A_B has many distinct parents’ pairs, cardinality m is predefined fixed or variant with m >0.
Elucidation: Parents’ distinct pairs rest in entities A and in B, while occurrences of child relationship of distinct parent’s pairs rest in a new entity A_B. Thus the child relationship has a variant tone of child occurrence in A_B.
The mandatory cardinality m of parent’s distinct pairs in A & B and mandatory cardinality m occurrence(s) of child A_B shall be invoke in A_B.
13.10 (m to m) ASSOCIATIONS: (Optional to Mandatory) & (Optional to Optional)
Crucial Note: These genres neither, portray the relational events, nor, conform to the prescribed relational instincts on the footings of parent-child relationship.
Pragmatically, the parent must exist prior to a child entry.
The violation would jeopardize the standard SQL enforcement on the database due to missing linking pin FKs.
Note: Certain applications of legacy systems need imperatively the indicated genres for custom oriented perceptions of parent-child relationship.
This e-monograph covers on the surface the indicated reflexions for completeness beyond relational technology.
Business Rule: Optional occurrences of A and B (parents) related to optional/ mandatory (cardinality m) occurrence(s) in A_B (child).
Elucidation: Occurrences of A and B without parent child binding. However when child A_B is mandatory (cardinality m).
13.10 (m to m) ASSOCIATIONS: (Optional to Mandatory) & (Optional to Optional)
Crucial Note: These genres neither, portray the relational events, nor, conform to the prescribed relational instincts on the footings of parent-child relationship.
Pragmatically, the parent must exist prior to a child entry.
The violation would jeopardize the standard SQL enforcement on the database due to missing linking pin FKs.
Note: Certain applications of legacy systems need imperatively the indicated genres for custom oriented perceptions of parent-child relationship.
This e-monograph covers on the surface the indicated reflexions for completeness beyond relational technology.
Business Rule: Optional occurrences of A and B (parents) related to optional/ mandatory (cardinality m) occurrence(s) in A_B (child).
Elucidation: Occurrences of A and B without parent child binding. However when child A_B is mandatory (cardinality m).
*****
Click To MAIN PAGE: OBJECT- ORIENTED RELATIONAL MODELLING E-MONOGRAPH, By J. Ashraf, M. Khan, and H. Mir
PART-II: “OBJECT-ORIENTED MODELING Foundation”
PART-III: “OBJECT-ORIENTED MODELING Pragmatic Approach”
APPENDICES:
*****
MESSAGE: DEDICATED TO ANONYMOUS COMBATANTS OF KNOWLEDGE
مکتب علم الل مہد منل لحد Learning continues from birth to death
FOR PROMOTION OF LEARNEDNESS SHARE WITH FRIENDS ABOUT;
- CAUSE AND EVENTS – SPATIAL And TEMPORAL RESPECTIVELY: https://be4gen.wordpress.com/2012/11/16/cause-and-events-spatial-temporal-respectively/
- WHETHER ‘BRAIN-POWER’ OR ‘HEART-IMPULSE’ PLINTHS ‘HUMAN GEN’? http://sunedu.wordpress.com/2012/09/17/whether-brain-power-or-heart-impulse-plinths-human-gen/
************
Pingback: LESSON-12 BUSINESS TRANSACTION RULES (Cont’d; Ashraf, Khan, and Mir) | be4gen