A Typical Development Process

The following steps are a typical process for modifying objects and deploying them through successive path codes and into the production environment.

1. Check out the objects from the DV920 path code, modify them, test them, and check them back in.

2. Use an incident-tracking system or any numbering system to track changes.

   Always use an incident number when you check in the objects.

3. If the objects need to reside on the logic server, transfer them to the DV920 path code on that server.

4. Test the objects by comparing them to the objects on the server.

5. Use an incident number with Object Transfer to transfer the objects to the PY920 path code.

   Use the checkout log to confirm the transfer (optional). The objects are not in production, but they are now available for you to build a test package in the PY920 path code.

6. Build a full or update package.

7. Test the newly built, unreleased package in the PY920 path code.

   You test the package only by comparing it to workstation processes, not to server processes. Although the name of this package will probably be PY920U1 (update package number 1 for the PY path code), it is a test package because you have not released it to the users.

8. Schedule the update package to deploy to a test machine and test it in an environment that contains PY objects with PY data.

9. Deploy server objects to the PY920 path code on the enterprise server and test them.

   If you prefer, you can build the server package and schedule the deployment at the same time that you build and schedule the workstation package. Building these packages simultaneously can save you time, although this method puts a greater load on the server.

10. Schedule the new package to deploy to PY users.

11. Use an incident number with Object Transfer to transfer the object to the PD920 path code.

    Use the checkout log to confirm the transfer (optional). The objects are now in the production environment and are available for you to build a package in the PD920 path code.

12. Build a full or update package for client workstations.

13. Perform a server package build.

    You can transfer the server package now or wait until it has been tested on a workstation.

14. Schedule the new package to deploy to end-user workstations.

15. Deploy the server objects to the PD920 path code on the enterprise server and test them.

    If you prefer, you can build the server package and schedule the deployment at the same time that you build and schedule the workstation package.