Artifact: Method Design
This artifact describes the overall structure of a method asset (or a set of related assets), as well as the significant decisions and rationale that drive the content and organization of the asset.
Domains: Software Capability Improvement
Purpose

Examine and explain the method asset so that key decisions can be made about its included elements and the relationships between those elements.

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

This artifact is an abstraction of the authored method asset in terms of its composition (for example: plug-ins, packages, configurations, and elements). 

All elements are briefly described, and the relationships between elements are identified. All necessary variability relationships are specified.

Tailoring
Impact of not havingImplementation of the method asset will proceed without needed analysis. This can lead to assets of poor quality that are difficult to understand, deploy, or reuse.
Reasons for not needingIf the method asset is very simple, then documentation in addition to its authored definition is not necessary as the design is visible in the definition.
Representation OptionsThe format of the design is not as critical as the content. Use whatever format would enable you to communicate with the stakeholders so that they can understand the design and provide feedback. However, when selecting a format, it may be helpful to consider the downstream activities that may be able to leverage these materials (for example, enablement) and choose a format that promotes such reuse.