Kbase 14206: Roundtable Sample Workspace Setup and Explanation
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Roundtable Sample Workspace Setup and Explanation
DRAFT COPY - Currently under review and edit.
INTRODUCTION:
=============
Roundtable allows for an unlimited number of workspaces to be setup
configured in any way. Here is an example and explanation of a
sample workspace setup.
WHY YOU NEED TO KNOW THIS:
===========================
Recommend a setup of workspaces to a new Roundtable user. Understand
the impact of managins multiple workspaces.
SCHEMATIC EXPLANATION:
======================
/-----\ /----\ /----\ /---- | DEVEL | -->| TEST | --> | BETA | --> | PROD | \_____/ \____/ \____/ \____/ \--> CUSTOMERS
Each "Bubble" represents a different workspace. For this entry
assume there are 4 workspaces. Development, Testing, Beta, and
Production.
Definition of Workspaces:
DEVELOPMENT:
Frequency of change: HIGH
Quality of testing data: POOR
Useful for unit testing only
TESTING:
Freqency of change: LOW
Quality of testing data: GOOD
Stable for full cycle testing
BETA
Frequency of change: SCHEDULED CHANGES ONLY
Quality of testing data: EXCELENT
Stable for load and regression testing using real system data
PRODUCTION
Frequency of change: EMERGENCY PATCHES ONLY
Quality of testing data: None
Used for deployment purposes only;
OVERVIEW:
The majority of changes occur in the Development workspace. As
cycle testing yields bugs, those changes are made directly in the
Testing workspace. As bugs are found doing load testing in the Beta
workspace, changes can be made in that workspace with management
authorization only. As customers report high priority bugs the
patches are made in the Production workspace for immediate deployment
to the end users.
As changes are made in any workspace other than Development, those
changes are imported back into the development workspace. If changes
have occurred in the development workspace and another workspace
on the same object, the 2 changes must be integrated when imported
into the development workspace.
WHY run things like that?
That combination of workspace give the development group plenty of
separation as well as allowing them to respond to the customers
needs as quickly as possible. The re-integration of changes made
in other workspaces, is the price you pay for the flexibility.
Progress Software Technical Support Note # 14206