Artifact: Enterprise Tool Configuration
This work product describes how to configure a tool or set of tools for enterprise deployment.
Domains: Software Capability Improvement
Purpose

The purpose of this work product is to simplify usage of tools by standardizing on configurations that are proven to work with the organization's processes.

Relationships
RolesResponsible: Modified By:
TasksInput To: Output From:
Description
Main Description

This work product describes how to configure a tool for enterprise-wide deployment. Tool configurations are often associated with method assets, because the tool may automate - or be configured to be consistent with - a given process.

Some examples of tool configurations include - but is not limited to - the following:

  • Preference settings
  • Permissions
  • Report definitions
  • Descriptions of requirements attributes and traceability for a requirements management tool
  • Project templates for a project management tool such as Rational(R) Team Concert.
Tailoring
Impact of not havingEach team must learn how to configure tools on their own if defined enterprise tool configurations do not exist. It would be difficult for teams to evaluate the effectiveness of tools and make improvements if such configurations do not exist. 
Reasons for not needingSmaller organizations may choose not to define standard tool configurations because there aren't enough teams to benefit from reuse. If you have tools that are easy to configure correctly without the need for standard configurations to exist, then this artifact is not needed.
Representation Options

Representation options include a document that describes how to configure the tool, a report from a configured tool that describes how the tool is configured, or the actual files used to configure the tool.