PM 1.4: Toolset Management

  PM1.4 - Toolset-Management durchführen

Contents		Product Flow Handling Recommendation Explanation		Roles Tools Requirements External Norms Links to the V-Model Mailinglist

Product Flow

+ "Chapter" are extra columns from the original printed version of GD 250

Further Results:
Selection of development environment/assessment environment

Handling

The methods and tools as well as the standards and regulations must be defined for all submodels. The methods and tools must be bindingly allocated to the activities and products of the project-specific V-Model.

The selection of methods and tools is realized on the basis of standards or recommended tools. Provided that the adherence to certain standards is mandatory-like GD 251 and GD 252 for the German MoD field-the standard conformity for the specifications must be proven.

The participants (customer, contractor, user) must agree about which methods and which tools are to be established.

Apart from the selection of methods and tools for the development environment and the definition of standards and regulations, this activity includes the preselection of the target computer equipment and the tools related to the target computers.

Special requirements with regard to the development environment and tools related to the target computers (e. g. cross compilers) resulting from the actual quality requirements for the software to be developed are generated and established in submodel SD. This may also result in the update of the specifications in activity PM1.4 - Toolset Management.

If necessary, it will be determined by special proof tests whether the selected tools are suitable.

The IT measures realized by security functions or other concepts require a trustworthiness that meets the reliability requirements. This is also determined by the quality of its implementation (e. g. E-level). Depending on this, however, a development environment must be selected that meets the requirements.

If necessary, minimum requirements have to be met with regard to methods and tools.

Based on IT security reasons, special requirements may be set up in order to differentiate between various users and roles and to guarantee their accountability within the development environment.

This may help

• to authorize the user for activities and actions, or
• to make it possible to separate roles in order to realize activities.

Recommendation

• Technology is available until
  • either the end of utilization, or
  • the end of SWMM, or
  • the end of the development.
• The tool manufacturer gives his support.
• The tool manufacturer possibly guarantees an acceptable further development of the product necessary both for both the technology used in the system and for the technology supporting the development process.

Explanation

Further relevant criteria are also reliability and robustness of a tool, distribution and references, compatibility, adaptability, maintainability, flexibility, network readiness, support, use by the staff member in charge of the application, other contractors, customer and subcontractors.

The project management has to ensure of adequate application support. This requires:

• integration of the development environment into the organization,
• resources for using the tools,
• training, consulting and supporting the tool users,
• release of new tool versions for the project.

Roles

Tools Requirements

External Norms

Links to the V-Model Mailinglist

This page online  •  GDPA Online  •  Last Updated 05.Feb.2003 by C. Freericks