REALIZATION, ACCEPTANCE, LAUNCH

Phase RA.2 Acceptance 

RA.2.1 Purposes

The main purpose of the acceptance phase is to validate one more the solution in an environment as close as possible to the final operational environment, and to perform the official acceptance.

The acceptance is performed among others by the key-users. It is thus mandatory to train them before.

RA.2.2 Realization actions

Train the key-users.

Prepare the training supports

Create the training environment, close to the operational environment.

Prepare the testing environment.

Install the hardware, the network, the operating system and all components of the acceptance environment.

Perform the data conversions, data migration, interfaces, in order to get a significant data set.

 Perform the tests games

Also performances tests, in an environment close to the operational environment.

In order to test the security, you could simulate the final system and allow the key-users to test separately the different user roles.

 Complete procedure test

test not only the information system, but all the business processes

ask a friend (or a customer key-user) to make a purchase and verify, from the user's point-of-view :

site performances from its home (download time, response time)

customer understanding of the site organization and the purchasing process

reception of a confirmation e-mail, ...

product reception : waiting time, packaging and product state, ...

 Validate the other components of the solution:

operational documentation

users documentation, help files

RA.2.3 Project management actions

 Gather all conditions in order to build the acceptance environment.

Get the key-users availability

RA.2.4 Quality assurance actions

A procedure should ensure that not any element could be set in operation without having first passed successfully the acceptance tests . This should be booked in the Acceptance File .

 The nonconformities should be recorded in the Nonconformities File ; you should follow them up until they are certified.

 Tests must be performed on the following issues:

 individual tests on the various components, in the acceptance environment

included the various documentations.

to be checked in comparison with the deliverables recorded during the preliminary study, and mentioned in the Realization Specifications.

 integration tests in order to test the global coherent operation of the whole set.

RA.2.5 Phase closing actions

 Sign the official acceptance

 Decide to launch in production