Requirements field reference for the CMMI process in Azure Boards
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019 | TFS 2018 - TFS 2013
When you create a project using the CMMI process, you can define fields to track requirements to be developed and their importance to the overall product.
None of these fields are indexed. For more information about data types and field attributes, see Work item fields and attributes.
| Field name | Description | Data type | Reportable type |
|---|---|---|---|
| Requirement Type | The kind of requirement to implement. You can specify one of the following values (see note 1): - Business Objective - Feature (default) - Functional - Interface - Operational - Quality of Service - Safety - Scenario - Security Reference Name=Microsoft.VSTS.CMMI.RequirementType |
String | Dimension |
| Impact Assessment | The customer impact of not implementing this requirement. You might include details from the Kano model about whether this requirement is in the surprise, required, or obvious categories. Reference Name=Microsoft.VSTS.CMMI.ImpactAssessmentHtml |
HTML | None |
| User Acceptance Test | The status of the user acceptance test for a requirement. You can specify one of the following values (1): - Pass (default) - Fail - Not Ready - Ready - Skipped - Info Received You specify Not Ready when the requirement is in the Active state, and you specify Ready when the requirement is in the Resolved state. Reference Name=Microsoft.VSTS.CMMI.UserAcceptanceTest |
String | None |
| Subject matter experts | The names of one to three team members who are familiar with the customer area that this requirement represents. You can specify the names of valid team members only. Reference Name=Microsoft.VSTS.CMMI.SubjectMatterExpert1 …Microsoft.VSTS.CMMI.SubjectMatterExpert3 |
String | None |
Notes:
- To change the menu selection, see Customize a picklist.