agile, analysis, best practice, data, data design, design, event, flowchart, functional decomposition, iterative, jackson, lifecyle, management, model choices, modeling, perspective, planning, priority sequence, process, requirements, scope, SDLC, state, state transition, swim lane, technology, use case, visual, warnier-orr
All Data Are Protected (ala The Matrix)
An Event occurs that is associated with a collection of data attributes that need protection.
Each unique Event has a finite list of Data that are expected to occur when a new instance of an Event happens. In almost all cases, that list of Data includes, at least, the Date, Time, Location, and Instigator of the Event. Other Data are also needed depending on the specific Type or Name of each Event. This list of proscribed Data for a unique Event is called a Row. When each Row first expresses as an Event it is considered an Unprotected Row.
Event Data requires that it receive protection before becoming in three levels:
- Content Protection
- Field Relationship Protection
- Object Relationship Protection
Once a set of Event Data or each Unprotected Row passes all three of these levels, it can become a legitimate Transaction and take its place in its Legitimate Protected Transaction Row Object to be processed against its Master Data Object(s).
Protection Level One: Content
Each Data has a pre-determined set of Valid Values that are anticipated and allowed in that Data. If a Data contains Value that is not in the anticipated Valid Value set, then the Unprotected Row that represents this particular Event is sent to “Corrections” for further processing. This set of Event Data CANNOT be processed as a Level One Unprotected Row.
Further, each Unprotected Row for a unique Event will have Data that are defined as Primary and/or Partial Key Data which is used to uniquely identify each instance of every Event occurrence.
Valid Unprotected Rows that pass this Level One Protection can proceed to Level Two Protection validation.
Protection Level Two: Field Relationship
Some Data have Values that require or limit the selection of Valid Values for other Data in its Unprotected Row. If a Data Value prescribes that other Data be limited to a subset of their anticipated Valid Values then those Data must be validated based on that limited subset.
If a related Data does not comply with its limited Valid Value set, then the Unprotected Row that represents this particular Event is sent to “Corrections” for further processing. This set of Event Data CANNOT be processed as a Level Two Unprotected Row.
Valid Unprotected Rows that pass this Level Two Protection can proceed to Level Three Protection Validation.
Protection Level Three: Object Relationship
Successful Level One and Level Two Unprotected Rows must have Relationships with other Objects in the Model by using the Valid Values that are in their Data that are part of their Primary or Partial Key Data. The Values in these Primary and/or Partial Key Data have specific Relationship Rules to other named Objects that must be Validated.
Optional Relationship Rules need NOT be Validated.
The Relationships that are marked as Mandatory MUST find Protected Rows in named Objects elsewhere in the Model. If these Mandatory Relationships are not proven to exist then the Unprotected Row is sent to “Corrections” for further processing. This set of Event Data CANNOT be processed as a Legitimate Protected Transaction.
Valid Unprotected Rows that pass this Level Three Protection will be inserted in the Legitimate Protected Transaction Row Object that this Type of Event is assigned to for further processing.
All Data Are Protected.