Sequoia it development methodology
 | welcome page | projects | contact us | get  the free off-line version |

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.

(-)  programming or coding the software

(-)  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

(-)  In every case, write the users documentation; this one should include:

screens description

reports description

user guide - processes description

error messages - advises

authorized data values

(-)   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 .

(-)   Checklist sample to test an interactive program.

(-)  Adequacy tests: check that the program conforms to the detailed study

functional adequacy

methodological adequacy

(-)  Data tests

mandatory data

versus a list of authorized values

versus a fork of values (pay a particular attention to the extreme values !)

compatibility between data

physical input sequence; test illogical mouse driven input sequences

screen refreshment after data input

(-)   Output validity tests

direct check of the output tables and files

check by the downstream programs

check by reports, control lists, statistics, ...

(-)  Navigation tests

when using the function, tabulation and other displacement keys

by using the mouse

test also the cancellation of the current operation

(-)  Other tests of the user interface

coherence of the design, functions, buttons, operating mode throughout all programs.

multilinguism

sub-screens synchronization for the different authorized operations

behavior in case of error; precision of the error messages

(-)  Access security tests;

(-)  for the different user profiles:

selective access to the menus & programs

specific behavior of the programs; selective access to the data

(-)  exceptional access procedures:

possibility to access the programs from non-official procedures

possibility to access the data from non-official programs

(-)  Transactions tests

behavior when a transaction is interrupted

concurrent accesses management

(-)  Performances tests

(-)  Documentation and help files tests. 

RA.1.5 Phase closing actions

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


copyright (c) séquoia sprl (www.sequoia.be), belgium, 1999-2000. all right reserved.