Creating Views › Assign View Characteristics › Recommendations

Recommendations

Consider the following tips as you create views:

• When passing data up and down a hierarchy of Action Diagrams, use one of the following combinations of view characteristics:
  • Import, Transient, Exported
  • Export, Transient, Imported
• When importing data that will not be exported, use Import, Transient, Import only. These views can be starved.
• When multiple Action Diagrams require access to the same physical data record, use persistent views. Batch processing is an example of multiple Action Diagrams requiring access to the same physical data record.
• Remember that persistent views require coordination between the using and the used Action Diagrams as to the intended usage of the data. It is not a good idea, for example, to lock entity occurrences that are needed only for inquiry. A view can only be Locked or Unlocked. There is no option to switch between the two options at runtime.
• Starve all views, especially entity action views. Include only the attributes that are required to make an Action Diagram work. Starving the views this way saves time at execution because the DBMS does not retrieve any unnecessary data.