Managing an Environment for Subsetting › Apply Effective Project Management Techniques › Subsetting Considerations › Choosing Life-Cycle Techniques

Choosing Life-Cycle Techniques

Use the following life-cycle techniques to reduce the need for subsetting, minimize the impact of changes to the data model, and improve developer interaction:

• Defer action diagramming-Instead of building Process Action Diagrams before starting Design, build them after the procedures and screens are approved.
• Prototype screens using literals-Instead of building a screen prototype that is based on information views (which use entity types and attributes); create screens that contain only literals. This prototype can even be built in a separate model.
• Add dialog flows after Procedure Action Diagrams are tested-Instead of adding dialog flows at the start of Design, plan the overall dialog flow. The flows can then be added to the model after the Procedure Action Diagram and screen have been thoroughly unit-tested. Adding flows last reduces the probability that you accidentally include the procedures of other developers in your subset.
• Use workstation construction for testing-Instead of generating code and unit testing using host construction, unit test on the workstation. Using the workstation construction minimizes the number of updates to the Host Encyclopedia.

  Using the workstation construction also reduces the contention on the Host Encyclopedia by minimizing the number of code generation jobs.

  Note: The life-cycle techniques are not appropriate for all projects.