Requirements

Overview

Requirements are the top-level containers for product capabilities or feature areas in UXit. They help you organize work from a high-level feature idea down to the specific behaviors you want to define and review.

Requirements in UXit follow this structure:

Requirement -> Use Case -> Acceptance Criteria

Each level adds more detail and specificity.

• Requirement defines the feature area or capability being delivered.
• Use Case breaks that requirement into a focused user scenario.
• Acceptance Criteria capture the specific behaviors that should be true for that use case.

Use this page to create and manage requirements. For more detailed guidance on use cases and acceptance criteria, see the related pages below.

Workspace Views

The Requirements workspace includes multiple views of the same active work:

• Requirements
• Kanban
• Gantt
• Activity

These views all show the same active work in your account. Use Requirements to keep use cases organized.

Create A Requirement

1. Open Requirements.
2. Click New Requirement
3. Enter the requirement details.
4. Click Create

Requirement Fields

• Requirement: The name of the feature or capability being delivered. Limited to 32 characters.
• Description: A short summary of what the requirement includes. Limited to 84 characters.
• Tracking Link: A link to related work in tools like Jira, ClickUp, Asana, or Linear.
• Point of Contact: The person responsible for the requirement.

After Creation

New requirements appear as cards in the Requirements list, including an ID such as REQ-001, title, description, point of contact, date, counts, progress, and a more-actions menu.

Manage Requirements

Open the requirement card menu to manage an existing requirement.

Current actions include:

• Edit requirement
• Share requirement
• Delete requirement

Archive

Use the trash icon in the Requirements toolbar to open the Archive, which lists archived requirements by Type, Title, Date Archived, and Edit row actions. The badge on the trash icon shows how many items are currently in the archive.

Building Out Requirements

After creating a requirement, you can continue refining it by adding use cases and acceptance criteria.

• Use cases break the requirement into focused user scenarios.
• Acceptance criteria define the specific behaviors that should be true for each use case.

For step-by-step guidance, see the dedicated Use Cases and Acceptance Criteria pages.