REALIZATION, ACCEPTANCE, LAUNCH

Phase RR.1 Realization 

RA.1.1 Purposes

The realization includes all the internal activities of the supplier or of the IT department before the final product can be delivered to the end-user or to the customer.

  creating static page contents : texts, layouts, graphics, ...

 programming or coding the software and/or the HTML-generating templates and scripts

 customizing and configuring the package or the programs

 writing the documentations

 performing the internal tests

RA.1.2 Realization actions

 For the specific developments:

program or code the software

perform the basic configuration before the application can be transferred to the end-users

write the technical programs documentation

 For the packages:

customize and configure the package or the programs

program the specific add-ons, the interfaces with other applications and other migration programs

write the customization and program technical documentations

  It is very important that the users documentation is written in a clear language that the users can understand. The users documentation should always start from the business point of view and explain how you can solve a business case by using the application.

RA.1.3 Project management actions

The purpose of the project management is to respect the deadlines and to manage the possible ups and downs.

RA.1.4 Quality assurance actions

The quality during the realization and maintenance phases depends greatly on the development methodology that you have selected. It influences indeed the understanding that the people can have of the application, its portability, its compatibility, the team work integration.

A procedure should ensure that not any element could be delivered not presented to the acceptance without having first passed successfully the internal validation tests . This should be booked in the Internal Validation Tests File .

RA.1.5 Phase closing actions

Deliver the application and its documentation for acceptance and launch in production