Purpose
  • To verify that the tools can be used to develop the system.
Role:  Tool Specialist 
Frequency:  When new tools are introduced or changes have been made to existing tools. 
Steps:  
Input Artifacts:    Resulting Artifacts:   
Tool Mentors:   

Workflow Details:   

The tools and the development infrastructure has to be verified before the project starts using them. How this is done will clearly vary dependent upon skills, technology, and tools.

Verify the Environment

Verify the environment contains the correct hardware, software, and data. Verify that the correct hardware is installed. This may be done visually or through a tool (such as using Windows Properties for My Computer). 

Verify the Tools

Verify that the correct software configuration is installed. This may be done by looking at the registry settings, 'ini' files, or by launching the tool and looking at some information options or configuration options.

Verify Data

Verify the data contains the appropriate data. Verifying data may require using tools to visually inspect the data, or using an application to display the data. At some point, one or more use cases may be selected and executed (one or more scenarios) for each tool to ensure the tool and the results of using the tool are consistent with the need.

Run the Tools

Assemble a small team of people who know the tools and the project's development case well, and let them run the tools. 

  • Test multi site, many colliding users
  • At least one use case scenario for each tool has been executed to verify the appropriate installation and configuration of the tools. 
  • Try the normal scenarios in the development case and in the tool guidelines.  
  • Test the integration between different tools. 

Issue change requests if necessary. 



Rational Unified Process   2003.06.13