JavaTM Virtual Reality Applications and
Related Technologies

"Freedom" Service-Oriented Methodology
Release Process

Overview  Process      Levels  Models  Definitions  Papers  Training


chart semantics

Principles -- Release

Create Installation Documentation

Installation documentation is created by the developers, and contains installation and configuration instructions for the system administrators who will install the application on the customer's computers. Installation documentation may be in a README type file or other informal format, unless formal documentation is authorized by customer management.


Validate Installation Documentation

The installation documentation is validated by test team personnel. Validation includes checking the content for accuracy and clarity by performing the documented installation and configuration procedures. Also, the natural language content of the installation documentation is checked for correct spelling and grammar. Any deficiencies noted are reported to the development team using any efficient internal reporting mechanism, such as direct communication with the appropriate developers.


Create Release

Especially on larger or distributed projects, work products should be stored under the aegis of a configuration management and version control (CM) system. The subset of the development team tasked with maintaining the CM system creates the distribution files for the release group after all code test and documentation validation tasks have been successfully completed. The distribution files for the release will usually utilize a standard archive format such as UNIX tape archive (tar), Java archive (jar), or web archive (war). The release archive contains all work products delivered to the customer such as source and object code for the application, documentation (user, installation and API), test code and data, and test results.


Populate Reuse Library

Reusable components are also packaged for release by development CM personnel after all code test and document validation tasks are completed, but in separate release archives termed library archives. A library archive contains work products such as source and object code, specifications (design and, if appropriate, requirements), documentation (installation and API), test code and data, and test results for the reusable components.

Train Customer Personnel

If authorized by the customer, development personnel create training materials for the instruction of customer personnel in the installation, configuration, and operation of the application. and help train the customer staff if requested. The training materials may consist of items such as instructor led courses, on-line courses, and tutorials. Customer staff feedback from trial use of the training materials is used to enhance and correct the training materials.


about downloads gallery goal plan products
e-commerce future science & engin you & me

Copyright (C) 2000-2003 LDJ Trust