The first item, Maximize Non-redundant Development, is accomplished by ensuring that every enterprise database and business information system only contains the components necessary for the scope of either the database or business information system. This is accomplished through their development according to the sequence set within the Resource Life Cycles Nodes.
As stated in the Issue section, constricting the scope of the business information system to just that which is required to achieve the state change represented by the Resource Life Cycle Node is important. This ensures non-redundancy, and a “bright line” set of conditions of where the business information system starts, and finally a bright line of where the business information system ends.
The most immediate vehicle for setting out the business information system’s bright lines is the scope of the enterprise data model subset that is allocated to achieving the state change for the Resource Life Cycle Node. If a properly defined the Resource Life Cycle Node’s subset data model does not have the database tables needed for an existing business information system, that business information system’s scope is too large and must be reduced to fit just the needs of the Resource Life Cycle Node. The only exception to this would be any tables that bridge one Resource Life Cycle Node’s ending state to the starting state of the next Resource Life Cycle Node.