-
6.05-01 Make DEV the source for everything
DEV> Test, and DEV>Prod is more flexible; it allows multiple Test models, and Test models to be created and deleted without compromising Prod. It also supports segregation of duties Best Practice articles: ALM Explained—Part 1: Compatibility ALM Explained—Part 2: Testing Questions on this topic? See 6.05-01 Make DEV the…
-
6.05-02 Archived Models
Compatible models (DEV, TEST or PROD) can be archived without breaking the link between them Related to Rule: 6.05-03 Model modes Best Practice article: ALM Explained—Part 2: Testing Questions on this topic? See 6.05-02 Archived Models in our Planual forum.
-
6.05-03 Model modes
When restoring Archived models, restore the model to Deployed mode if this is a Production or Test model Related to Rule: 6.05-02 Archived Models Questions on this topic? See 6.05-03 Model modes in our Planual forum.
-
6.05-04 Keep the Development model small
Keep the Development model as small as possible. Try and only use a selection of items in the production lists to minimize the model size. Use the “create from revision” functionality as part of the set up Best Practices article: Prepare Applications for ALM Questions on this topic? See 6.05-04 Keep the Development model…
-
6.05-05 Use a Data hub to populate the Development Model
Use saved views within the Data Hub to populate the Development model. This allows defined data and structures to be imported to assist initial development and component testing Questions on this topic? See 6.05-05 Use a Data hub to populate the Development Model in our Planual forum.