Practical implementation of TS software

The process of transitioning to practical use of software technology begins with the development and subsequent implementation of a transition plan. This plan may reflect a phased approach to transition, from a carefully selected pilot project to projects with a significantly increased variety of features.

The transition plan should cover:

• information regarding the goals, evaluation criteria, schedule, and possible risks associated with the plan;
• information regarding the acquisition, installation, and customization of software creation technology;
• information regarding integration with existing facilities, including both the integration of facilities with each other and their integration into the organization’s software development and operation processes;
• anticipated training needs and resources used during and after the transition process;
• Definition of standard procedures for the use of software technology.

The transition plan should define the initial application practices and procedures for using the tools. Real application of any software creation technology in a specific organization and a specific project is impossible without development of a number of standards (rules, agreements) that should be observed by all project participants (it is especially important at collective software development by a large number of groups of specialists). Such standards include the following:

• modeling and design guidelines;
• naming conventions;
• quality control procedures and acceptance processes, including examination schedules and methodologies used;
• procedures for backing up, protecting master copies, and configuring the project database;
• procedures for integration with existing facilities and databases;
• procedures for data sharing and database integrity control;
• secrecy standards and procedures;
• documentation standards.
• design standard;
• standard of design documentation;
• standard of the user interface.

For successful implementation of software technology in an organization, consistency in its application is essential. Since most systems are developed collectively, it is necessary to determine the nature of the future use of software creation technology by both individual developers and groups. The use of standard procedures will ensure a smooth transition between the individual stages of the software lifecycle.

The result of this stage is the introduction of the software technology into the daily practice of the organization. In addition, software technology support is included in the organization’s ongoing software support plan.