Testing
The code is set up on a staging server from the development
server. This preliminary step is not a final "go-live", it is
merely a coming out for a first glimpse by the client.The
staging server is viewable by the client, and is not visible
to the general public. When we get to this stage, we have
already completed several layers of quality control testing,
including testing on the modular and Alpha levels.
At the staging server stage, we are ready to "widen" the
testing groups to include the client's staff, if they wish, to
provide feedback and possible revisions. It is at this stage
that there may be several beta versions, each of which goes
through an extensive quality assurance process.
Staging Servers
Our staging database server contains the business data, such
as marketing campaigns and product catalogs, and database
resources that you want to stage to the database servers in
the production environment. Business users can update business
data in the staging environment so that you can test and
approve the changes before you incorporate the changes into
the run-time environment. |
|
The staging environment
prevents disruption of the run-time site and services by
isolating the test and production systems.
The staging server is a mirror of the production business
management server. We create staging projects and routes on
the staging server to deploy site updates from the test
environment to the production environment.
We also finalize the training strategy for the clients staff.
Roll out
Final Solution Implementation, Roll-out & Installation
Implementation includes installation, onsite verification of
correct installation, as well as a few other tests to confirm
final solution implementation is complete.
The more simple the technology, the easier it will be to
operate with minimal training. In fact, for technology that is
primarily for use in locations to be operated or supervised by
casual staff, simplicity in use and operation will likely be
one of the key considerations in our design. |